high-assurance-verificationlisted

Run the heavier pre-apply verification harness for a SENSITIVE change, one that is gate-blind on correctness (a fit or semantic property no existence gate can check), delicate at scale (a wide reshape or bulk mapping where a hand-edit is itself a defect risk), and costly to get wrong (a cited or downstream-relied-on artefact). Use before applying such a change, when the maintainer directs absolute-integrity rechecking, or when resuming a sensitive item left open in the register. It composes research fan-out, a mechanical signal pass over the negatives, two independent adversarial verifiers (false-negative and false-positive lenses, blind to each other and to the research), a programmatic invariant floor, and a deterministic scripted apply plus re-parse, so apply-correctness does not rest on the orchestrator's in-context precision. It catches the plausible-but-wrong value that survives every existence gate because the gate confirms the value is well-formed, not that it is right.
jposluns/grc_library · ★ 3 · AI & Automation · score 71

Install: claude install-skill jposluns/grc_library

# High-Assurance Verification (the sensitive-change harness) ## Project wiring (the parent library's instantiation; adopters substitute their own) Portable procedure, concrete names. In the parent GRC library this skill runs with: - Persistent register: the high-assurance register in the consuming project's working state, one row per sensitive item (the item, which trigger conditions make it sensitive, the stages run and their outcomes, the status). Open rows (`pending` / `in-progress` / `deferred`) are surfaced at session resume by the `/resume` command alongside the other standing registers, so an item survives a session boundary. - Motivating case: adding a control-framework column to the compliance matrix, where each cell carries a control code whose fit no existence gate can check. - Cadenced companion on matrix changes: the `/matrix-fit` semantic-fit audit (this harness at apply time, the cadence as the closing check). An adopting project maps each bullet to its own register location, resume-surfacing mechanism, and companion cadences; the procedure below refers to them generically. ## Overview Most changes are adequately protected by the routine layers: the research-assistant discipline (workers research, the orchestrator re-reads and authors), the mechanical gates, and the per-change and periodic sweeps. A small subset is not. When a change carries a correctness property no gate can check, is large or delicate enough that a hand-edit is itself a defect risk, and