§61.1 Existence Class
Operational organs are subordinate civilization modules that act under Runtime authority and depend on Treasury for sustainment. They are constitutionally named but operationally defined.
- §61.1.aSpace
Operational organ. Role and surfaces defined operationally.
- §61.1.bRadar
Operational organ. Role and surfaces defined operationally.
- §61.1.cLabs
Operational organ. Role and surfaces defined operationally.
- §61.1.dInsights
Operational organ. Role and surfaces defined operationally.
- §61.1.eFuture modules
Additional operational organs may be activated under GPL-01 without constitutional amendment.
§61.2 Relationship to Runtime and Treasury
Every operational organ derives execution authority from the Runtime and material sustainment from the Treasury. None operates outside that pair.
§61.3 Out of Scope
Implementation detail — endpoints, schemas, internal scheduling — is operational, not constitutional. The Constitution declares existence; the Runtime declares behavior.
§61.4 Final Principle
The Constitution names the organs. The Runtime gives them hands.
“Existence is constitutional. Implementation is operational.”
Operational Bindings
View system map →This article is not inert prose. It compiles into the following runtime systems, schemas, signals, and governance permissions.
- Civilization RuntimeL1 · RT-01Execution substrate that materializes ratified doctrine into running protocol state.runtimerpc / intentonlinekiri:system/runtime
- Sovereign TreasuryL3 · TRS-0188% sharded custody, fifty-year liquidity horizon, ledger-bound to swarm reporting.treasurysharded custodyonlinekiri:system/treasury
- kiri:spec/OCO-01Existence class for operational organs; implementation defined operationally.
- RT-01 · Civilization Runtime→TRS-01 · Sovereign TreasuryOperational organs derive execution from Runtime and sustainment from Treasury.
