Document Ownership Matrix¶
Authority: Bluefly Engineering (hand-maintained; not generated from Portfolio-Registry.yaml) Scope: Canonical status and lifecycle of key documents within
Engineering-Standard. Excludes repository/platform ownership — see platform-ownership-matrix.md for those (repository-ownership-matrix.md was merged into it 2026-08-03, now archived at_ARCHIVE/REPOSITORY-OWNERSHIP-MATRIX.md). Status: Authoritative Last verified: 2026-08-05
Purpose¶
This matrix catalogs key documents within Engineering-Standard to determine their canonical status and lifecycle, resolving which document is authoritative when more than one covers the same topic.
Classification rules¶
- Canonical? —
Yesif this is the single authoritative document for its topic;Canon-Candidateif proposed but not yet ratified;Not establishedif unverified. - Duplicate? —
Yes/Noif a competing document was found and adjudicated;Not establishedif no duplicate-check has been run yet. - Lifecycle — one of the shared catalog status values: Operating, Implemented, Partial, Planned, Deprecated, Retired, Not established.
Active/Quarterlybelow denote review cadence, not lifecycle state, and are being reconciled onto this vocabulary as each row is re-verified.
Catalog¶
| Document | Canonical? | Duplicate? | Owner | Lifecycle | Evidence |
|---|---|---|---|---|---|
governance/documentation-implementation-boundary-contract.md |
Yes | No | Platform Governance | Operating | New 2026-08-19 — extends constitution.md's composition/implementation Axiom with directory-level rules for this repository; cross-linked from constitution.md and BLU-BIBLE.md, no prior document covered this specificity. |
operating-model/platform-priorities-doctrine.md |
Yes | No | Thomas Scola / Bluefly.io | Operating | New 2026-09-06 — delivered verbatim by Thomas via BLU; sits above the technical standards catalog and sets P0-P4 priority order and work-selection rule. Indexed from BLU-BIBLE.md. |
ledger/verification/nas-audit-2026-08-05.md |
Yes | No | Bluefly Engineering | Operating | OBSERVED 2026-08-05 — live SSH audit of blueflynas; all shares, containers, and snapshots verified. |
catalog/NAS-AUDIT.md |
Yes | No | Bluefly Engineering | Operating | OBSERVED 2026-08-05 — live SSH audit of blueflynas; all shares, containers, and snapshots verified. Distinct from ledger/verification/nas-audit-2026-08-05.md (merged from retired catalog/document-ownership-matrix.md 2026-08-25). |
governance/engineering-methodology.md |
Not established | Not established | Not established | Not established | OBSERVED 2026-08-19: file does not exist in this repository (live or _ARCHIVE/) despite this row's prior claim of VERIFIED/Operating. That prior claim was wrong — no file, no frontmatter to have checked. Four other documents still reference this path (decision-records/ADR-0008-upstream-authority-location.md, templates/decision-records/atomic-adr-template.md); those are separately flagged as broken links pending owner decision. |
standards/platforms/runtime/openclaw-mayor-operations.md |
Yes | No | Bluefly Engineering | Operating | VERIFIED via retrieval of explicit OpenClaw Gateway configuration rules and repository mapping. |
authority/executable-ownership-inventory.md |
Not established | Not established | Not established | Not established | File was indexed by qmd but requires further evidence to determine lifecycle. |
governance/canonical-infrastructure-convergence.md |
Not established | Not established | Not established | Not established | File was indexed by qmd but requires further evidence to determine lifecycle. |
standards/platforms/runtime/phase-6-bluefly-convergence.md |
Not established | Not established | Not established | Not established | File was indexed by qmd but requires further evidence to determine lifecycle. |
Relationships¶
This matrix governs documents; it does not govern repositories or Bluefly-vs-upstream capability ownership (both platform-ownership-matrix.md). When a document's canonical status conflicts with a claim made in another catalog file, this matrix is authoritative for the document itself, but the ownership claim's content authority is whichever matrix owns that domain.
Governance¶
Rows with Not established values require an evidence-gathering pass before promotion to Canonical: Yes or No. Do not resolve Not established by inference — only by direct verification of the target document.
Verification¶
Evidence classification (VERIFIED, or Not established pending review) is recorded per row above; no row is marked VERIFIED without a cited retrieval or content check.