§55.1 Function

BAL-01 names the three activation postures of the civilization runtime. The posture is the single answer to the question "what is the runtime currently authorized to do?" Every other operational doctrine consults it.

§55.2 Postures

Three postures, exhaustively defined. There is no fourth.

1. §55.2.a
   A_read_only

   Runtime observes and reports. No state transition with civilization consequence may publish. All guardian blocks require explicit operator co-signature.

2. §55.2.b
   B_bounded_live

   Runtime executes within named, capped, audited bounds. Identity and doctrine guardian blocks may auto-pass; treasury and release blocks require co-signature.

3. §55.2.c
   C_autonomous_trial

   Runtime executes the full block set under recorded supervision. Every auto-pass is logged with the rationale that authorized it. Trial is time-bounded and reverts to B on expiry.

§55.3 Activation Posture Surface

The current posture is published, citable, and signed. Every consumer — guardian mesh, recovery, release governance — reads the same value from the same surface.

json
{
  "subsystem":     "kiri:system/activation_posture",
  "values":        ["A_read_only", "B_bounded_live", "C_autonomous_trial"],
  "transitions":   "GPL-01 ratified, signed, time-bounded for C",
  "consumers":     ["guardian_mesh", "recovery_repair", "release_governance"]
}

§55.4 Transition Discipline

A posture change is a ratified act under GPL-01. It is not a flag flip. Posture C is always time-bounded; expiry returns to B without further action.

§55.5 Bounded Scope

BAL-01 does not modify activation runtime logic, does not alter machine manifests, and does not introduce new APIs. It ratifies the posture taxonomy the runtime already implements.

§55.6 Final Principle

A civilization that cannot say what it is currently authorized to do has already lost the answer. BAL-01 keeps the answer published.

“Three rungs. Named. Gated. Reversible.”