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

Tares records what the crew decided on the project page, in the Decisions and Assumptions folds. Decisions hold every question the crew asked you and your answer in your own words. Assumptions hold every choice the crew made on its own and whether you kept it. Tickets and Sessions complete the audit trail for a framework migration in a Node/TypeScript app.

How it works

Every project you hand to the crew gets a page of its own, the record of the whole build. The page shows four steps across the top (Spec, Build, Review and Done) and a progress bar with one segment per ticket. Below them, each part of the record folds open. A framework migration in a Node/TypeScript app is a project like any other, so it is recorded the same way.

Four folds make up the audit trail:

• Decisions: every question the crew asked you and your answer, newest first. You answer in the orchestrator’s session, and the answer is stored as you typed it, up to 4,000 characters. A long pasted reply with several lines or paragraphs matches in full. A reply stored before Tares fixed this stays cut, so paste the missing lines once more.
• Assumptions: every choice the crew made on its own, and whether you kept it. When the crew meets something the plan does not cover, it 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. Mid-build, assumptions are still open. At the end of each milestone the orchestrator brings them to you together in one question.
• 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.

An example from a real Node project shows what an assumption looks like. The working doc named vitest.config.ts, which fails to load on the repo’s Node version. The builder used vitest.config.mts instead and recorded that as an assumption. You can read the full walk-through in A project, end to end.

Set it up

1. Hand the migration to the crew if you have not yet. Follow Get started for the full order, then bring up the crew and plan the project:

tares factory crew up
tares factory spec "what you want to build"

2. Answer the crew’s questions in the orchestrator’s session. Each answer goes into the Decisions fold as you typed it.
3. Open the Crew page in the console, at http://127.0.0.1:8787/crew on a local Tares. Find your project in the Projects list. Open projects are listed with their builders, and finished ones are folded below.
4. Open the project page and unfold Decisions to read your answers, newest first.
5. Unfold Assumptions to see each choice the crew made on its own, whether you kept it, and the tickets and builder it names.
6. Unfold Tickets to see each ticket with its builder, pull request and review rounds. Unfold Sessions to open the recorded Claude Code sessions.
7. To make an assumption stand from now on, say so in the orchestrator’s session, for this project or for every project.

What you get

• One page per migration that holds the whole record, from the starting prompt to the last merged pull request.
• Your own words in Decisions, so you read back exactly what you approved, up to 4,000 characters per answer.
• A list of the choices the crew made without asking you, such as which config file name to use for your Node version. Each one shows whether you kept it and names the tickets and builder involved.
• Tickets with their builder, pull request and review rounds, plus the recorded sessions behind the work.
• A record that stays after the project is Done. Tares keeps the projects, tickets and answers, so a finished project moves to the finished list on the Crew page and the crew can carry on from it.

When something else fits

• To see what moved across projects rather than the reasoning behind one, use Standup on the Crew page. It reports what is done, started, in review, blocked and waiting on you since yesterday, over the last 7 days, or between dates you pick.
• For the live state of a station or a question waiting for you, use the Crew page instead of the project page.

Related