free · local · open source · no account
lema redirects it — mid-session, with the decision and the why — so settled questions stay settled. Ten minutes, one command, your repo.
how it works
Nothing hidden. lema writes plain files into your repo, your agent asks before it acts, and you record as you correct.
One command, no account. Every file it touches is listed and yours to read.
Served as 240-char claims with pointers — not documents dumped into the context window.
The moment you fix the agent, the decision is captured — chosen is what you did, rejected is what it proposed.
The ask isn't a line in a prompt file the model can ignore — it's a PreToolUse hook that fires before the edit lands. Instructions are advisory; hooks are enforcement. And the why is read from your ADRs, PR threads, commits, and issues — not just the rare repo that kept ADRs.
why this is different
Code records what you kept — never what you tried and killed, or why. lema captures rejected alternatives at the moment of deliberation, then enforces them on every agent. And when someone hits a closed decision, it routes them to whoever owns it — supersede on purpose, not by accident.
smarter context, not blunt caps
To serve verdicts at decision time, lema had to become a context memory — atomized claims, pointers instead of copies, retrieval inside the session. That substrate is the second product: everyone else hands your AI a filing cabinet; lema hands it the verdicts — and the map to the cabinet, opened only on demand.
Decisions, ruled-outs, supersession, the guard — served back to every agent and every engineer at the moment of the next decision.
Content-agnostic by construction: decisions today — docs, repos, PRs, and connected sources next. Your corpus stays where it lives, under your permissions.
one build, two layers — judgment keeps the memory accurate; memory makes judgment affordable to serve.
In our adversarial research sweep, 21 of 25 vendor savings claims failed verification. The 90-percents died. The research direction stands — bounded memory beats transcript replay (arXiv:2601.11653, preprint) — but the only number we’ll print is ours: tokens-per-completed-task from the open enforcement-lift harness, with and without the graph attached, method public.
the whole product
The wedge ships today — the redirect, free and local. Every other surface below is the same graph, growing.
Never-reopen, live in the session — the wedge, working right now over MCP.
Store decisions as an append-only event stream — proposals, concerns, and resolutions — so we can replay how we got here, with the rejected options kept first-class.
Ruled out: a flat audit log — it captures the diff, not the why, and the agent kept re-proposing the killed option.
Argue it out once — the why, and what you ruled out, stay permanent.
“We are drowning in information, while starving for wisdom.”
— E. O. Wilson, Consilience (1998)
engineering first. the schema is industry-neutral by architecture.Runs local, no account, no lock-in. Works with any MCP client.
pricing
The redirect works the same at every tier. The paid line adds hosted memory and a pooled graph — it never takes anything away.