How to use the Workboard

Every item on the roadmap is something we could build for you, grouped by the part of the business it serves. Open one and it reads the same way every time: who it's for, how it works today, what we'd build, and how many tokens we think it takes.

Each item carries two priorities side by side: ours, and yours. You set Now, Next, Later or Park on anything, and you can propose an item we missed. Where your priority and ours differ, that's the agenda for the Monday check-in.

Each item also says which phase it belongs to. Only Phase I is in the agreement. The rest are proposals, labeled that way so there's never a surprise.

The roadmap says what. The board says how, and the first thing on the board is features. A feature is something you get: big enough to have a name, small enough to finish.

Every card belongs to exactly one feature. Use the Feature filter on the board to see one feature on its own, and the column counts tell you how far it is without reading a status report.

A sprint runs Wednesday to Tuesday, always. Each sprint has a name and one sentence: what's true at the end of it if the week went well. You'll find that goal line at the top of the board. If the sentence is true on Tuesday, the sprint worked.

The rhythm runs itself:

• Monday morning, the system opens next week's sprint and drafts its name and goal from the open cards.
• Tuesday, the team finishes planning and closes the week that ended.
• Your part is the Monday check-in, thirty minutes, plus a Friday note from us saying what came to life and what's still owed.

The board has five columns, and a card only ever sits in one of them: To do, Doing, Waiting, Done and Not Doing. Not Doing is work we decided against, kept visible rather than deleted. The column is the status, so the board can't lie.

Open a card and it reads top to bottom:

• The title says the outcome, not the activity.
• Under it, one paragraph that starts with “Done when”. That's the whole contract. If you can't write the done-when line, the card isn't ready.
• Who has it, when it's due, which column it's in, and how many Human Tokens we think it takes.
• Three pills: the feature, the sprint, and the pull request once there's code.
• Subtasks, then one activity stream with every comment and every move in time order.

Some cards are yours: the export we need, the login, the answer only you have. They're assigned to you, dated, and they sit under Needs you on your portal home page. Click one and you land on the board with the card open. You see every card exactly as we do. Nothing is hidden from the board except what we've marked internal, and that's rare.

When we build, the code goes into your own GitHub account as a pull request: a bundle of changes with a description, reviewed before it's merged. Merged means live.

Every pull request links back to its card, so the card tells you the outcome and the pull request shows you the work. The Pull Requests tab on your program lists all of them, and the tile at the top counts how many merged in the last thirty days. Because the code is in your account, nothing has to be handed over at the end. It was never anywhere else.

Your agreement buys Human Tokens. Your Tokens page shows where they stand:

• Bought is what the agreement gave you.
• Delivered is the time we've logged on your program, from our own time tracking, not from estimates.
• Planned is the estimated tokens still ahead on your roadmap.
• Balance is bought minus delivered.

If the plan is bigger than the balance, you see it before we do, and that's a Monday conversation, not a surprise at the end. One more figure: Leverage is how much AI did per hour of human time on your program.

That's the whole system: a roadmap you prioritize, features that give the work a shape, sprints that give it a week, cards that say what done means, pull requests that prove it shipped, and tokens that show what it cost. Everything you see is everything we see.

Open your portal and find your name. That's where we start.