Persuasion Audit Input Contract: Required Fields, Rejection Rules, and Handoff

The direct answer

Define the minimum input record and deterministic rejection rules before local, structured review of sales-copy persuasion and trust risks begins. The working output is A versioned input-contract table with required fields, validation rules, owners, and rejected-example fixtures.

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 input contract

This input contract 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 input contract remains reviewable because its decisions have named owners, evidence fields, and stop conditions.

Copy this Persuasion Audit table into an intake form or machine-readable schema. Its validation column answers whether an input is usable for local, structured review of sales-copy persuasion and trust risks; its rejection column prevents an incomplete record from entering execution as though it were approved.

Example record

{
  "contract_version": "1.0",
  "request_id": "ART-13-01-EXAMPLE",
  "intended_outcome": "Define the minimum input record and deterministic rejection rules before local, structured review of sales-copy persuasion and trust risks begins.",
  "input_boundary": "a Claude MCP environment, the draft copy, approved claims, and house voice constraints",
  "authority": "named owner approval required for consequences outside this artifact",
  "acceptance_status": "NOT_TESTED",
  "reopen_if": "persuasion strength checked before claim truth"
}

Contract decision

A record is admitted only when every required field is present, its source is named, and the qualified compliance reviewer can run the associated check. It is held when a missing fact could be supplied without changing scope. It is rejected when the requested effect exceeds the authority of the recorded owner or asks this product to promise an outcome outside its boundary.

Run the workflow as a sequence of decisions

The Persuasion Audit input contract 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 input contract 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 input contract 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 input contract condition observable. Its record binds source, time, method, and the current ART-13-01 fingerprint.

Contain the input contract: 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 input contract 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 input contract condition observable. Its record binds source, time, method, and the current ART-13-01 fingerprint.

Contain the input contract: 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 input contract 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 input contract condition observable. Its record binds source, time, method, and the current ART-13-01 fingerprint.

Contain the input contract: 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 input contract 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 input contract condition observable. Its record binds source, time, method, and the current ART-13-01 fingerprint.

Contain the input contract: 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 input contract 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 input contract condition observable. Its record binds source, time, method, and the current ART-13-01 fingerprint.

Contain the input contract: 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 input contract check cannot run, its result remains NOT_TESTED.

Ownership and handoff

For this Persuasion Audit input contract, 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-01.

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 input contract check, retain the tested object, environment or source, observation time, method, expected result, actual result, verifier identity, and artifact hash. In this ART-13-01 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 input contract names the distinct reader job: Define the minimum input record and deterministic rejection rules before local, structured review of sales-copy persuasion and trust risks begins.
• 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 input contract 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-01 condition probably holds.

Related campaign guides

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

• Persuasion Audit Evidence Packet: What to Capture Before a Decision
• 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