stack/docs/compaction-refresh/governance/GATE0-PROBE3-EXEC-AMENDMENT.md

Gate0 Charter Amendment — Probe-3 (D4) Evidence-Class EXECUTION Authorization

Status: DRAFT (revision 2) — supersedes prior candidate pin 8fca5b7a; pending Mos re-scope-verify BEFORE re-pin is ratified. Revised per Mos adjudication directive (2026-07-18): §3 = D4-focused Option A; §1 = explicit binding model. Amendment type: Additive durable-authority amendment (does NOT mutate any ratified pinned doc in place). Milestone: 188 — Compaction-Refresh Mechanism · Issue: Gitea #827 (WI-0 Gate0) · gates WI-3 #830 merge.

---

1. Authorized source (why this amendment is valid)

Per the Mosaic governance principle (OpenBrain f0cb61b6, permanent; fail-closed / DO-178C): a durable Gate0 execution-hold clears ONLY by (i) explicit user (owner) authorization OR (ii) a durable-authority amendment from an authorized source. A runtime coordinator's verbal GO does NOT qualify.

• Owner authorization (i): Jason (owner / north-star) directed in #mos 2026-07-18 17:28Z — "amend the charter" (option B from the WI-3 escalation), quoting the escalation back. This is the direct-user authorization artifact that homelab's durable-Gate0 objection (2026-07-18 06:34:56Z) explicitly named as a valid resolution condition ("user artifact OR auth amendment"). Relayed + authenticity-adjudicated by Mos (web1:mos-claude). Owner outranks any peer-lane durable authority.
• Amendment (ii): this document, authorized BY that owner directive.

Both qualifying conditions are therefore satisfied. Homelab's stated condition is met by the owner artifact; homelab is NOTIFIED as a transparency step (it holds durable-Gate0 standing and raised the original catch), but its co-sign is not a gate (owner > peer).

Binding model (explicit — how this SHA is authorized). The authority binding for this amendment's pinned bytes is the composition of two distinct acts:

1. Owner class-authorization (PRE-SHA): Jason (owner) authorized the class of action — "amend the charter" (option B), #mos 2026-07-18 17:28Z. This occurred before these amendment bytes (and hence this SHA256) existed; the owner authorized the amendment, not a specific hash.
2. Independent-adjudicator byte-verification: Mos (web1:mos-claude), acting as the independent adjudicator (author ≠ verifier — MS-LEAD authored, Mos verifies), scope-verifies the exact bytes of this document and confirms they express only the owner-authorized narrow scope.

There is therefore NO single "Jason-signs-the-SHA" artifact, and none is required under this binding model: owner-authorized-class + independent-adjudicator-byte-verify is the binding. This is the durable, inspectable chain of custody for the pin.

2. Charter provisions amended (sha-pinned, unmutated)

This amendment attaches to — and does NOT rewrite — the ratified Gate0 charter provisions:

• compaction-refresh-BUILD-BRIEF.md §5 / R4 "Gate0 = BUILD-ADMISSION GATE", specifically the item: "Same-PID runtime_generation bump on reload/resume/fork revokes prior lease (D4)." sha256 89fdbc27ed0e5050dc7b52f3ef2ddaea691edf17fd89d51b15e26fb5ed47171b (intact/unchanged).
• compaction-refresh-SPEC-RATIFICATION.md R4. sha256 bac58319c9c4028b5b40e1129e0033cdb5a6b7b02033c25f06f4cb77d7779c67 (intact/unchanged).

The two pinned docs remain byte-identical; this amendment is the delta of record.

3. What is authorized (NARROW — D4-focused harness ONLY)

Adjudicator ruling (Mos, web1:mos-claude): "D4-only" against the existing runner is non-executable — the only runner (pi_gate0_run.py) drives P2+P5+P6+D4 in one flow, and D4 intrinsically requires a promoted-to-VERIFIED baseline (spec L219: "P3 immediately follows the valid P2 promotion so reload must revoke a genuinely VERIFIED prior gen") to revoke a genuine prior generation. Therefore authorize EXACTLY the minimal executable form (Option A) required as WI-3 (#830) merge-gate (2):

• D4-focused harness: spawns ONLY p3_generation_broker.py (not the full pi_gate0_run.py runner).
• Minimal promotion-to-VERIFIED, as a FIXTURE PRECONDITION ONLY: established solely so the D4 revoke has a genuine VERIFIED target. This is NOT authorization to bank P2 as an independent evidence class.
• D4 same-PID runtime_generation-bump revoke observation: new generation → MUTATOR_UNVERIFIED; prior (superseded) generation → STALE_GENERATION.
• Explicitly EXCLUDED: P5 (missing / oversize / hash-invalidation) and P6 (atomic-observation) — not needed for the WI-3 D4 gate and not authorized by this amendment.
• Isolation / integrity (per §4/§5): 3× repeated, isolated runs; hardened deterministic harness; non-destructive; launches broker/socket/state artifacts in an isolated fixture ONLY; does NOT touch production, mutates no live lease/broker/deployment, creates no durable side effect outside the fixture; a FAIL returns to planner — no retry-launder.

Intrinsic-precondition boundary (verbatim): the promotion step is a D4 test fixture, not a P2 evidence-gathering authorization; P5/P6 remain unauthorized.

4. What is NOT authorized (all other holds remain in force)

• This is NOT a blanket Gate0-execution release. Every other Gate0 execution item and every standing execution hold remains exactly as-is.
• No live mutation, migration, canary, deployment, systemd, tmux-fleet, or connector/socket/Hermes action is authorized by this amendment.
• Authorizes producing THIS evidence class once (3× isolation is the evidence-integrity requirement, not a license to re-run on failure): a FAIL returns to planner — no retry-launder, no severity-laundering.

5. Preserved fail-closed / DO-178C invariants (verbatim, unchanged)

• Producing probe evidence EXECUTES the Gate0 mechanism (launches processes, creates socket/state artifacts, exercises revocation transitions); "isolated + non-destructive" does not make it non-execution. This amendment authorizes that execution for the narrow class in §3 — it does not redefine execution as non-execution.
• A sha-pinned DURABLE authority OUTRANKS a runtime coordinator's verbal GO; when they conflict the durable artifact wins. This amendment derives its authority from the OWNER, not from a coordinator.
• Card-advancement gates and execution-holds are distinct; this amendment lifts ONLY the §3 execution-hold, not any advancement/review/SECREV gate. WI-3's independent-review + Opus-SECREV + green-suite gates stand.

6. Effect on WI-3 (#830) merge chain

On this amendment being pinned (Mos-verified + Jason-shown): a fresh lane (ms-rev-826) executes the §3 probe-3 evidence class (3× isolation) → PASS/FAIL reported to Mos. On PASS, and only after re-confirming WI-3 head f4008307 UNMOVED + FIRE-PRECONDITION-0 (fresh mosaic-context-refresh attestation for mosaic-100 + planner-opus), the existing chain runs: CI queue-guard → push → PR → mirror RoR → relay full-40 head + pr/ci# → Mos independent 6-check → squash closes #830 → chain WI-4→7. On FAIL: planner-return.

---

Amendment author: MS-LEAD (web1:mosaic-100), Gate0 governance interface / charter custodian. Pin protocol: this file's sha256 becomes the amendment pin ONLY after Mos re-scope-verify. Reported to Mos before any ratification/publication, per the transparency checkpoint on a durable-authority change. Ratification and durable publication (to a homelab-inspectable provider ref) are the adjudicator's (Mos), NOT the author's (MS-LEAD) — the author does not self-ratify and does not publish.