Route fixtures
Page patterns as concrete routes
These fixtures are built for agents, not visitors. Each route demonstrates how a page-pattern contract should become visible structure, source notes, schema obligations, good and bad examples, and QA evidence.
Homepage Agent Entity Fixture
A public website homepage that must let an agent identify the entity, offer, audience, proof, next routes, and machine-readable discovery surfaces without prior chat context.
Pattern: Homepage entity summary
Agent question: What is this site, who is it for, what proof exists, and where should the agent inspect next?
Required visible sections
- Entity summary
- Primary offer
- Audience fit
- Proof summary
- Core route links
- Machine discovery links
- Source and claim notes
QA gates
npm run qa:fixturesnpm run qa:seonpm run qa:aeo
Open fixture route
Service Offer Scope Fixture
A service page where an agent must separate buyer pain, scope, inputs, deliverables, proof, objections, and next step before writing copy or schema.
Pattern: Service or offer page
Agent question: What is included in the offer, what inputs are required, what proof supports it, and what is the next step?
Required visible sections
- Problem
- Offer scope
- Inputs required
- Process
- Deliverables
- Proof
- Objections
- Next step
- Source and claim notes
QA gates
npm run qa:fixturesnpm run qa:seonpm run qa:aeo
Open fixture route
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.
Pattern: Proof evidence page
Agent question: What claim is being supported, what evidence proves it, and what limitations must stay attached?
Required visible sections
- Supported claim
- Evidence artifact
- Permission note
- Baseline
- Work performed
- Result
- Limitations
- Related offer link
- Source and claim notes
QA gates
npm run qa:fixturesnpm run qa:crawlnpm run qa:aeo
Open fixture route
Answer Ready Resource Fixture
A resource page where an agent must answer the target question directly, then add definitions, nuance, decision criteria, caveats, and related entity links.
Pattern: Answer-ready resource page
Agent question: What is the direct answer, what entities matter, what caveats apply, and what should the reader inspect next?
Required visible sections
- Direct answer
- Definition
- Detailed explanation
- Decision criteria
- Caveats
- Related entity links
- FAQ
- Source and claim notes
QA gates
npm run qa:fixturesnpm run qa:aeo
Open fixture route
Contact Conversion Fixture
A contact page where an agent must expose the next step, contact options, fit qualifier, expectations, service area, fallback path, and privacy note.
Pattern: Contact conversion page
Agent question: How should a qualified person contact the business, what should they provide, and what fallback exists?
Required visible sections
- Contact options
- Expected next step
- Fit qualifier
- Service area
- Privacy expectation
- Fallback path
- Source and claim notes
QA gates
npm run qa:fixturesnpm run qa:seonpm run qa:aeo
Open fixture route
Schema Backed Detail Fixture
A schema-backed detail page where an agent must compare visible facts, schema type, entity IDs, breadcrumbs, source claims, and blocked private facts.
Pattern: Schema-backed detail page
Agent question: Which visible facts are safe to expose through schema, and which facts must be blocked or sourced first?
Required visible sections
- Visible fact inventory
- Schema type selection
- Stable entity IDs
- Relationship context
- Source-backed claim references
- Blocked schema examples
- Source and claim notes
QA gates
npm run qa:fixturesnpm run qa:aeo
Open fixture route