Document ownership and decision authority
Source authority depends on the question being answered. An accepted product rule, executable implementation, current operating procedure and historical receipt serve different purposes. Find the owning source before resolving a disagreement; quoting a document repeatedly does not expand its authority.
The repository’s documentation map routes current contracts. CONTEXT.md owns domain vocabulary. The working agreement establishes current environment and execution boundaries. Code, active migrations and tests establish what a named revision implements, including possible defects against an accepted rule.
Authority reference
Section titled “Authority reference”| Question | Owning evidence | Important limit |
|---|---|---|
| What does a domain term mean? | CONTEXT.md and accepted domain decisions | A UI label or imported column does not silently redefine it |
| What is the agreed rule? | Current topic contract and accepted ADR within scope | Proposed/superseded decisions retain their status |
| What does this revision do? | Code, migrations and relevant tests | Implementation can contradict the accepted rule |
| How is work performed now? | Current development/deployment/runbook owner | A dated delivery receipt is not a current command sequence |
| What is running? | Current component/schema observation | Main or a branch name is insufficient |
| What passed? | Named execution receipt and actual target/version | Coverage labels or test source are insufficient |
| What remains accepted or unresolved? | Current issue/decision state plus scoped evidence | A stale status index cannot establish current closure |
Resolve a disagreement
Section titled “Resolve a disagreement”First state the conflicting claims and their exact scope: identity, environment, operation, revision and time. Check the current owner through docs/MAP.md. Read the ADR’s status and any superseding decision. Inspect implementation when the question concerns actual behaviour, not only intended design.
A clear documentation contradiction can be corrected in the owning source with source-bound evidence. An established code defect needs the authorized implementation, negative/positive checks and relevant publication. An unresolved product definition requires human judgement; record the concrete decision instead of choosing an attractive interpretation.
A proposal remains a proposal. The shared-infrastructure adoption document can guide discussion without authorizing a connector cutover, new collector or shared recovery. Infrastructure ownership describes the accepted discovery/adoption boundary.
Current instructions and historical observations
Section titled “Current instructions and historical observations”Current Toolora instructions declare pre-launch shared testing and a real Vi Målar Fortnox binding. Older references to production, retired test hosts or earlier provider bindings do not authorize present actions. Preserve dated receipts as historical facts and use the current environment contract for a new action.
Likewise, a successful historical schema adoption does not permit rewriting a migration already on main. The current migration/runbook contract owns that action. An inventory or graph can help locate the owner, but stale relationship text cannot override current repository instructions.
Synthetic conflict example
Section titled “Synthetic conflict example”A recovery note suggests supabase db diff, while the current schema contract says it cannot reliably represent the complete schema. The relevant implementation is schema_catalogue.py; the owning recovery procedure must use a generation-bound catalogue comparison before compatibility migrations. Correct the current procedure while preserving the historical receipt’s original comparison and limits.
A different conflict might concern a report’s future margin definition. Current calculations can be documented precisely, but an open definition must stay open. Known limits records the missing decision rather than deriving policy from the existing chart.
Maintenance and verification
Section titled “Maintenance and verification”Link one canonical explanation instead of copying operational rules into several pages. Update related articles when an accepted contract changes and preserve stable topic IDs/old anchors. Each source review records a full revision and real source paths. Status and evidence distinguish implementation, publication and scenario results. The handbook’s reviewed status means its writing scope was checked, not that every product decision is settled.