Capability evidence ledger

SRB tracks capability claims in docs/data/capabilities.toml. Code proves feature presence; runtime, real-data and hardware claims need evidence at the corresponding level. The ledger holds current records and blockers.

Promotion ladder

Capabilities advance through five ordered levels:

present
unit_verified
simulator_verified
real_data_verified
hardware_verified

A higher level requires evidence for all earlier levels. Blockers are not evidence.

Evidence identity

Evidence is tied to source and input identities; changes invalidate it. Historical reports do not establish current-tree status.

Local producer policy

Approved local gates record commands, inputs and outcomes as local-unattested. They support diagnosis, not CI, release, merge, readiness or hardware acceptance.

Local evidence runs

scripts/capability_gates/run_local.bash runs approved local end-to-end gates and reports their evidence and prerequisites. Use the governance gate for the overall result.

The checked-in ledger is authoritative without a current execution record. Local evidence cannot promote another commit or changed source scope.

Evaluation seam

srb.core.capability_ledger.evaluate_capability_ledger validates ledger data, source identity, evidence freshness and promotion order; it does not run tests or benchmarks. A clean report is not external acceptance or hardware qualification.

from srb.core.capability_ledger import evaluate_capability_ledger

report = evaluate_capability_ledger(
    current_code_sha=commit_sha,
    current_source_digests={"python-ci": source_sha256},
    evidence_paths=[evidence_path],
    run_id=run_id,
)

Persist report.to_json() to retain a local result. Its checksum provides integrity, not authentication.