S
smithadifd/ledger
An append-only SQLite ledger for work items, decisions and the words they rest on, driven by one CLI for people and agents alike.
updated 2026-11-19
View on GitHub ↗Link checked 2026-11-17 · HTTP 200 · opens the vendor's own site
After install: how to tell it works
- What you see after install — The command exits 0 and the terminal shows no "command not found" or "permission denied".
- One-line self-check — Run the smallest usage example from that repository's README. If the output matches what the README describes, it is working.
- If that does not work — This project has no troubleshooting notes. Search its issues for "install".
The install command comes from the repository; these checks describe observable results only and do not replace the project's own docs.
- Star count
- 0 ★ · smithadifd/ledger · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-17 · last seen 2026-11-20 · seen 4× · listed by 2 sources
- Score
- score 203 · 2 sources · repo
- Install
- see Install & config above
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
smithadifd/ledger;first catalogued 2026-11-17;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# ledger
Excerpted from the repository README (abridged)
An append-only, hash-chained event log in one SQLite file, for the work items
of one body of work, the decisions made about them, and the words those
decisions rest on. One command, ledger, is the interface for people,
scripts and automated agents alike.
New here? docs/start-here.md takes you from nothing to a
working ledger, one step at a time.
## Why
A body of work leaves two kinds of record. One kind is prose a person edits
over time: a design note, a standard, a decision record. Its change is read
as a diff, and git is the right home for it. The other kind is things that
happen or exist: a ticket was opened, a question was asked and then answered,
an item was claimed, a review returned its verdict, a decision was taken on
these words. That record is appended, not edited, and each line of it needs
to say what wrote it and what it rested on.
Most tools keep the second kind of record in the first kind's home. The
status table in a planning file, the decisions section at the bottom of a
document, the checklist in a ticket description: each is state written in
place, and each is rewritten by whoever touched it last. When the writers are
a person and several automated agents, that goes wrong quickly. Two sessions
edit one table and one of them loses. A decision is stored as a summary, and
by the time anyone asks what it rested on, the words are gone. A tracker, a
notes file and an agent's memory each hold a copy of the state, and none of
them knows which copy is right. A resume note written at the end of one
session reads as fact to the next, with nothing to separate what was verified
from what was hoped.
The ledger keeps the second kind of record the way it should be kept: as
events, appended once, chained by hash, each stamped with what wrote it.
Current state is derived from the events and never edited. A decision quotes
the words it rests on, and the quote is checked against them. Every fact has
one owner, and the views that show a fact name the events they were built
from. Prose stays prose, in git, and the ledger points at it.
What that looks like in practice:
note and state append events; an item's status is a SQL view over its
events, and a correction is one more event. Nothing in the events table
is ever updated or deleted.
elect refuses a quote that is not a byte-exact substring of the captured
utterance it cites, and lint-quotes re-checks every election later.
card renders a resume card that names the events it was built from and
ends with "This card is a projection; the events are the authority".
Every write refuses without LEDGER_HARNESS, so the log always says
whether a shell, a scheduled job or an agent runtime wrote the line.
One database holds one system's work, and the file itself records which
system that is, so a work ledger and a personal one cannot be mixed by a
wrong path.
None of this is new. Built on says where the ideas came from.
## What this is
One SQLite file and one command. ledger has verbs that create
items, append notes, record questions, elections and decision records, claim
items with leases, render cards, search, export, back up and restore. It is
written against the Python standard library (3.11 or newer) with no runtime
of one body of work, the decisions made about them, and the words those
decisions rest on. One command, ledger, is the interface for people,
scripts and automated agents alike.
New here? docs/start-here.md takes you from nothing to a
working ledger, one step at a time.
## Why
A body of work leaves two kinds of record. One kind is prose a person edits
over time: a design note, a standard, a decision record. Its change is read
as a diff, and git is the right home for it. The other kind is things that
happen or exist: a ticket was opened, a question was asked and then answered,
an item was claimed, a review returned its verdict, a decision was taken on
these words. That record is appended, not edited, and each line of it needs
to say what wrote it and what it rested on.
Most tools keep the second kind of record in the first kind's home. The
status table in a planning file, the decisions section at the bottom of a
document, the checklist in a ticket description: each is state written in
place, and each is rewritten by whoever touched it last. When the writers are
a person and several automated agents, that goes wrong quickly. Two sessions
edit one table and one of them loses. A decision is stored as a summary, and
by the time anyone asks what it rested on, the words are gone. A tracker, a
notes file and an agent's memory each hold a copy of the state, and none of
them knows which copy is right. A resume note written at the end of one
session reads as fact to the next, with nothing to separate what was verified
from what was hoped.
The ledger keeps the second kind of record the way it should be kept: as
events, appended once, chained by hash, each stamped with what wrote it.
Current state is derived from the events and never edited. A decision quotes
the words it rests on, and the quote is checked against them. Every fact has
one owner, and the views that show a fact name the events they were built
from. Prose stays prose, in git, and the ledger points at it.
What that looks like in practice:
note and state append events; an item's status is a SQL view over its
events, and a correction is one more event. Nothing in the events table
is ever updated or deleted.
elect refuses a quote that is not a byte-exact substring of the captured
utterance it cites, and lint-quotes re-checks every election later.
card renders a resume card that names the events it was built from and
ends with "This card is a projection; the events are the authority".
Every write refuses without LEDGER_HARNESS, so the log always says
whether a shell, a scheduled job or an agent runtime wrote the line.
One database holds one system's work, and the file itself records which
system that is, so a work ledger and a personal one cannot be mixed by a
wrong path.
None of this is new. Built on says where the ideas came from.
## What this is
One SQLite file and one command. ledger has verbs that create
items, append notes, record questions, elections and decision records, claim
items with leases, render cards, search, export, back up and restore. It is
written against the Python standard library (3.11 or newer) with no runtime
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/smithadifd-ledger/)
- Source
- github · https://github.com/smithadifd/ledger
- Browse by field
- Open source
- Listed by
- 2 independent sources
- added
- today
More entries
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.