Skip to content

Evidence and coverage

Documentation review, implementation, publication and business verification describe different facts. A page identifies its reviewed source revision in the source details. That revision is not a statement about the currently running application.

Fact Meaning
Implemented Present in a named code revision
Merged Included in main
Deployed Observed in a named component and environment
Verified A stated scenario passed on a stated version and target

Frontend, API and applied schema states can differ. Use current runtime evidence for a current-deployment claim. A dated receipt proves its recorded scenario and version. Reading a test file does not establish that its check was executed.

An overview-reviewed page has been checked against its listed sources at the declared overview depth. Initial topic summaries use this status with their limited scope stated explicitly. They do not establish detailed topic completion.

A section-reviewed article additionally meets its declared detailed acceptance criteria. Draft describes incomplete writing or review. Each topic’s detailStatus in the coverage register tracks whether detailed work is planned, draft or reviewed. Area summaries can therefore be available while all their detailed topics remain planned. Documentation status does not establish product readiness.

The repository’s docs/MAP.md identifies current document owners. CONTEXT.md owns domain language. Active topic contracts own detailed rules; code and active migrations establish implementation. Resolve clear disagreements in the owning source and record uncertain ones as concrete gaps.

ADRs retain decisions within their recorded status and scope. Archived research and superseded plans provide historical context. A proposal does not become an accepted decision through repeated quotation.

The HTML build contains selected pages, local assets, search and continuation files. build-info.json identifies the documentation build commit, reviewed product baseline and working-tree status. Each page retains its own source reference. Packaging requires a clean committed candidate.

Build, link and browser checks validate the handbook reader flow. They do not certify Toolora’s business behaviour. The coverage register and topic map identify all 85 reviewed answers and their separate evidence limits. NEXT.md now defines maintenance rather than another writing pass.