AatirWorking now
Owner and engineer
19 updates across 3 stories, 36 commits, 0.3 hours.
Technical details · 36 commits
Sessions, New York time
| 18 Sept 2026 | 14:06 | open | agent not reported |
| 18 Sept 2026 | 14:24 | open | claude-code, claude-fable-5-1 |
The project board that writes itself.
Your engineers' coding agents fill in the board as they work. You read it each morning and reply from the same page. Nobody moves a card.
Every board is also a record. When you need to prove it, turn the Ledger on.
Truestate
Team board
18 Sept 2026
12.3
Hours · all time
110
Tasks done · all time
147
Commits · all time
6
In progress · stories
Today
18 Sept 2026
0.3 h
Stored in your GitHub repository. All times are New York.
Live: this is Truestate's own board. Open it full size
Boards assume someone updates the card.
With coding agents, the work happens while nobody is watching.
So the board goes stale, and you go back to asking.
Three moments, no typing.
- session opens
Day start
Opening a session starts the day. The agent sees yesterday, today's plan, and anything you assigned.
ExampleDay start for Alex, 2026-09-11 (Eastern). Created tracker/log/2026-09-11/alex.json.Last shipped: 2026-09-10: Done: Month picker; 4 commits (4 commits)Blocked: noneToday: Continue 012-billing-exports: CSV emitter | Start 012-billing-exports: PDF bundleAssigned to you on the board: 1 open task (#41 Add a search box to the invoice list). Open change requests: 0.Record task status in tracker/stories/ as you work. The day closes automatically at 00:05 Eastern; say "day end" to close early.
- session works
Record as you go
Every task the session starts, blocks, or finishes is written to the repository in the same commit as the code. Hours come from the session's own clock.
ExampleIn progressBilling exports3 of 6 done. Working on: PDF bundle.
In progress- PDF bundle
Blocked- None
To do- Email the file when it is ready
- Close
Done (3)
- midnight
The day closes itself
At five past midnight the day is finalized for everyone, signed, pushed, and the board is current before you open it.
Example5 hAlexEngineer3 updates across 1 story, 3 commits, 5 hours.
Billing exports- Done: CSV emitter
- Started: PDF bundle
- 3 commits: feat(exports): CSV emitter; feat(exports): PDF bundle scaffolding
3 commitsNext- 012-billing-exports: PDF bundle
Technical details
Intervals11 Sept 2026 09:02 11:40 11 Sept 2026 10:10 14:02 Commits- d161ee2
- 9c4b0aa
- 3e8f1c0
Open one page each morning.
6 phases. 2 done, Foundation is nearly done.
90%
Each phase counts the tasks of its stories; the total is the average of the phases.
1Foundation98%In progress
Before any product code: the written spec is settled, the app skeleton exists, and the board's own record keeping runs on this repository so the build is visible from day one.
- Settle the written specShipped
- Repository foundationShipped
- Marketing siteIn progress
2The board100%Shipped
What a product owner opens: today's work by person, the build by phase, every feature and its tasks, the daily log, and a link that can be shared without a login.
- The boardShipped
3Sign in, tasks, and Ask88%In progress
Members sign in by email, hand out work and answer decisions from the board, and ask questions that get answered from the repository.
- Sign in and the GitHub AppShipped
- Tasks as issuesIn progress
- Ask the repositoryIn progress
4Install and ship82%In progress
A new team gets running in minutes, and the first outside customer migrates onto the hosted product.
- The CLI: init and installIn progress
- Deploy and the first team handoffIn progress
5Assistants and onboarding100%Shipped
Two things that make the product usable beyond this team: a connector so an assistant outside the repository can ask where the build is, and an onboarding path where the board proposes the team from git, seeds itself from history, and shows a checklist until the first real day.
- MCP serverShipped
- OnboardingShipped
6The record and the Ledger69%In progress
Every session records which agent and model did the work, every agent authored commit carries a named human review, the nightly close signs and chains the record and anchors it outside the repository, and a verify command lets an assessor check it offline. Cost, quality, and policy views read the same files.
- The record and the LedgerIn progress
- The site, enterprise firstShipped
Done
- The command line tool is on npm; hours can be corrected with a signed note.
- An assistant outside the repository can read the build through the MCP connector.
- A new repository gets a checklist, a team screen that proposes people from git, and a board seeded from its own history.
- Assistants can also create tasks, ask questions, and answer decisions through the connector, and doctor checks a machine in five lines.
- Onboarding is complete, including the migration mode for a team already running the internal board.
- Every session records which agent and model did the work, every commit shows whether a named person reviewed it, and signing can be turned on per board.
- The site now sells the record: the Ledger page, the Board page for small teams, four tiers, a Talk to us form, and the live embed on the Ledger tab.
Now
- The chain and the anchor: the nightly close will hash what it wrote and publish the hash outside the repository.
- The verify command an assessor runs offline.
Next
- The Ledger tab and the evidence export.
- The first outside team's first week.
The Phases tab, live. The hero above is the Today tab.
- Today. One card per person. What moved, what is blocked, hours with the intervals behind them.
- Phases. The whole build as one bar. Click a phase for the features inside, in plain words.
- Stories. One row per feature. Progress, what is being worked on, who owns it.
- People. Every person's page. Their tasks, their features, their hours.
Talk back from the board.
Pin a note on the live product
Coming nextCircle the thing that is wrong. It becomes a task with a screenshot, on the right page, for the right person.
Example
/portalPinCircleArrow
Approve deliverable
1
The approve button is easy to miss. Make it the main action on this page.
Saves a screenshot and becomes a task
Save note
Animation: a pin is placed on the approve button of the live product, a small form opens beside it with the note text, and the note is saved as a task with a screenshot.
Ask the repository
Ask about the build. An agent reads the code and answers in minutes, without pulling in an engineer.
Example
Ask the repository
Is the client portal ready for the Hartwell demo on Friday? (example)
Nearly. Clients can sign in, see open work, and approve a deliverable as of today. Two things are not ready: comments on a deliverable are still to do, and storing signed approvals is blocked on a decision that is waiting for Maya. If that decision lands tomorrow, the demo can show the full approval flow.
Example answer, in about 3 minutes
Answer decisions in one click
When the team needs a call, you get a card with a recommendation. Agree in one tap, or write your own.
Example
Decide: where signed approvals are stored
- Where should a signed approval be stored?
Recommended: In our own database, with a copy of the PDF in object storage. Simplest to audit.
AgreeSomething else - Should clients be able to download their signed approvals?
Recommended: Yes, from the portal, as a PDF with the signature block.
AgreeSomething else
1 of 2 answered. You can send some now and the rest later.Send
Hand out work
Assign a task to a person. Their next coding session picks it up as the day's work.
Example
Give someone a task
Add a search box to the invoice list
Alex
Due 18 Sept 2026
Assign a task
Next morning in Alex's session: Assigned to you on the board: 1 open task
Hours you can defend.
Every hour is a timed interval from a real session, not a guess from commit times.
Engineers control their own clock.
Any correction is signed.
Example
Alex
Engineer
3 updates across 1 story, 3 commits, 5 hours.
Billing exports
- Done: CSV emitter
- Started: PDF bundle
- 3 commits: feat(exports): CSV emitter; feat(exports): PDF bundle scaffolding
3 commits
Next
- 012-billing-exports: PDF bundle
Technical details
Intervals
| 11 Sept 2026 | 09:02 | 11:40 |
| 11 Sept 2026 | 10:10 | 14:02 |
Commits
- d161ee2
- 9c4b0aa
- 3e8f1c0
Teams that do not bill by the hour turn hours off with one setting.
Built for the people who asked for the software.
Founders with a small team
The morning record replaces the standup. Ask replaces the interruption.
Agencies and studios
Your client is the product owner. They see the daily record, leave notes on the live build, and sign off on hours without a status email.
Teams already on git native trackers
Keep how your engineers work. Give the rest of the company a page.
$ npx @truestate/cli init$ npx @truestate/cli installDay start for Alex, 2026-09-11 (Eastern). Created tracker/log/2026-09-11/alex.json.Last shipped: 2026-09-10: Done: Month picker; 4 commits (4 commits)Blocked: noneToday: Continue 012-billing-exports: CSV emitter | Start 012-billing-exports: PDF bundleAssigned to you on the board: 1 open task (#41 Add a search box to the invoice list). Open change requests: 0.Record task status in tracker/stories/ as you work. The day closes automatically at 00:05 Eastern; say "day end" to close early.
For engineers
One command in the repo, one on your machine. Status is written as JSON in the same commit as the code, signed, with git as the audit trail. You never type it again.
Works with Claude Code today. More runtimes coming.
Free during early access
One repository, up to three people, free.
The CLI, the hosted board, tasks, Ask through your own workflow, and the record with identity and review. The Ledger, Team, and Enterprise tiers are on the home page.