compare · five questions

Every tool you already own answers one question and goes blind at the seam.

No single product covers the chain — just four categories of incumbent, each stopping exactly where the next question starts. Tap a question.

How long did this actually take?

YOU'D REACH FOR

Toggl, Harvest, Clockify

WHAT IT CANNOT SEE

Whether the timer was a human or a forgotten tab — and it never touches the artifact the hour produced.

dira

Who — or what — wrote this code?

YOU'D REACH FOR

git blame, co-author trailers, Copilot metrics

WHAT IT CANNOT SEE

The workstation. A trailer is a claim anyone can type; the code host cannot witness the session that produced the diff.

dira

Why is it built this way?

YOU'D REACH FOR

Confluence, Notion, ADR folders, kiro.dev specs

WHAT IT CANNOT SEE

Whether anyone followed it. A wiki page enforces nothing, and a generated spec is a plan the next agent run can quietly rewrite.

zavet

Was this change properly governed?

YOU'D REACH FOR

CI, branch protection, compliance collectors

WHAT IT CANNOT SEE

That a check ran is not that a human supervised. They record the gate, never the supervision behind the change passing through it.

proba

What should the next one cost?

YOU'D REACH FOR

Spreadsheets, story points, gut feel

WHAT IT CANNOT SEE

That its calibration died in 2024. Every input is a self-reported number from before agent leverage existed.

miara

CLOSEST NEIGHBOUR · KIRO.DEV

Kiro writes the spec before the work. letopis records what the work actually did.

The one product here we wouldn't call structurally blind — same premise, that agent output needs structure around it.

KIRO · SPEC-FIRST, IN THE IDE

→A plan generated before the code, inside one IDE.

→Nothing witnesses whether the plan was followed afterwards.

→No hours, no provenance, no price.

LETOPIS · RECORD-FIRST, AROUND THE REPO

●Decisions captured as a byproduct, then enforced on the next run.

●Hours and supervision witnessed on the workstation, harness-agnostic.

●A signed record per merged change that outlives the tool that made it.

Five tools, or one chain.

dira is free forever for solo work and open source.

Start tracking free →

compare · what you'd use today

Every tool you already own answers one question and goes blind at the next.

No single product covers the chain — just four categories of incumbent, each stopping exactly where the next question starts.

THE QUESTION	YOU'D REACH FOR	WHAT IT CANNOT SEE	LETOPIS
How long did this actually take?	Toggl, Harvest, Clockify	Whether the timer was a human or a forgotten tab — and it never touches the artifact the hour produced.	dira
Who — or what — wrote this code?	git blame, co-author trailers, Copilot metrics	The workstation. A trailer is a claim anyone can type; the code host cannot witness the session that produced the diff.	dira
Why is it built this way?	Confluence, Notion, ADR folders, kiro.dev specs	Whether anyone followed it. A wiki page enforces nothing, and a generated spec is a plan the next agent run can quietly rewrite to agree with itself.	zavet
Was this change properly governed?	CI, branch protection, compliance collectors	That a check ran is not that a human supervised. They record the gate, never the supervision behind the change passing through it.	proba
What should the next one cost?	Spreadsheets, story points, gut feel	That its calibration died in 2024. Every input is a self-reported number from before agent leverage existed.	miara

CLOSEST NEIGHBOUR · KIRO.DEVADJACENT, NOT BLIND

Kiro writes the spec before the work. letopis records what the work actually did.

Kiro is the one product on this page we would not call structurally blind. AWS built it on the same premise we did — that intent belongs in the repo, versioned, beside the code — and it is genuinely good at the half it owns. It is upstream of letopis, not instead of it. A spec is a stated intention; a chronicle is an observation. Only one of those survives contact with an agent.

KIRO · SPEC-FIRST, IN THE IDE

→.kiro/specs — requirements, design and tasks, authored before the code and tracked against it.

→Steering files apply team conventions to every agent action, first-class and versioned.

→Hooks fire on save and commit — inside Kiro.

✕Sees only work done in Kiro. The editor is the boundary. Your teammate on Claude Code is invisible to it.

✕Its artifacts are generated, unsigned and rewritable. Refine the design and the next run syncs over it. Nothing stops an agent from making the spec agree with the code it just wrote.

✕Cannot witness the merge. No CI state at merge, no non-author review, no supervision minutes — the IDE is on the wrong side of the pull request.

✕No hours, no client, no invoice. It prices agent credits, not the work. Nothing in it tells you what the feature cost or what the next one should.

LETOPIS · RECORD-FIRST, AROUND THE REPO

●Decisions captured as a byproduct of the work, then guarded — an agent that contradicts one has to surface it, not overwrite it.

●Every harness the developer actually used — Claude Code, Codex, Cursor, OpenCode. The git remote is the boundary, not the editor.

●Witnesses the merge: CI at the merge commit, review by a non-author, supervision minutes, no branch protection bypassed.

●Time, compute cost, client, invoice and the next quote all hang off the same signed session.

✓Signed at capture on the workstation, immutable after — which is what makes it evidence rather than documentation.

—And what letopis doesn't do: it will not write your spec, plan your tasks or steer your agent. Kiro is better at that than we intend to be.

Run both. A .kiro/spec is perfectly good evidence of intent, and zavet will cite it like any other decision record — a change that implements one reaches 999 fineness the same way. What Kiro cannot do is tell you whether anybody followed it.

AND THEN THE REAL PROBLEM

Buy all four categories and the interesting questions are still unanswerable.

Because they are questions across links, and five vendors share no key. letopis has exactly one: the signed session every other record hangs off.

pick a question →
same question, two stacks

YOUR STACK TODAY

Confluencethe decision page — no field a timer knows about

Toggl3h 12m against "API work" — no decision reference

Provider consoletoken spend by day, by nobody in particular

✕3 systems · 0 shared keys · unanswerable

LETOPIS

zavet · D-0042the decision, its guards, the paths it owns

dira · s-2481, s-2490the sessions that referenced it, signed

the joindecision ↔ session, same key

✓3h 12m engaged · 14h 02m agent · 612k tok — and the guard has blocked 4 reverts of it since

This is the only thing letopis sells that cannot be assembled from parts. Anyone can build a timer, a wiki or a CI check — nobody else can join them, because nobody else signs the session all four hang off.

Five tools, or one chain.

dira is free forever for solo work and open source. Everything else is written on top of it.

Start tracking free →The AI Act case →