Sample report · repo-proof-index · evidence handoff

Scattered proof needs an index.

`repo-proof-index` is the handoff point in the proof-surface stack. It turns contracts, receipts, and capability descriptors into a compact table or JSON surface a reviewer can actually inspect.

Surface

FieldValue
RepoHarperZ9/repo-proof-index
Surface classS:proof-index-tool
Review modePublic README, package manifest, and CLI behavior
AccessNo credentials, private files, or protected payloads

Output fields

  • kind: best-effort contract type.
  • surface: product, language, witness, root, or name.
  • status: status, maturity, verdict, or fallback.
  • evidence: short evidence summary.
  • path: source JSON path in JSON mode.

Evidence present

EvidenceStatus
Public READMEPresent and tightened with examples, non-goals, and pipeline role
Install commandPresent
CLI entry pointrepo-proof-index
JSON output mode--json
Workspace discovery mode--root .
Custom contracts directory--contracts-dir project-docs/contracts
Bundled examplesSample product, backend capability, witness receipt, and malformed input
Runtime dependenciesNone listed

Recognized shapes

  • Product use-case manifests.
  • Backend capability descriptors.
  • Witness receipts.
  • Generic JSON contracts with common claim/status fields.

What it does not do

  • It does not validate a JSON Schema.
  • It does not decide whether evidence is sufficient.
  • It does not decide whether a claim is true.
  • It does not read private payloads referenced by a contract.
  • It does not replace tests, audits, or release review.

Proof-surface verdict

CategoryStatus
LegibilityGood after README tightening
Bounded claimGood
Evidence visibilityGood foundation with sample contracts and malformed input fixture
Buyer usefulnessHigh for proof packet assembly and diligence handoff
Overclaim riskLow if schema validation and certification stay out of scope
Next actionAdd installed-package smoke evidence and CI pointer