Six-tier sovereignty matrix
fix(architecture): add dated Correction callouts to 13 of 28 architecture/ articles, verified against canonical origin/main — repeated Apache-2.0-for-core-OSes license error (3 articles), fictional os-orchestration-graph design (already shipped differently), doctrine document citing a source that doesn't contain it (internally contradictory 52-vs-54 claim count), fabricated marketplace pricing, wrong Tier A model size contradicting sibling article, 4-tier pairing model repeating the how-to/ systemic defect; 11 verified clean, 4 already self-corrected
@@ -26,7 +26,7 @@ Every directory at the monorepo root falls into one of the following tiers: | Tier | Prefix | Purpose | Example components | |---|---|---|---| | 1 — Application | `app-` | User-facing surfaces — the personality cartridges that define how a job looks and feels | `app-console-input`, `app-mediakit-marketing`, `app-orchestration-command` | | 2 — Asset | `asset-` | Non-code resources — fonts, icons, 3D models, design tokens, brand assets | `asset-brand-pointsav`, `asset-brand-wcp` | | 2 — Asset | `asset-` | Non-code resources — fonts, icons, 3D models, design tokens, brand assets | `asset-brand-pointsav`, `asset-brand-wcp` (Correction, 2026-08-02, verified against canonical `origin/main`: no `asset-*` directory of any name exists in the monorepo — the whole 6th tier is a naming convention with zero real examples yet. Separately, this article's "Name supersession" table names `app-mediakit-distribution` (singular); the real directory is `app-mediakit-distributions` (plural). Flagged, not resolved.) | | 3 — Moonshot | `moonshot-` | Research and development experiments not yet promoted to production | `moonshot-gpu` | | 4 — OS | `os-` | Operating-system compositions — the runtime containers that load other components | [[console-os|`os-console`]], [[totebox-os|`os-totebox`]], [[os-orchestration|`os-orchestration`]] | | 5 — Service | `service-` | Background business-logic daemons | [[service-slm|`service-slm`]], [[service-content|`service-content`]], [[service-email|`service-email`]], [[service-people|`service-people`]] |