Keith Soyka · evidence ledger · claims attested 2026-10-11

“Spreading knowledge is not packaged with the clean output. It’s the entire journey.”

A capability record that keeps the red beside the green: what failed, what changed, what the evidence proves, and where the boundary still sits.

434 → 37source rows merged into distinct claims
12 findingsfirst structured review fully dispositioned
5 exclusionsunsupported or gated figures kept out
43 sealed leaves37 claims + 5 registers + 1 review

The knowledge is in the change

Red-to-green record

Six places where the ledger became stronger by refusing a clean but incomplete story.

Claim index

Read the evidence, not the résumé

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 claims shown37 / 37 attested · attestation did not alter grades
No claims match this view. Clear the filters to return to the full ledger.

The ledger becomes the plan

Promotion criteria

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.

Strict grade transitions

Planned → Partial

Show existence: a named repository, file, package, or deployed surface that resolves and matches the claim’s stated scope.

Partial → Verified

Add independently checkable implementation evidence: executable behavior, test or run logs, a merged change, or corroboration beyond self-report.

Any promotion

Requires an explicit issuer verdict. No source count, model judgment, or passing test silently changes a grade.

Verified retention

Keep named evidence resolvable and preserve every scope boundary. If support disappears, the claim is re-graded rather than smoothed over.

Five source states

There

Named evidence was located and is checkable.

Not there

A named source was searched for but not located.

Planned

A spec, outline, or prototype exists; the claimed implementation does not.

Pending

A specific confirmation, run, or independent check is still required.

Future target

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.

14 promotion paths · 12 partial · 2 plannedhistory is append-only

Corrections go forward

What the ledger refuses

A trustworthy record is defined as much by what it excludes as by what it includes.

The journey is the knowledge.

Failure, fix, and implementation travel together so the next person does not repeat the same mistake.

Gaps are labeled, not filled.

Unverifiable figures are excluded or gated—not smoothed into plausible claims.

Corrections move forward.

Originals remain preserved in the corpus; the ledger records what changed and why.

Attestation is human.

The system assembles and grades. The issuer attests, edits, re-grades, or drops.

Evidence does not inherit conclusions.

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

First structured review

ChatGPT 5.6 (Sol, Deep Thinking) reviewed a static snapshot. Keith dispositioned every finding; the review never promoted itself into truth.

12
findings dispositioned

10 accepted · 1 noted · 1 deferred

What changed in v2

  • C-008 and C-017 were decomposed and re-graded from verified to partial.
  • C-013 now separates the implemented module from the spec-stage vision.
  • All evidence references carry access, independence, and reproducibility dimensions.
  • Public claim language is separated from derivation history and assessor interpretation.
  • The non-propagation invariant is now explicit: evidence status does not become conclusion status.
Open the sealed review record →

Portable verification

Verify the sealed ledger

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.

Seal ready to verify43 content leaves: 37 claims + 5 governing ledger files + 1 structured review.
Canonical Merkle root
da6bd04bbc1c948e8170ec3cfb75bdd0173fb5dff127a3430c954a46f4995642