Evidence Model and Rules

Evidence tiers

Not all evidence is equal. Reports label each tier.

TierExampleProvesDoes not prove
declaredowner states "human review before send"what the owner saidthat it is true
observedopenai found in package-lock.jsonan entry exists in a fileit runs in production
digest-onlySHA-256 of a model cardbytes at recording timecontent is correct or complete
executedan assurance check ranbehavior on that input and hostother inputs
verified-by-named-reviewera named person reviewed evidencethat reviewer's judgmentanything about the reviewer's competence

Evidence record

id, systemId, kind, relativePath, sha256, sizeBytes, scope, recordedAt, expiresAt, verifier, limitations, status = reference-hashed-not-content-validated. File content is not copied.

Rule evaluation

Each rule returns exactly one status with a reason:

Example: a control verified-by-named-reviewer with an evidence ID that does not exist in the index fails GOV-004. The same control with an evidence item whose expiresAt is past yields unknown.

Exceptions

FieldRequirement
ruleIdthe rule being excepted
approver{name, type: "human"}; any other type is invalid
rationale, scopenon-empty
expiresAtvalid ISO date in the future

After expiry the finding is reopened and the reason says so.

Verifying evidence later

evidence verify re-hashes each file: ok, digest-changed, missing, expired, unsafe-path.

Audit chain

Sequential events chained by prevHash. audit verify reports issues by line: invalid JSON, sequence mismatch, previous hash mismatch, event hash mismatch. Not a signature or WORM storage.

Seals

Audit reports carry evidence.sha256 over canonical (sorted-key) JSON. verify --report recomputes it.