Decisions, limitations and system status
Toolora records decisions, active contracts, code, releases and scenario evidence in different sources. Their scope and status determine what can be concluded. A dated plan or receipt is not a current operating instruction. Test coverage and documentation completeness are also separate from the latest execution result.
Document ownership and decisions
Section titled “Document ownership and decisions”The documentation map identifies active topic owners. CONTEXT.md owns domain language; active contracts and implementation establish current behaviour within their scope. ADRs retain the decisions they record, including status and historical context. Resolve discrepancies in the owning source and record uncertainty until resolved. Operational transition still requires its own authority.
Document ownership and decision authority provides the detailed contract, examples and verification limits.
Known limits and open decisions
Section titled “Known limits and open decisions”A limitation identifies the affected behaviour and what remains unknown or undecided. It should not imply that a configured feature is verified or that missing data is a confirmed zero. Revised margin definitions and remaining recovery outcomes have separate owners. Reports and recovery documentation retain those boundaries.
Known limits and unresolved evidence provides the detailed contract, examples and verification limits.
Implementation and release status
Section titled “Implementation and release status”Implemented identifies code in a revision. Merged identifies inclusion in main. Deployed identifies an observed running component and version. Verified identifies a scenario that passed on a stated target and version. Frontend, API and schema states can differ. Exact-commit publication preserves these distinctions during delivery.
Implementation, publication and verification status provides the detailed contract, examples and verification limits.
Scenario evidence and coverage
Section titled “Scenario evidence and coverage”A receipt proves only its named scenario, revision, target and commands. Reading test code is different from executing it. A coverage label describes the existence or depth of checks rather than their latest result. Test execution defines where to find actual outcomes, while the handbook coverage register describes writing depth.
Interpret tests and delivery receipts provides the detailed contract, examples and verification limits.