Moves information from intake through source review, status assignment, verification, publication, staleness review, correction, and retirement.
Lifecycle
- Capture source and intended claim.
- Review authority, license, date, and conflicts.
- Assign status and target surface.
- Publish with source and limitations.
- Reverify on a defined cadence.
- Correct, narrow, deprecate, or retire stale claims.
Scope
This starter page defines the questions, boundaries, evidence, and failure modes that should be recorded before a capability is presented as supported.
Engineering considerations
- Identify the source, version, target environment, and owner.
- Separate observed values from estimates and externally reported values.
- Record trade-offs, unsupported cases, and fallback behavior.
- Link performance statements to a compatible benchmark methodology.
Verification questions
- What exact artifact, revision, backend, and environment were reviewed?
- Which assumptions could change the result?
- Which data should be retained so another engineer can reproduce the conclusion?