Assurance and Evidence

How to check what GovernSutra 0.2.1 claims, without trusting the author.

Independent-style audit

governsutra audit --out DIR runs 31 checks and writes a sealed report in JSON, Markdown and HTML. The verdict ASSURANCE_CHECKS_PASSED_HUMAN_REVIEW_REQUIRED here means every executed check behaved as specified on this host. It is not an approval. Skipped checks (1) are listed, not counted as passes.

Open the sample audit report (HTML), Markdown or JSON.

Evidence tiers

ArtifactTierProvesDoes not prove
Assurance checksexecutedbehavior on listed inputs, this hostother inputs or hosts
Hash-chained audit logtamper-evidentaccidental or partial edits detectableauthorship; whole-file rewrite by an admin
Evidence referencesdigest-onlybytes matched at recordingcontent is true
Owner declarationsdeclaredwhat was statedaccuracy
Scan candidatesobservedan entry exists in a fileproduction use; completeness
Risk scoreheuristictransparent weighting of declared inputslegal risk, safety

Proof files

FileContent
test-run.tapRaw TAP output of 80 tests
fuzz-results.jsonSeeded fuzzing counts and invariant results
environment.jsonVersions and counts
SHA256SUMS.txtDigests of every proof file
CLI transcriptsReal command output including refusals

Verify the digests: sha256sum -c SHA256SUMS.txt in the proof folder. Verify the seal: governsutra verify --report audit-report.json.

Sample outputs

Not tested / not claimed

How to challenge this project

Run the audit on your machine. Break a check by editing the code or an input, and confirm it fails. Open an issue with the failing command. Failures found by others are welcome and will be added as tests.