Sovereign OS — Platform Map
Who is this for? Pick your lane.
- **Stakeholders / product owners →
S-files.* Plain language, no jargon, status and money talk. Start at S-01 Overview, then S-02 Program, S-03 Glossary, S-04 Week in Review. - **Operators / administrators →
A-files.* Stack topology, recovery playbooks, billing ops. Start at A-01 Deploy Topology, then A-02 Runbooks, A-03 Billing Ops. - **Developers →
D-files.* Architecture, schema, APIs, conventions. Start at D-01 Architecture, then D-02 Core Concepts, D-03 Strata & SurQL, D-04 Data Fabric.
Stakeholders
| File | What it answers |
|---|---|
| S-01 Overview | What is this platform, in one page of plain language? |
| S-02 Program | Which work is done, blocked, or waiting on a customer? |
| S-03 Glossary | What do all the acronyms mean? |
| S-04 Week in Review | What did the last week teach us? Plain-English summary of the retrospective. |
Administrators
| File | What it answers |
|---|---|
| A-01 Deploy Topology | What is running where, on which port? |
| A-02 Runbooks | How do I fix X when it breaks? Step-by-step playbooks. |
| A-03 Billing Ops | What gates the billing production migration? |
Developers
| File | What it answers |
|---|---|
| D-01 Architecture | What is the design thesis and how are the planes split? |
| D-02 Core Concepts | CNS, claims, truth graph, PoCE, scope, quorum. |
| D-03 Strata & SurQL | Schema layout, deploy order, 3.0.5 constraints, canonical tables + functions. |
| D-04 Data Fabric | NATS bus, KV config plane, outbox + relay, the spine consumer. |
| D-05 Claims Plane | Guarded transitions, packs, desks (panel/SLA/quorum/VAS/intake), consumer, metrics. |
| D-06 FINMON | Monetization: split profiles, voyages, entitlement, wallet, dual-control. |
| D-07 CAPSRC & INTRQ | Capability supply sourcing + interaction requests. |
| D-08 Config Federation | FCT protocol, cells, tracks, cells/evidence. |
| D-09 BFF Surface | The agent-bff route inventory + runtime (consumers/relays). |
| D-10 Truth + Sovereign API | Truth BFF surface/guards, Sovereign API + ZTDS/AfiyaLink/UIC. |
| D-11 Spec Index | OpenAPI specs, versions, parity rules, how to add a route, where the full references live |
| The generated API reference set | Rendered OpenAPI references — one file per spec with every operation plus the verbatim spec JSON; regenerated by scripts/render-platform-map-api-docs.mjs |
| The complete API inventory | Measured implementation coverage — every HTTP route in the codebase, marked covered or uncovered vs the specs; regenerated by scripts/extract-api-inventory.mjs |
Jijibora (smart city)
| File | Audience | What it covers |
|---|---|---|
jijibora/README.md | all | The Jijibora set's own master index |
jijibora/S-01-OVERVIEW.md | stakeholder | What Jijibora is; pilot shape; delivery commitment |
| S-02 — What Jijibora Can Do for You (plain-language feature guide) | stakeholder | The capability catalog, buyer by buyer |
| S-03 — Jijibora Playbook Registry (stakeholder + developer) | stakeholder | The playbook registry — processes, guardrails, audit output |
| S-04 — Security and Fairness: What We Can Promise and What We Cannot (plain-language guide) | stakeholder | Security & fairness: promise inventory vs published limits |
| Jijibora Competitive Positioning — Buyer's Language | stakeholder | Market features the category expects; what we meet / don't claim |
| S-06 — Environmental Playbooks (for stakeholders) | stakeholder | Environmental reflex playbooks (building, sourcing, civic rounds, SOS, sensing) |
| S-07 — Starter Packs for Stakeholders | stakeholder | Day-1 starter bundles + the 14-day pilot commitment |
| A-01 — Jijibora Deployment (Administrator Operations) | administrator | Stack, Soft posture, rollout rituals, what to watch |
| A-02 — Jijibora Compliance Operations (Administrator) | administrator | Audit trail retention, data minimization, incident posturing |
| A-04 — Environmental Ops (administrator) | administrator | Reflex enablement, capacity probes, the hurt-playbook ladder |
| A-04 — Starter Packs for Administrators | administrator | Bundle activation, rollback, Soft→live gate ritual |
jijibora/D-01-ARCHITECTURE.md | developer | Jijibora design: control loop, reflex model, backbone, ontology, non-goals |
| Jijibora Features → Interfaces Map | developer | Planes + interface surfaces + three worked integration walks |
| D-04 — Environmental Playbooks (developer) | developer | Reflex family contracts + the authoring recipe |
| D-05 — Starter Packs for Developers | developer | Pack anatomy, bundle composition, cold-vs-live rollout, authoring |
| D-12 Camel Gateway | Protocol-translation gateway, claims routes, dispatcher. | |
| D-13 Verticals | KaziSasa, Kutuma, Matterra/Kujenga/MARS/GenMfg, SKU matrix. | |
| D-14 Dev Workflow | Stack-up, conventions, test layout. | |
| D-15 Honesty Invariants | The fail-closed rules every module must obey. | |
| D-17 Backlog Validation | Every recommendation from the week review, re-checked against the live repo. | |
| D-16 Changelog | 180 days in 2,004 commits. | |
| D-18 Branch Audit | Branch inventory vs main, prioritization and hygiene playbook. |
Status at a glance (2026-11-09)
- Commercialization backlog: every buildable card done. Remaining items are all ops-gated (TSA at FCT-18, PSAP at INTRQ-20, Kill Bill prod at FINMON-16).
- Claims plane runs end-to-end live (create → guarded transition → outbox → relay → spine consumer → receipt); product rollout stays deliberately Soft.
main=program-backlog=origin/main(all at latest merged commit; tree clean).
Exclusions
External-database migration history is excluded from this doc set (canonical store is SurrealDB + NATS everywhere).