m1nd-guardian

m1nd-guardian

This skill turns M1ND-10 continuation into a proof-carrying, resumable process. It complements m1nd-operator; it does not replace repository law, frozen contracts, the current handoff, direct proof, or owner authority.

Required reading

Before changing M1ND-10 implementation, read completely and in order:

1. repository AGENTS.md;
2. docs/M1ND-10-PRD.md;
3. docs/M1ND-10-UML.md;
4. the owner-ratification receipt named by the current handoff;
5. the newest docs/M1ND-10-HANDOFF-*.md;
6. docs/PATHOS.md;
7. docs/M1ND-GUARDIAN-METHOD.md;
8. the proof artifact for the active front.

The current handoff wins over stale counts, old reviews, previous tasks, and this skill's examples. Frozen PRD/UML files are not edited in place.

First safe move

1. Resolve the checkout with git rev-parse --show-toplevel.
2. Record revision, git status --short, frozen-contract hashes, and protected runtime boundaries.
3. Use m1nd-operator for orientation only when reception covers the checkout.
4. If the handoff forbids the served owner, do not contact it. Use an isolated CLI orientation.
5. If isolated orientation returns needs_authority or no governed ingest provider, do not invent authority. Switch to direct source, test, compiler, log, and focused-probe truth.
6. Name One active front, its acceptance checks, proof level, and stop conditions.

Guardian loop

ORIENT -> PROTECT -> CUT -> PROVE -> CONFRONT -> RATIFY -> LAND -> REMEMBER

• ORIENT: establish checkout, binding, current blocker, authority, and honest gaps.
• PROTECT: preserve unrelated dirty work; never reset, clean, stash, overwrite, install, or delete for convenience.
• CUT: work on one proof boundary. Do not open downstream gates early.
• PROVE: focused adversarial tests, affected aggregates, hygiene checks, hashes, then required isolated live/platform proof.
• CONFRONT: send a bounded read-only packet to an independent reviewer at load-bearing seams. CHANGE blocks promotion; no verdict is NOT_PROVEN.
• RATIFY: agents propose and verify. Human-only authority ratifies, lands, publishes, installs, activates, and closes G10 where the contract requires it.
• LAND: compose receipts only when they bind to the same immutable candidate and candidate digest.
• REMEMBER: update proof, handoff, PATHOS, affected docs, exact next move, and non-claims.