Where can I read back what the crew decided during bug fixes in a Node/TypeScript app?

Tares keeps what the crew decided on the project page, in the Decisions and Assumptions folds, so you can read back every choice made while fixing bugs in your Node/TypeScript app. Decisions holds every question the crew asked you and your answer, in your own words, newest first. Assumptions holds every choice the crew made on its own, and whether you kept it. The Tickets and Sessions folds complete the audit trail.

How it works

Every project you hand to the crew gets a page of its own, the record of the whole build. Each part of the record folds open, and four of the folds make up the audit trail for bug fixes:

• Decisions: every question the crew asked you and your answer, in your own words, newest first. If you typed a merge approval, you read it back as you typed it.
• Assumptions: every choice the crew made on its own when the plan did not cover something. The crew picks the sensible answer, writes it down as an assumption and carries on. Each assumption names the tickets it touches and the builder that made it.
• Tickets: milestones with their acceptance checks, and each ticket with the builder that held it, its pull request and its review rounds.
• Sessions: the recorded Claude Code sessions, from the spec session to each builder.

You answer the crew’s questions in the orchestrator’s session. Mid-build, assumptions stay open. At the end of each milestone the orchestrator brings them to you together in one question, and your answer is recorded in Decisions. Questions waiting for you also appear at the top of the Crew page and on the project page under questions waiting for you.

The walkthrough in A project, end to end shows this on a project with bugs to fix and no tests. The assumptions it recorded were concrete. The working doc named vitest.config.ts, which fails to load on the repo’s Node version, so the builder used vitest.config.mts instead. The CI job for database tests ran on the same Node version as the unit tests. The reviewer’s smaller findings became a new ticket. All of it is readable afterwards in the folds.

Set it up

1. In your repo, run the spec command and answer Claude Code’s questions. The result goes into Tares as a spec, a plan, an AGENTS.md for the project and milestones with acceptance checks. If you are new to the factory, start with Get started.
2. Hand the project to the crew when the spec session ends, and start the crew.
3. Answer the crew’s questions in the orchestrator’s session as the build runs. Each answer is stored in your own words.
4. Open the Crew page in the console, http://127.0.0.1:8787/crew locally, and open your project from the Projects list.
5. Open the Decisions fold to read your answers, newest first. Open Assumptions to see each choice the crew made on its own and whether you kept it. Open Tickets and Sessions to trace a decision back to the pull request, review round or recorded session behind it.
6. At the end of each milestone, answer the assumptions question. To make an answer stand from now on, say so, for this project or for every project.

tares factory spec
tares factory crew up

When the last milestone is done, the orchestrator asks whether the project is finished. Tares marks the project Done with your words and moves it to the finished list on the Crew page. Run tares factory crew down to stop every station. Tares keeps the projects, tickets and answers, so you can still read them back later.

What you get

• One page per project that records the whole build, from the starting prompt to the last merged pull request.
• Your answers kept as you wrote them, so the record shows what you said and not a summary of it.
• Every autonomous choice written down as an assumption, with the tickets it touches and the builder that made it, so nothing the crew chose on its own is hidden.
• A trail from decision to ticket to pull request to session, so you can check why a bug fix was done the way it was.
• A record that stays after the crew stops. Tares keeps projects, tickets and answers when you run tares factory crew down.

When something else fits

• To see live work rather than the record, use the Crew page, which shows each station’s state, the tickets it holds and its last lines.
• To change a doc the sessions read, such as the spec, the plan or AGENTS.md, edit it under All docs at the foot of the Docs fold. Decisions and Assumptions are a record of what happened, not a place to edit.
• To steer work that is in progress, talk to the orchestrator in its session.

Related