Four books that record what your agents and your people actually did — hours, decisions, provenance, price.
The gap is not waste — it is leverage nobody has a unit for yet. dira measures it;miara eventually prices it.
Two ship today, two are next — and the last ships warm, because its history has been accruing since your first tracked hour.
OpenSpec, GitHub Spec Kit, BMAD Method, superpowers units resolve into zavet living specs, and dira attributes the time behind each. Read-only — no new format.
One price for all four books — dira, zavet, proba and miara. You are billed per developer who actually recorded something that month, and for nothing else.
Solo work and public repos stay €0 forever — not a trial
dira is free forever for solo work and open source. Everything else is written on top of it.
Getting started →letopis is four products that write down agent-era software work: the time it took, the reasoning behind it, the process that governed it, and what the next one should cost. Hover the ring.
Most tools ask you to trust a number someone typed in. Every number here traces back to something signed and checkable: a session, a commit, a written decision, a merge. That is the only reason a client, an auditor or a CFO ever accepts it.
While your agents work, dira counts the minutes you were actually there — prompting, reviewing, approving. Run four agents at once and it still counts one you. Each hour is stamped with the commits it produced, so a client can click through and see the work.
Six months on, nobody recalls why exports stream row-by-row. zavet writes the reason down when the choice is made, keeps it in the repo next to the code, and blocks the next agent from quietly undoing it. Ask /zavet:why and get the answer in seconds.
Gold gets stamped 585, 750 or 999 for how much of it is really gold. proba stamps every merged pull request the same way — did tests pass, did a second person review it, which agent wrote it, how long you supervised. It reports; it never blocks.
Agents made your old estimates useless — the same feature now takes a fraction of the time. So miara ignores gut feel and prices new work from jobs you actually delivered, with real recorded hours. It gives a range, and below three similar jobs it gives no number at all.
Drag the agents to open the gap. Then walk the loop that closes it — four books, in order, each handing the next one something it could not otherwise know.
↺ the delivered job becomes the next comparable — which is why the ring closes
Agent time and engaged time are different things, so dira keeps them apart and anchors both to commits that provably exist in the remote. Engaged is the billable base; agent is what the harnesses burned while you watched.
The leverage exists because agents wrote a lot of code quickly. Decisions are captured as a byproduct of that work and guarded, so the next agent cannot quietly undo the thinking you were paid for — and the rationale is still there when Annex IV asks for it.
A hallmark witnesses the process per merged change — CI at the merge commit, a review by someone other than the author, the supervision minutes, no branch protection bypassed. The gap stops being a claim and becomes a record.
Billing 6h 18m is defensible, and it is less money. miara prices the next job from your own evidenced deliveries instead, so the leverage lands in the price rather than in a discount you never meant to give.
They are not five separate problems. They are one sequence, and the fifth answer feeds the first.
↺ what you delivered re-prices what you quote next
OpenSpec, GitHub Spec Kit, BMAD Method, superpowers units resolve into zavet living specs, and dira attributes the sessions and time behind each. Read-only — no new format, and your specs stay where they are.
Every deliverable the Act asks a software team for is a question about the past. A compliance project answers with archaeology. letopis answers with a lookup — because the answer was recorded while the work was happening.
The key design choices, including the rationale and assumptions made — dated, attributed, and guarded against the next agent.
Engaged supervision minutes per change, deduped across parallel agents. A number, not a policy page.
Design control and change control per merge: CI at the merge commit, non-author review, no branch protection bypassed.
The decision and change history of one subsystem, answered with citations in seconds rather than a fortnight.
letopis is not a compliance badge, not runtime logging and not legal advice — and it says so on the page. What it removes is the archaeology.
Two ship today, two are next — and the last one ships warm, because its history has been accruing since the third step.
dira counts the minutes you were actually engaged while Claude Code, Codex, Gemini, Cursor, OpenCode and Grok did the work — deduped across parallel sessions — then anchors every billable hour to commits a client can inspect.
Every decision behind your agent-built code, captured as a byproduct of the work — guarded against agent reverts, answerable with /zavet:why, and tied to the exact minutes it cost.
Proba mints a signed hallmark for every merged PR — CI state, non-author review, which harness wrote it, supervision-minutes spent, guards respected. It grades the process, never the code.
A quoting surface inside dira cloud that prices future work from your own recent, evidenced deliveries — ranges only, with n and spread, and a flat refusal below three confirmed comparables.
proba App only
CI state, non-author review, agent authorship inferred from trailers and bot accounts. Weak provenance — and labelled as such.
+ dira on the workstation
Cryptographically attributed sessions, which harness wrote it, engaged supervision-minutes per change. The layer a code host structurally cannot see.
+ zavet in the repo
Decisions referenced by the change; guards respected, not bypassed.
One price for all four books — dira, zavet, proba and miara. You are billed per developer who actually recorded something that month, and for nothing else — from two active developers up to fifty. Above fifty we quote per contract, because org-wide rollout is a different job.
Already tracking locally? Your existing data flows straight in, nothing to re-capture.
Everything in Team, plus proba's Enforce dial — org-wide rulesets, fail-closed available, break-glass recorded — and the whole stack inside your own VPC; SSO/SCIM, data residency, audit export.
Quoted per contract. You get the number on the first call, not the third.
dira is free forever for solo work and open source. Everything else is written on top of it.
Start tracking free →