AAgentProof
Uses your browser's native print dialog. Choose "Save as PDF" to export.

AgentProof readiness report

Sample: Order-routing assistant

Report ID: trial-sample-001

Section 1

Executive summary

Sample: Order-routing assistant scored 64 on the AgentProof readiness band — placing it in the medium band.

This sample report illustrates how AgentProof presents readiness findings to a buyer. The actual findings, evidence examples, and improvement actions are illustrative only.

Section 2

Readiness score and band

Readiness score

64

Medium band

Score: 64 / 100

Band: medium

Bands: Foundational · Working · Solid · Strong · Best practice

Section 3

Critical findings

Report-linked guidance

Every finding links to Learn, controls, evidence, and an improvement action

  • Action authority

    Action authority not bounded

    high

    Why it matters. The agent can write to production records without a documented scope limit. A misunderstood prompt could affect data outside the intended workflow.

    Related control family

    Action authority

    Evidence example

    Document the exact set of record types + operations the agent is allowed to perform, plus a denylist for everything else.

    Improvement action

    Pin a written action-authority scope and have the agent owner sign it.

  • Human oversight

    No human approval on consequential drafts

    medium

    Why it matters. Drafts that change customer-visible records ship without a human reviewer. A bad draft becomes a bad customer-facing message.

    Related control family

    Human oversight

    Evidence example

    Show the reviewer queue, the SLA, and a transcript of one approved + one rejected draft.

    Improvement action

    Add a reviewer queue with a 4-hour SLA and a documented escalation path.

  • Testing & evidence

    Testing and evidence is thin

    medium

    Why it matters. There is no documented test suite for the agent's refusal patterns and no archive of audit traces. A regression would be invisible.

    Related control family

    Testing & evidence

    Evidence example

    Refusal-pattern test transcripts + a 30-day audit-trace archive.

    Improvement action

    Stand up an adversarial-prompt test suite and archive every audit trace for 30 days.

Section 4

Evidence expectations

Evidence expectations

What good evidence looks like — and how AgentProof uses it

  • Refusal-pattern transcripts

    Why it matters. Refusal patterns are the cheapest control. They prevent the agent from doing something it shouldn't.

    Good example

    A transcript showing the agent declining an out-of-scope request with a calm, branded message.

    Weak example

    A screenshot with the agent's reply cropped out.

    How AgentProof uses it. AgentProof reads refusal transcripts as the primary evidence for Zone 1 readiness.

  • Draft provenance

    Why it matters. Drafts must be clearly labelled so a reviewer knows what they are reading.

    Good example

    A draft with a provenance footer: agent, model, source data, draft timestamp.

    Weak example

    A draft pasted into a chat with no provenance.

    How AgentProof uses it. AgentProof scores Zone 2 readiness against the provenance footer.

  • Audit trace + rollback rehearsal

    Why it matters. If the agent takes an action, the audit trace and rollback path must both exist.

    Good example

    An audit row with actor identity, before/after, timestamp + a rehearsed rollback playbook.

    Weak example

    A log line with just a timestamp and no actor identity.

    How AgentProof uses it. AgentProof scores Zone 3 readiness against the audit trace + rollback evidence.

Section 5

Recommendations

  • Tighten access scoping — ensure the agent only reads sources the buyer's policy permits.
  • Capture human-in-the-loop checkpoints for the agent's highest-impact outputs.
  • Document the agent's tools / actions in the canonical capability zone (so reviewers can verify scope).
  • Schedule a quarterly readiness re-score against the latest intelligence pack.

Section 6

Improvement plan

  1. Open the AgentProof improvement cycle for this agent and complete the named actions.
  2. Capture the evidence requested in Section 4 — point to the existing artefacts in your organisation.
  3. Run the AgentProof score again. The new score will replace this report in the agent's report history.
  4. When the band moves up, share the improved report with the relevant approver.

Section 7

Methodology and version

Methodology
AgentProof readiness methodology v1 (live)
Intelligence pack
R13-A controlled source watchlist (curated)
Report layout
R17-EXPANDED ReportProfessionalLayout (7 sections)
Sample status
Illustrative content only. Not a certification. Not legal advice.
This report is a deterministic readiness assessment based on AgentProof's published methodology. It is not legal advice, not compliance certification, and not an endorsement of any third-party platform. The score reflects the answers and evidence provided at the timestamp in section 7.