Provenance
Provenance mode: synthetic. This page combines portable failure patterns into a hypothetical implementation. It contains no private incident detail, performance metric, customer result, or certification claim.
The starting condition
Imagine an agent-built publishing system with many route pages and several independently developed renderers. Each change is locally reasonable, but the system has no shared answer for four questions:
- which state is authoritative
- which pages have earned claims, links, and schema
- which agent may write which boundary
- what evidence makes a release complete
The predictable result is drift: one module withholds a claim while another emits it, status channels disagree with source freshness, and a merged fix is mistaken for a served fix.
The implementation pattern
Start with the five portable contract families:
- Declare page tiers and their evidence requirements.
- Give each enrichment stage one writer and an explicit gate.
- Derive the link graph from eligible targets.
- Separate materialized write state from read-time rendering.
- Define acceptance in terms of the served surface and a replayable receipt.
Then attach falsifiable invariants to the failure classes. A probe that lacks required evidence returns
UNMEASURED, not PASS. A network probe also declares its mutation_class, because a read-through cache or self-healing
path may change the corpus during observation.
What a successful adoption would demonstrate
A named, timestamped public receipt could support claims such as:
- all declared pages in a pinned cohort were evaluated
- every published claim traced to one source decision
- suppressed claims were absent from visible and machine-readable surfaces
- the promoted generation matched the generation served on the wire
- a deliberately broken fixture caused the relevant gate to fail
Until such a receipt exists, these remain acceptance criteria—not results.
What remains private
Portable contracts, validators, synthetic fixtures, and public documentation belong in the public framework. Entity registries, route maps, operational thresholds, prompt systems, production incidents, and private evaluation baselines remain in their implementation repositories.