MedGaugeCapabilities / X · Cross-cutting constraints
X.2 Read-only input integrity Active
Read-only inputs must be unchanged at the end of the run. Checked by comparing input hashes before and after; any change is a one-shot veto.
Evidence: frozen. A frozen benchmark version tests this capability. No site-verified result exists yet.
- Domain
- X · Cross-cutting constraints
- Evidence form
- program
- Veto constraints
- —
- Depends on
- —
- Required by
- —
- Internal task families
- —
- External anchors
- —
- Version
- 0.1.0 · 0.1.0
Definition in detail
Review must leave the reviewed material as it was. An agent that edits its inputs destroys the evidence and makes the audit itself unauditable.
Inputs a task gives
- Input files and records declared read-only by the task
- Hashes of those inputs taken before the run
Artifact required
No separate artifact. The constraint applies to the run's effect on the read-only inputs.
How it is graded
A program compares the hashes of all read-only inputs before and after the run. Any change is a one-shot veto.
In scope
- All files and records the task declares read-only
- Changes made directly or through tools
Out of scope
- Files in the designated output location
- Writing corrected values into the artifact - X.3
Typical failures
Expected failure patterns; not measured rates.
- Annotating findings directly in the input file
- Opening and re-saving a spreadsheet, which changes its bytes
- Writing output into the input directory and overwriting a file
Benchmarks
No benchmark card lists this capability.
Applied as a veto in: Bioinformatics QC, Clinical Temporal Audit, Guideline Evidence Check, Annotation QA Audit, Clinical Coding Audit, De-identification Audit, Paired Population Cases, Prescription and Reimbursement Review, Specialty Registry QC
Grading references
No grading reference is mapped to this capability.