research-integrity-auditlisted

# Research Integrity Audit Audit without modifying the input. Treat `block` as a release stop, `warn` as a required review, and `pass` only as “no rule violation detected,” never as proof that a historical claim is true. ## Run From this Skill's own folder, so the command works both inside the repository and in a copy of the folder downloaded on its own: ```bash python3 scripts/audit_case.py \ path/to/research-case.json \ --output path/to/integrity-audit.json \ --pretty ``` Existing report paths are not overwritten. Exit codes are `0=pass`, `1=warn`, `2=block`, and `3=input/output error`. ## Interpret Read `status`, then `substance`, then `checks` and `findings`. Resolve every `block` before packaging. Review every `warn`, recording why it was resolved, accepted, or left unresolved. Preserve the report as an audit event and rerun after changing claims or evidence. ### Vacuous versus substantive `status: pass` alone never means a case earned anything. Read it together with `substance`: | field | meaning | | --- | --- | | `claims_examined` | how many claims the gate looked at, in total | | `substance.publishable_claims_examined` | how many carried `publication_status: publishable` | | `substance.substantive_claims_examined` | how many of those had at least one existing, non-HYP, non-generated evidence record | | `substance.level` | `substantive` when that last count is above zero, otherwise `vacuous` | | `publishable` | `true` only when `status` is `pass` **and*