Persuasion Audit Evidence Packet: What to Capture Before a Decision

The direct answer

Assemble reviewable evidence for local, structured review of sales-copy persuasion and trust risks without turning assumptions or producer claims into proof. The working output is A claim-to-evidence packet with provenance, freshness, contradiction, and NOT_TESTED fields.

For Persuasion Audit, the bounded capability is local, structured review of sales-copy persuasion and trust risks. Begin only when the team can supply a Claude MCP environment, the draft copy, approved claims, and house voice constraints. The documented delivery target is a local MCP copy-review tool returning structured verdicts and edit suggestions; anything broader requires a new scope and a new authority decision.

The copyable evidence packet

This evidence packet is for teams that want repeatable copy feedback without sending drafts to another model API. It begins with a Claude MCP environment, the draft copy, approved claims, and house voice constraints and stays inside the documented workflow: local draft intake, rule evaluation, violation evidence, bounded suggestions, human adjudication, revision, and comparison. For Persuasion Audit, the evidence packet remains reviewable because its decisions have named owners, evidence fields, and stop conditions.

The Persuasion Audit evidence packet keeps each claim separate from its source and from the reviewer decision that accepts or rejects it. For this evidence-packet task, a URL or file name supplies provenance but not automatic proof; an executor saying “done” remains an assertion until a separate observation supports the exact criterion.

Machine-readable evidence row

{
  "claim_id": "CLM-01",
  "claim_type": "OBSERVED",
  "content": "Every flagged issue points to exact draft text.",
  "evidence": "attach a direct readback or test receipt",
  "provenance": {
    "source": "named path or system",
    "observed_at": "ISO-8601",
    "method": "inspection or test"
  },
  "status": "NOT_TESTED",
  "contradictions": [],
  "reopen_if": "persuasion strength checked before claim truth"
}

Contradiction rule

When two admissible records disagree, retain both and mark the claim REVIEW. Do not average incompatible observations or choose the convenient one. The qualified compliance reviewer records what changed, which evidence applies to the current boundary, and what must be rerun. When required evidence is unavailable, the status stays NOT_TESTED.

Run the workflow as a sequence of decisions

The Persuasion Audit evidence packet follows this working sequence: local draft intake, rule evaluation, violation evidence, bounded suggestions, human adjudication, revision, and comparison. Within this artifact, each phrase marks a state boundary for local, structured review of sales-copy persuasion and trust risks. A stage output becomes the next named input, while a failed, missing, or unavailable check keeps the dependent evidence packet decision closed.

Separate failure register

• FAIL-01: Persuasion strength checked before claim truth.
• FAIL-02: Suggestions that invent proof or urgency.
• FAIL-03: Dark-pattern risks treated as style preferences.
• FAIL-04: Local processing undermined by external logging.
• FAIL-05: A rule score accepted without reading the cited text.

The register supplies negative cases for the complete acceptance set. A reviewer determines affected checks from observed evidence; array position never asserts that one failure proves or disproves one criterion.

The producer can explain what it attempted, but the qualified compliance reviewer evaluates the evidence. If the artifact changes, its prior verdict expires. This is especially important for local, structured review of sales-copy persuasion and trust risks, where a plausible narrative can hide a stale configuration, an untested negative case, or an authority mismatch.

Failure and recovery drills

A useful Persuasion Audit evidence packet explains what happens when its happy path breaks. These drills come from the accepted product truth record rather than a claim that every buyer has each failure. Use safe synthetic or authorized observations for local, structured review of sales-copy persuasion and trust risks, and keep private credentials out of every fixture.

1. Persuasion strength checked before claim truth.

Detect for Persuasion Audit: copy owner captures a direct readback or safe fixture that makes this evidence packet condition observable. Its record binds source, time, method, and the current ART-13-02 fingerprint.

Contain the evidence packet: stop only the affected Persuasion Audit path after observing “persuasion strength checked before claim truth”. Preserve its failed material and last verified state instead of erasing evidence or blindly repeating an external effect.

Recover and prove: apply the smallest authorized Persuasion Audit correction, then have a distinct reviewer re-evaluate the complete accepted check set. Do not select one check merely because it shares this failure's list position. If any affected evidence packet check cannot run, its result remains NOT_TESTED.

2. Suggestions that invent proof or urgency.

Detect for Persuasion Audit: claim owner captures a direct readback or safe fixture that makes this evidence packet condition observable. Its record binds source, time, method, and the current ART-13-02 fingerprint.

Contain the evidence packet: stop only the affected Persuasion Audit path after observing “suggestions that invent proof or urgency”. Preserve its failed material and last verified state instead of erasing evidence or blindly repeating an external effect.

Recover and prove: apply the smallest authorized Persuasion Audit correction, then have a distinct reviewer re-evaluate the complete accepted check set. Do not select one check merely because it shares this failure's list position. If any affected evidence packet check cannot run, its result remains NOT_TESTED.

3. Dark-pattern risks treated as style preferences.

Detect for Persuasion Audit: brand reviewer captures a direct readback or safe fixture that makes this evidence packet condition observable. Its record binds source, time, method, and the current ART-13-02 fingerprint.

Contain the evidence packet: stop only the affected Persuasion Audit path after observing “dark-pattern risks treated as style preferences”. Preserve its failed material and last verified state instead of erasing evidence or blindly repeating an external effect.

Recover and prove: apply the smallest authorized Persuasion Audit correction, then have a distinct reviewer re-evaluate the complete accepted check set. Do not select one check merely because it shares this failure's list position. If any affected evidence packet check cannot run, its result remains NOT_TESTED.

4. Local processing undermined by external logging.

Detect for Persuasion Audit: qualified compliance reviewer captures a direct readback or safe fixture that makes this evidence packet condition observable. Its record binds source, time, method, and the current ART-13-02 fingerprint.

Contain the evidence packet: stop only the affected Persuasion Audit path after observing “local processing undermined by external logging”. Preserve its failed material and last verified state instead of erasing evidence or blindly repeating an external effect.

Recover and prove: apply the smallest authorized Persuasion Audit correction, then have a distinct reviewer re-evaluate the complete accepted check set. Do not select one check merely because it shares this failure's list position. If any affected evidence packet check cannot run, its result remains NOT_TESTED.

5. A rule score accepted without reading the cited text.

Detect for Persuasion Audit: tool operator captures a direct readback or safe fixture that makes this evidence packet condition observable. Its record binds source, time, method, and the current ART-13-02 fingerprint.

Contain the evidence packet: stop only the affected Persuasion Audit path after observing “a rule score accepted without reading the cited text”. Preserve its failed material and last verified state instead of erasing evidence or blindly repeating an external effect.

Recover and prove: apply the smallest authorized Persuasion Audit correction, then have a distinct reviewer re-evaluate the complete accepted check set. Do not select one check merely because it shares this failure's list position. If any affected evidence packet check cannot run, its result remains NOT_TESTED.

Ownership and handoff

For this Persuasion Audit evidence packet, the adjudication role is qualified compliance reviewer. That role judges frozen acceptance evidence for local, structured review of sales-copy persuasion and trust risks without becoming the product owner, legal adviser, security authority, or buyer. Its handoff retains open gaps, failed evidence, changed hashes, and the next action permitted for ART-13-02.

Evidence and acceptance

Use these product-specific statements as candidate acceptance checks:

• Every flagged issue points to exact draft text.
• Claim truth is reviewed separately.
• Suggestions do not add unsupported facts.
• Network egress is tested rather than assumed.
• Human rulings are recorded.

For every Persuasion Audit evidence packet check, retain the tested object, environment or source, observation time, method, expected result, actual result, verifier identity, and artifact hash. In this ART-13-02 record, label a direct readback OBSERVED, a reproducible transformation COMPUTED, and an interpretation JUDGMENT; never merge those states into one confident claim.

The admitted Search Console packet contained no article-specific demand observation for this exact topic. The page is therefore justified by its distinct operator job and product truth, not by an invented volume estimate. Performance remains unknown until measured after an authorized release.

The product boundary remains controlling: A rules-based audit cannot prove that copy is ethical, accurate, compliant, persuasive, or effective for a particular audience. A qualified reviewer still owns claims and legal decisions.

Implementation checklist

• The evidence packet names the distinct reader job: Assemble reviewable evidence for local, structured review of sales-copy persuasion and trust risks without turning assumptions or producer claims into proof.
• The input boundary is explicit: a Claude MCP environment, the draft copy, approved claims, and house voice constraints.
• The intended deliverable is explicit: a local MCP copy-review tool returning structured verdicts and edit suggestions.
• Every required acceptance check has current evidence or an honest NOT_TESTED status.
• At least one negative fixture covers persuasion strength checked before claim truth.
• The qualified compliance reviewer is distinct from the artifact producer.
• Rollback or reopen conditions are written before consequential action.
• No ranking, traffic, conversion, compliance, certification, or buyer-outcome guarantee was added.

When this Persuasion Audit evidence packet has a failed item, repair that named item and rerun its dependent checks. Keep the frozen threshold intact; the remaining checks cannot establish that the failed ART-13-02 condition probably holds.

Related campaign guides

These four crawlable links cover the other Persuasion Audit operator artifacts. Each leads from the current evidence packet to a different reader task and promised artifact, rather than to a keyword variation of this page.

• Persuasion Audit Input Contract: Required Fields, Rejection Rules, and Handoff
• Persuasion Audit Operator Runbook: Daily Checks, Escalations, and Handoff
• Persuasion Audit Control Dashboard: Signals, Alerts, and Review Cadence
• Persuasion Audit Change Protocol: Versioning, Canary Tests, and Rollback