stack/docs/compaction-refresh/governance/RATIFICATION.md

Gate0 Probe-3 (D4) Amendment — Adjudicator Ratification Record

Ratifies pin: 9ac9ff873fad41a6e15763cc89cb94d0bc4a6b0cf9b6770561d1781b03f63276 (GATE0-PROBE3-EXEC-AMENDMENT.md, 7699 bytes, this branch). Supersedes: prior candidate pin 8fca5b7a (never executed against; withdrawn on scope + durability grounds).

Re-scope-verify — PASSED

Verified by Mos (web1:mos-claude), acting as independent adjudicator (author ≠ verifier: MS-LEAD authored, Mos verified), 2026-07-18. SHA256 recomputed = pin (exact). Scope checks, all PASS:

• §3 = Option A, D4-focused: harness spawns ONLY p3_generation_broker.py; minimal promotion-to-VERIFIED is a FIXTURE PRECONDITION only (not P2 evidence-banking); D4 gen-bump revoke observation (new→MUTATOR_UNVERIFIED, prior→STALE_GENERATION); P5/P6 explicitly excluded + unauthorized; verbatim intrinsic-precondition boundary line present.
• §1 binding model explicit; §2 charter provisions pinned unmutated; §4/§5 invariants intact.
• No scope creep beyond the owner-authorized narrow class.

Authority binding

• Owner class-authorization (PRE-SHA): Jason (owner) — "amend the charter" (option B), #mos 2026-07-18 17:28Z. Authorized the amendment class before these bytes existed.
• Independent-adjudicator byte-verification: Mos scope-verified the exact bytes.
• No single "Jason-signs-the-SHA" artifact exists or is required under this binding model.

Round-trip integrity (this branch/commit)

All three files fetched back via the Gitea raw API and SHA-matched (each > 200B, no not-found sentinel):

• GATE0-PROBE3-EXEC-AMENDMENT.md → 9ac9ff87…f63276 ✓
• charter-BUILD-BRIEF.md → 89fdbc27…71b ✓
• charter-SPEC-RATIFICATION.md → bac58319…67 ✓

Status: RATIFIED — probe-3 execution remains HELD

Publication here closes the governance-infra gap (the charter provisions were previously local-only, not inspectable). Probe-3 execution stays HELD pending both: (1) homelab independent verification of these published bytes; (2) owner transparency window. On both clearing → ms-rev-826 builds + runs the §3 D4-focused harness (3× isolation, non-destructive) → PASS/FAIL to Mos → WI-3 (#830) chain per §6.

Note: the amendment file's own status line reads "DRAFT (revision 2)"; that internal text is superseded by THIS external ratification record (the pinned bytes are deliberately not edited, so the SHA stays stable). Ratification status lives here, not in the pinned artifact.