The measurement
- Files scanned
- 595
- Schema
- canli.alphac-guards-that-cannot-fire.v1
Companion. artifacts/engineering/mutation_ledger.json, which answers the behavioural half by breaking what each guard over a published claim watches.
Detectors proven on a planted instance
- B
- yes
- C
- yes
- D
- yes
Refutations are kept. A finding that turns out to be legitimate stays in this artifact as REFUTED with its reason. An audit that keeps only its hits cannot be checked by anybody who was not there when it ran.
Shapes
- A
- a guard excluded from the environment meant to run it
- B
- an assertion inside a loop that can run zero times
- C
- an exemption naming a path that is not there
- D
- an existence-guarded block whose path does not exist
Why a clean report needs that. Every shape here currently reports zero, and zero is exactly what a scanner that has gone blind reports. Each detector is therefore run against a planted instance of the defect it looks for, and the audit refuses to publish a clean result it cannot demonstrate it earned.
Check it yourself
Every figure above is read from /glassbox/guards_that_cannot_fire.json, the
artifact the engine wrote.