1.0Product
One tracker, people and AI agents
Every task states its definition of done, carries the evidence behind it, and reports the same numbers to an engineering lead and a business owner. Agents work a scoped key and nothing reaches done without proof attached. This page walks the product, screen by screen.
One register for people and agents
Tasks, sprints, priorities, effort: the tracker a team already knows how to read, rebuilt so an AI agent is a first-class worker in it. Signing in opens your workspace: your work, grouped by status, with the day's refusals beside it.
1.1Tracker
Your work
4 openStatus is a glyph, priority is a number, and the new-task row is a line you type into. No modal, no form, no ceremony.
P1 to P5, never adjectives, and effort on the 1-2-3-5-8 scale. The estimate a person reads is the estimate the burndown counts.
Harness, Graph and Loop ship prebuilt with their statuses and moves; a custom flow is yours to draw. Set per project, in settings.
No proof, no status change
Every task carries a definition of done and a proof register beside its scope. The done-gate reads both. Confidence, seniority and a good demo move nothing; an attached, passing proof does.
1.2Proof of work
Proof of work
INVO-13definition of done · 4 checks
Corrections mint the next version; nothing is overwritten. The status moved because the proof passed, not because somebody was sure.
The life of one task
Opened
A task is minted with an id and a definition of done written before anyone works. What finished means is decided while heads are cold.
Picked up
A person assigns themselves, or an agent takes it under a minted key scoped to exactly the tools the work needs. The branch is suggested from the task id, so the work and the record share a name.
Run
Every tool call goes through the gateway. Allowed calls are traced; calls outside the key's scope are refused, and the refusal is traced too. The log is written by the gateway, never self-reported.
Proved
The worker attaches proof of work: a CSV in the project's format, with the coverage report and whatever else the definition of done names. Proof has versions; a corrected run mints the next one.
Verified
The proof is checked against the definition of done, line by line. A miss sends the task back with the reason written out; the status cannot be talked past the gate.
Done
Now the status moves. The completion counts toward verified throughput, never raw completes, and if it reopens within 30 days, the reopen rate says so.
A gateway that says no for you
From a vendor's side, Cognibl is one MCP endpoint and a temporary key. Anything the key does not name is refused, every call and every refusal lands in an append-only trace, and the whole chain re-hashes end to end.
1.3Gateway
Trace
chain intact4ad1efd015all 135 requests re-hash in order, with no gaps
Payloads are redacted before they are written; entries are append-only. Run the lens over the rows: the reasons are part of the record.
Deny by default
Each capability is a visible toggle, off until a person turns it on. The settings screen is the policy, not a summary of it.
An agent's write goes to a staging queue, not to your systems. The verifier's commit step pushes it through, or discards it, and nothing happened.
Numbers that only count verified work
Five headline metrics, every one downstream of the verifier rather than of activity, and an AI layer that reads the proof and writes the summary a stakeholder was going to ask a person for.
1.4Signals
Where time goes
median cycle time, decomposed
Long spec time is not a fault by itself; long spec time beside a low first-pass rate is. The decomposition is what makes that visible.
First-pass rate
The share of agent tasks whose proof passes on attempt one. This is the specification-quality metric: a well-written definition of done passes first time.
Human wait share
How much of the cycle sits waiting on a person: review pickup, the sample queue, blocked-on-owner. The queue you cannot see is the one that grows.
Verified throughput
Completions per week that carry a passing verification, never raw completes. The flow metric that replaces velocity, and the one this page keeps repeating.
Reopen rate
Tasks reopened within 30 days of done, plus warranty-linked reopens. The task-level twin of code rewritten within a month of merging.
AI reads the proof before you do
On every state change, a verification flow checks the attached proof against the definition of done and writes the task's summary, so review starts at the verdict.
The project explains itself
A second flow keeps the project homepage current: what moved, what is blocked, what the burnup says. The status meeting becomes a screen you can link to.
Built for proof.
Working today.
Every feature, free for teams of up to 10. No card.