Where can I read back what the crew decided during framework migrations in a Python backend?

Tares keeps the record of 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, and Assumptions hold every choice the crew made on its own, with whether you kept it. Tickets and Sessions folds on the same page complete the audit trail for your framework migrations in a Python backend.

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:

• Decisions: every question the crew asked you and your answer, in your own words, newest first. A recorded answer holds up to 4,000 characters.
• Assumptions: every choice the crew made on its own, and whether you kept it. Each one 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. The answer goes into the Decisions fold as you typed it. Tares finds your answer in your session by matching it line by line, so a long pasted reply with several lines or paragraphs matches in full. Tares keeps up to 20,000 characters of your turn for this, and the tags Claude Code wraps around pasted text do not stop a match.

When the crew meets something the plan does not cover, it picks the sensible answer, writes it down as an assumption and carries on. For a framework migration, that is where a choice such as a config file the crew used instead of the one named in the working doc would be written down. At the end of each milestone, the orchestrator brings you its assumptions in one question, and you keep or change them.

Set it up

You do not configure the audit trail. It is built as the crew works. To get a project page for your migration, plan it and bring up the crew, then read the page.

1. Bring up the crew with tares factory crew up.
2. Plan the migration from your repo with tares factory spec. 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.
3. Hand the project to the crew when asked. The orchestrator picks it up and starts a builder.
4. Answer the crew’s questions in the orchestrator’s session. Each answer lands in the Decisions fold as you typed it.
5. Open the project page from the Projects list on the Crew page in the console, at http://127.0.0.1:8787/crew locally. Open the Decisions and Assumptions folds.

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

To make an answer stand from now on, say so, for this project or for every project. For the full walk through of one project, from spec to done, read A project, end to end.

What you get

• A Decisions fold that shows every question the crew asked you and your answer, in your own words, newest first.
• An Assumptions fold that shows every choice the crew made on its own, each naming its tickets and the builder that made it, and whether you kept it.
• A Tickets fold that shows each ticket with the builder that held it, its pull request and its review rounds.
• A Sessions fold that shows the recorded Claude Code sessions, from the spec session to each builder.
• A record that stays: Tares keeps the projects, tickets and answers after tares factory crew down, so the crew carries on from them.

In the worked project, the crew raised five questions and five assumptions. For example, the builder used vitest.config.mts instead of vitest.config.ts because the first failed to load on the repo’s Node version, and it recorded that as an assumption. The same page shows the other choices the crew made.

When something else fits

• To see who is working on what right now, use the Crew page. It shows each station’s state, the projects and a review queue, rather than the history of decisions.
• For a summary of what moved across projects since yesterday or over the last 7 days, use Standup, top right on the Crew page.
• The project page is the record for work handed to the crew. Tares marks a project Done with your closing answer, and a finished project moves to the folded list on the Crew page. To pick it up again, hand it to the crew again, for example with a follow-up spec.

Related