Maximum interval from autonomous posture change to operator-bound board evidence.
荒坂株式会社
Autonomous force is accountable only when it leaves a receipt.
Rules-of-Force Ledger binds every SWARM-12 posture change to a named officer, permitted formation, civilian exclusion proof, rule basis, confidence field, and after-action evidence object before a machine act can persist as authorized force.
Every force-bearing state resolves to one named escalation officer before persistence.
Default sealed retention window for route proof, exclusion cells, sensor quorum, and after-action replay.
The ledger converts speed into an accountable chain of command.
Machine action becomes authorized force only after formation, exclusion, rule basis, officer binding, and evidence retention resolve to the same mandate.
FRM-01
Formation State Hash
Captures the exact veil, denial, overwatch, or extraction geometry the swarm occupied when authority changed.
EXC-02
Exclusion Proof Anchor
Attaches noncombatant uncertainty, medical lanes, property boundaries, and protected route cells to the force receipt.
OFC-03
Escalation Officer Seal
Binds a live human authority, command watchfloor, jurisdiction, and revocation window to each force-bearing state.
RPL-04
After-Action Replay Object
Packages sensor quorum, route state, exposure map, and command messages into a board-readable replay artifact.
A machine act is not authorized until the ledger can name its owner.
The ledger refuses persistence when formation, civilian exclusion, officer authority, permitted force class, or retention policy cannot be proven inside the same mandate.
Rules-of-Force Ledger routes SWARM-12 through formation geometry, civilian exclusion, route protocol, operations watchfloor, and board governance.
Formation defines the machine. Exclusion defines the negative space. The route protocol defines the movement. The ledger decides whether the resulting force can survive audit.
