10 accepted · 1 noted · 1 deferred
Keith Soyka · evidence ledger · claims attested 2026-10-11
A capability record that keeps the red beside the green: what failed, what changed, what the evidence proves, and where the boundary still sits.
The knowledge is in the change
Six places where the ledger became stronger by refusing a clean but incomplete story.
Claim index
Search the attested claim set, narrow by evidence grade or category, then open a claim to inspect its reasoning, evidence references, promotion requirement, and snapshot checksum.
37 / 37 attested · attestation did not alter gradesThe ledger becomes the plan
Every grade transition has a visible burden of proof. The fourteen claims below are not at the verified ceiling; each names the exact evidence event required to move without erasing its prior state.
Show existence: a named repository, file, package, or deployed surface that resolves and matches the claim’s stated scope.
Add independently checkable implementation evidence: executable behavior, test or run logs, a merged change, or corroboration beyond self-report.
Requires an explicit issuer verdict. No source count, model judgment, or passing test silently changes a grade.
Keep named evidence resolvable and preserve every scope boundary. If support disappears, the claim is re-graded rather than smoothed over.
Named evidence was located and is checkable.
A named source was searched for but not located.
A spec, outline, or prototype exists; the claimed implementation does not.
A specific confirmation, run, or independent check is still required.
Aspirational direction with no commitment date.
States describe evidence—not ambition. A category stays at zero when the current record contains no source of that kind.
history is append-onlyCorrections go forward
A trustworthy record is defined as much by what it excludes as by what it includes.
Failure, fix, and implementation travel together so the next person does not repeat the same mistake.
Unverifiable figures are excluded or gated—not smoothed into plausible claims.
Originals remain preserved in the corpus; the ledger records what changed and why.
The system assembles and grades. The issuer attests, edits, re-grades, or drops.
The existence or attestation of a supporting artifact never makes every conclusion drawn from it verified. Each conclusion carries its own burden of proof.
Review becomes part of the record
ChatGPT 5.6 (Sol, Deep Thinking) reviewed a static snapshot. Keith dispositioned every finding; the review never promoted itself into truth.
10 accepted · 1 noted · 1 deferred
Portable verification
The verifier re-hashes every sealed file in your browser, checks all 43 content leaves against the seal register, and rebuilds the Merkle tree. Nothing leaves this page.