Pattern fixture

Proof Evidence Artifact Fixture

A proof page where an agent must preserve permission, baseline, action, result, metric context, and caveats before using evidence in copy or schema.

Agent Question

What claim is being supported, what evidence proves it, and what limitations must stay attached?

Pattern Contract

Make claims inspectable through case studies, testimonials, metrics, screenshots, crawl reports, reviews, or other permissioned artifacts.

Visible Sections

Supported claim
Evidence artifact
Permission note
Baseline
Work performed
Result
Limitations
Related offer link
Source and claim notes

Metadata Checks

One H1 identifies the proof fixture
Title avoids unsupported outcome hype
Description includes evidence context

Schema Checks

WebPage schema names proof-evidence-page as the pattern
Review schema is treated as conditional, not automatic
Metrics require dates and context

Traceability Checks

Every result, testimonial, screenshot, logo, or metric has source and permission status
Private evidence cannot leak to LLM summaries

Source Evidence

src/data/agent-reference.ts: pagePatterns.proof-evidence-page
/source-traceability.json
/crawl-evidence.json

Good Example

A proof item states the claim, evidence type, permission status, baseline, action, result, date range, caveat, and related service.

Bad Example

A proof page shows anonymous wins, percentages without dates, and review schema for a quote that is not eligible.

Agent Instructions

Classify public, private, or sanitized proof before publishing
Keep metric caveats next to metrics
Do not place private proof in LLM endpoints
Run qa:fixtures after proof pattern changes

QA Gates

npm run qa:fixtures
npm run qa:crawl
npm run qa:aeo

Completion Criteria

Claim, evidence, permission, and caveat are visible
Schema eligibility is explicit
Private-proof boundaries are documented