grace-verificationlisted

Design verification that autonomous agents can trust: deterministic where possible, observable and traceable where equality checks alone are not enough. ## Prerequisites - `docs/development-plan.xml` must exist with planned modules or module contracts - `docs/verification-plan.xml` should exist; if it does not, create it from the GRACE init template before proceeding - if `docs/operational-packets.xml` exists, use its `FailurePacket` shape for failure handoff output - Read the relevant `MODULE_CONTRACT`, function contracts, semantic blocks, and existing tests first - If no contract exists yet, route through `/grace-plan` before building verification ## Goal Verification in GRACE is not just "did the final value match?" It must answer: - did the system produce the correct result? - did it follow an acceptable execution path? - can another agent debug the failure from the evidence left behind? - is the module safe enough to hand to a longer autonomous run without relying on hidden model reasoning? Use contracts for **expected behavior**, semantic blocks for **traceability**, and tests/logs for **evidence**. `docs/verification-plan.xml` is the canonical place where this evidence model lives. ## Process ### Step 1: Load Verification Context Read the smallest complete set of artifacts needed for the scope: - `docs/requirements.xml` - `docs/technology.xml` - `docs/development-plan.xml` - `docs/verification-plan.xml` - relevant source files and nearby tests When operating