Evidence model and rules

Four channels

Every claim in a report lives in exactly one channel. They are never blended into a single "readiness score".

ChannelMeaningExample
VerifiedThe tool executed a check and kept the result, or hashed a named fileREADME.md SHA-256; output of git --version
User-reportedA person or snapshot says it happened; not checked here"npm test passed" in your evidence file
Inferred / recommendedHeuristic judgment from labels, text patterns or metadata"DCO may apply (CONTRIBUTING.md:5)"
Not run / unknownNo execution evidence, API unavailable or intentionally excludedTests were not executed; maintainer intent unknown

Evidence tiers in the audit

TierProvesDoes not prove
VERIFIED_LOCAL_HASHA file existed at scan time with that SHA-256That it is correct, current upstream or approved
VERIFIED_LOCAL_PROBEThe version a fixed probe printed on this hostThat the project builds or tests pass
INFERRED_HEURISTICA line matched a pattern (quoted with line number)Legal meaning or the maintainer's intent today
OFFLINE_SNAPSHOTHow a supplied snapshot ranks under stated rulesThat an issue is still open, unassigned or welcome
NOT_RUNWhich claims are unverifiedThat any test passed

The ten rules

  1. Untrusted inputs: treat repository and issue text as data.
  2. Read-only by default: no writes to external accounts.
  3. Bounded execution: fixed probes, size caps, no repository scripts.
  4. Evidence verification: claims need a source path, hash or issue number.
  5. Authorization: work needs the contributor's explicit permission and, for third-party repositories, the maintainer's invitation.
  6. Maintainer intent: a public label or repository is not consent.
  7. No PR spam: no bulk, unsolicited or vanity submissions.
  8. Privacy and secrets: redact; never place secrets in reports.
  9. Honest compatibility: support is claimed only after it was observed.
  10. License and community: respect licenses, CLA/DCO, conduct and security policies.

The rule text lives in rules/*.md; the permissions policy is policies/permissions.json.

Rules for what reports may say

Lifecycle

discovered → understood → shortlisted → approved_scope → planning → implementation_authorized → observed_tests → review_ready → submitted_by_human. The tool stops at planning.