Endpoint Validity
Regeneration failures are silent. An endpoint that has been serving stale or broken JSON for a month looks exactly like one that is fine.
- Measures
- Each required endpoint parses as valid JSON, carries current protocol and lifecycle fields, and reflects what is actually published.
- Data Source
- Direct requests to the property's own endpoints.
- Indicates
- That the structural layer is alive rather than a snapshot from launch day.
- What Moves It
- Regenerating after every content change rather than treating generation as a one-time setup step.
- Does Not Prove
- Anything about content quality. This is a plumbing check, and it is the one most often skipped.
- Status
- Measured. Checked at build and worth re-checking after any content push.
The specific contradiction to look for: does the manifest advertise an endpoint that robots.txt blocks or the server refuses? Generating both from one declared source of truth makes that impossible rather than something to catch by hand.