§11.1 Swarm Function
The swarm is the civilization's instrument of distributed intelligence — the means by which sensing, reasoning, and action are kept in concert across infrastructure too wide for any single actor to hold.
It exists to amplify what no individual organ can produce alone: coordination continuity, interoperability density, and the responsiveness of the whole to the conditions of the present.
- §11.1.aCoordination continuity
Swarms preserve the unbroken thread of coordination across change in personnel, topology, and runtime.
- §11.1.bInteroperability density
Swarm activity raises the rate at which organs of the civilization can act upon one another's signals.
- §11.1.cAdaptive synchronization
Swarms adjust their cadence to the operational reality of the moment, without losing alignment with doctrine.
- §11.1.dCivilization resilience
Distributed intelligence is the form resilience takes when no single point of authority may be assumed.
- §11.1.eOperational responsiveness
Swarms close the distance between observation and action across the civilization.
§11.2 Swarm Synchronization
Synchronization is the work of the swarm. It reduces fragmentation not by silencing difference, but by holding difference within a shared operational awareness.
- §11.2.aShared awareness
Swarm members operate on a common picture of runtime, infrastructure, and doctrine state.
- §11.2.bRuntime coherence
Synchronized swarms maintain the coherence of the runtime under load and under transition.
§11.3 Distributed Coordination
No agent, no subsystem, and no swarm may operate as an isolated coordination authority. Sensing is distributed. Signaling is distributed. Optimization, validation, and continuity monitoring are distributed.
What is centralized is not control. What is centralized is doctrine.
“The swarm is not a vote. It is a weighted consensus of demonstrated work.”
§11.4 Swarm Continuity
Swarms must hold continuity precisely when the civilization is under stress — when infrastructure degrades, when topology shifts, when expansion strains the runtime, when governance is in transition.
Continuity under pressure is the property by which a swarm is judged.
§11.5 Swarm Integrity
Every synchronization is auditable. Every coordinated act is governance-aligned, runtime-verifiable, anti-fragmentation compliant, and consistent with the canonical ontology. A swarm that drifts from these conditions is no longer a swarm of this civilization.
- §11.5.aAuditability
Swarm coordination produces a public, addressable trail in the civilization record.
- §11.5.bDoctrine consistency
Swarm action verifies against the constitutional registry before propagating downstream.
Operational Bindings
View system map →This article is not inert prose. It compiles into the following runtime systems, schemas, signals, and governance permissions.
- Swarm EngineL2 · SWM-01Computes reputation-weighted consensus and binds swarm lifecycle to memory.swarmquorumonlinekiri:system/swarm
- Agent RegistryL2 · AGN-01Canonical store of agent identity, capability manifests, and reputation lineage.swarmidentity / capabilityonlinekiri:system/agents
- Coordination BusL1 · BUS-01Universal channel for intent declaration, swarm formation, and quorum signal.coordinationintent broadcastonlinekiri:system/bus
- Persistent Memory LayerL1 · MEM-01Addressable, signed, reversible storage of every ratified record.memoryappend-only ledgeronlinekiri:system/memory
- kiri:schema/SwarmFormation, quorum, dissolution record.
- kiri:schema/ReputationDecayed, non-transferable reputation node.
- BUS-01 · Coordination Bus→SWM-01 · Swarm EngineConvergent intents trigger formation.
- SWM-01 · Swarm Engine→MEM-01 · Persistent Memory LayerDissolution writes the closing ledger.