Platform Truth
Platform Truth is the place to answer one question quickly: which surface owns the truth you are about to rely on?
It groups contracts, projections, docs-state integrity, and fail-closed operational truth so operators, integrators, and reviewers do not have to guess whether a page is descriptive, derived, or canonical.
Use this area when
- you need to know which repo or module owns a contract
- you need to distinguish public docs projection from runtime truth
- you need to understand why a page is blocked, stale, redirected, or fail-closed
- you are reviewing a change and need to confirm that public docs did not invent parallel truth
What Platform Truth owns
- docs-platform contracts and readiness posture
- event-modeling and projection boundaries
- trust, governance, and fail-closed integrity surfaces
- owner-clear links between public pages and their machine-readable source material
What Platform Truth does not replace
- product pages for install, configuration, and module-specific operations
- runbooks for day-two recovery and troubleshooting
- generated reference surfaces for APIs, events, schemas, or MCP detail
Start here first
- Docs Platform Truth for bundle, readiness, and docs-system ownership
- Event Modeling for platform event and projection boundaries
- Trust Center for trust, posture, and governance context
Typical reading sequence
- Start on a product or journey page.
- Switch into Platform Truth when you need ownership or contract clarification.
- Return to Operations or Products once the truth boundary is clear.