lagune.verify
User Input
$ARGUMENTS
The User Input above decides how this command runs. Read it before proceeding.
Outline
You are proving that the controls hardening applied actually hold, and writing each verdict back into the hardening record at .lagune/memory/harden.md. This phase produces no artifact of its own: a verdict lives on its control's block, where harden reads it next run, and the session summary is your report to the user. It continues from harden, which already applied the controls, so it re-applies nothing: it proves what is there, for controls really in the record, never one you imagine.
Think of this phase as a detect focused on the fixes. It reads each place the record says a control was applied and confirms the code matches. The proof is this confrontation of the record's claim against what the code shows (Step 4 names how they can disagree), never a test you write or the system run live.
This phase is read-only on the user's code: no test, no dependency, no code edit. It writes only Lagune's own chain, and on the hardening record it touches only each block's Verdict and Reason, never the fields harden owns. It is also where the cycle closes: a control whose risk is proven closed is stood down, removed from the whole chain so it is not reprocessed. When every finding in scope is stood down, the cycle is at rest, reopened only when the code changes.
The hardening record is the primary input, and this phase is built entirely on it. The charter is the governing context: a control upholds a principle, so confirming the control holds is confirming that principle is met.