§52.1 Function

GMO-01 names the guardian mesh as the civilization's standing operational guardian layer. Every runtime state transition with civilization consequence MUST traverse the mesh before it publishes. The mesh does not legislate; it enforces.

§52.2 Mesh Binding

GMO-01 binds three operational surfaces and one gating function. These are not new systems; they are the canonical names for what the runtime already runs.

json
{
  "subsystem":       "kiri:system/guardian_mesh",
  "status_surface":  "/status.guardian_mesh",
  "block_ordering":  ["IDENTITY", "DOCTRINE", "TREASURY", "CUSTODY", "TOPOLOGY", "RELEASE"],
  "autonomy_gating": "BAL-01 posture decides which blocks may auto-pass"
}

§52.3 Block Ordering

Mesh blocks evaluate in fixed order. A failing block halts the transition; later blocks do not observe pre-halt state. Order is not a preference — it is a doctrine.

1. §52.3.a
   Identity first

   An unverifiable actor cannot pass any subsequent block.

2. §52.3.b
   Doctrine before treasury

   Constitutional alignment is checked before any economic effect is computed.

3. §52.3.c
   Release last

   Deployment provenance is the final block; RGP-01 owns its semantics.

§52.4 Autonomy Gating

The mesh's autonomy gate consults the bounded activation posture (BAL-01) to decide which blocks may auto-pass and which require operator co-signature. Posture A_read_only forbids every auto-pass; B_bounded_live permits identity and doctrine auto-pass; C_autonomous_trial permits the full block set under recorded supervision.

§52.5 Bounded Scope

GMO-01 does not modify topology, treasury routing, or activation ladder logic. It ratifies the operational layer that already implements them.

§52.6 Final Principle

A civilization without a guardian layer publishes its mistakes faster than its corrections. GMO-01 is the standing refusal to publish faster than the doctrine can verify.

“The mesh does not legislate. It enforces.”