Pattern fixture

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.

Agent Question

Which visible facts are safe to expose through schema, and which facts must be blocked or sourced first?

Pattern Contract

Expose page facts through structured data that matches visible content and source-backed claims.

Visible Sections

Visible fact inventory
Schema type selection
Stable entity IDs
Relationship context
Source-backed claim references
Blocked schema examples
Source and claim notes

Metadata Checks

One H1 identifies the schema fixture
Title and description describe schema validation
Canonical route is stable

Schema Checks

WebPage schema names schema-backed-detail-page as the pattern
Schema facts are visible or source-backed
Entity IDs stay stable across related endpoints

Traceability Checks

Every schema fact maps to visible content, site config, or source traceability
Private or blocked facts are excluded

Source Evidence

src/data/agent-reference.ts: pagePatterns.schema-backed-detail-page
/schemamap.xml
/schema.json
/source-traceability.json

Good Example

The route lists visible facts, source IDs, schema type, entity ID, related schema endpoints, and blocked facts that must not appear in JSON-LD.

Bad Example

The schema endpoint adds credentials, hidden FAQ answers, private service areas, or unstable entity IDs not visible on the page.

Agent Instructions

Inventory visible facts before editing JSON-LD
Check source traceability for every schema claim
Keep entity IDs stable
Run qa:fixtures after changing schema-backed patterns

QA Gates

npm run qa:fixtures
npm run qa:aeo

Completion Criteria

Visible fact inventory exists
Blocked schema facts are named
Schema and source-traceability surfaces align