Pattern fixture

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.

Agent Question

What is this site, who is it for, what proof exists, and where should the agent inspect next?

Pattern Contract

Orient agents, crawlers, and users to the entity, offer, audience, proof, and next routes.

Visible Sections

Entity summary
Primary offer
Audience fit
Proof summary
Core route links
Machine discovery links
Source and claim notes

Metadata Checks

One H1 states the entity and purpose
Title and description identify the agent-facing reference
Canonical route matches fixture route
Open Graph metadata mirrors the page purpose

Schema Checks

Organization and WebSite schema come from BaseLayout
WebPage schema names the fixture and pattern ID
Schema does not introduce claims missing from visible sections

Traceability Checks

Identity, proof, and next-step claims cite approved fixture evidence
Unsupported superiority language is listed as a blocked example

Source Evidence

src/data/agent-reference.ts: pagePatterns.homepage-entity-summary
src/data/agent-reference.ts: systemPurpose
/agent-manifest.json
/llms-full.txt

Good Example

A homepage starts with an entity summary, links to agent-manifest, file-map, examples, QA contract, and states what claims are source-backed.

Bad Example

A homepage uses a clever hero line, vague transformation promise, and no manifest or source route links.

Agent Instructions

Read the H1 and first section before judging visual design
Verify the linked machine endpoints exist
Compare homepage claims to manifest and LLM summaries
Run qa:fixtures after changing this pattern

QA Gates

npm run qa:fixtures
npm run qa:seo
npm run qa:aeo

Completion Criteria

Agent can explain entity and purpose from the fixture
Fixture links to machine discovery surfaces
Visible claims match schema and source notes