Done is proven, not declared
Done is proven, not declared.
Every acceptance check is ticked with evidence: the pull request, the test run, the commit. A done ticket counts as Verified only when every check passed, no pull request is still open and nothing is waiting for review.
Export a month of logged hours as CSV
Acceptance checks
4 of 4 provenGiven a manager, when they export March, then the file has one row per person and day
Pull request #381 via AI agentThe totals match the monthly overview
Test: npm test: 14 passed via AI agentA member cannot export someone else’s hours
Pull request #381Test: npm test: 14 passed via AI agent10,000 rows export in under 2 seconds
Test: 10,000 rows in 0.6 s via AI agent
Pull requests
Show the cost center on project cards
Done, not verified yet:
• Pass the last check with evidence
• Merge or close the open pull request
Export a month of logged hours as CSV
Show the cost center on project cards
Totals off by one day in March
The ticket key in the branch, title or description links the pull request.
The app’s own components, rendered with example data.
Evidence on every check
Agents must attach evidence to pass a check: a pull request, commit, test run or link, or the test that ran and its result. When a person passes a check in the app without evidence, it counts as Confirmed by that person. A failed check needs a note that says what failed.
Verified, or exactly what is missing
Done tickets show Verified or Not verified. The tooltip lists what is still needed, for example “Pass the last check with evidence” or “Merge or close the open pull request”. Verified tickets carry a shield mark on boards and in the backlog.
Pull requests move tickets
Connect GitHub, GitLab or Bitbucket and put the ticket key in the branch, title or description. Opening a pull request moves its tickets to In review; merging the last open one moves them to Done.
- Agents can link pull requests over MCP on every plan.
- One pull request can carry several tickets, and one ticket can have pull requests in several repositories.
Docs that can’t drift
Every product keeps its documentation next to its tickets: pages in Markdown with search, on every plan. On Business, a merge makes AI propose updates to those pages that must quote the diff or the ticket, and the server checks each quote character for character before anything is shown. A person applies them, and each page names the pull request it was last checked against.
- A page edited by hand after that says so, until the next proposal checks it again.
- Agents read the docs over MCP before they build, on every plan.
Questions
Can a person still close a ticket without checks?
Yes. Done is a status like any other. The ticket simply shows Not verified, with the reasons, so everyone can see the difference between done and proven.
What counts as evidence?
A URL of a pull request, commit, test run or page (the kind is detected), or a test without a URL with its result, for example “npm test: 48 passed”.
Who can tick checks?
The assignee, the reporter and project managers, in the app or through their agent.
Give your next agent a brief.
Free for up to 10 people, with MCP for every agent. No credit card.