docs: add ledger evaluation path#98
Merged
Merged
Conversation
ChelseaKR
marked this pull request as ready for review
July 18, 2026 15:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Ledger had a working demo and release workflow, but no short public path from evaluation to adoption readiness. These docs make the existing evidence usable without overstating what it proves.
Validation
make demopassed (synthetic no-outing proof)make verifypassed (1,005 tests plus lint, types, i18n, accessibility, dependency, secret, claims, and workflow checks)Release note
This PR intentionally does not create or tag
v0.1.0. The new checklist keeps the release blocked until PyPI trusted publishing, signed-tag identity, and actual independent security/accessibility review evidence are complete.