Where can I read back what the crew decided during dependency upgrades in a documentation website?
Tares keeps a project page for every project you hand to the crew, and its Decisions and Assumptions folds hold what the crew decided during dependency upgrades in a documentation website. Decisions lists every question the crew asked you, with your answer in your own words, newest first. Assumptions lists every choice the crew made on its own, and whether you kept it. Tickets and Sessions on the same page 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. Across the top are four steps (Spec, Build, Review and Done) and a progress bar with one segment per ticket. Below them, each part of the record folds open. Four folds matter for an audit trail:
- 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, and Tares keeps up to 20,000 characters of your turn for this. The tags Claude Code wraps around pasted text do not stop a match.
Assumptions appear when the crew meets something the plan did not cover. It picks the sensible answer, writes it down as an assumption and carries on. At the end of each milestone, the orchestrator brings you its assumptions in one question, and your answer lands in Decisions.
Set it up
-
Make sure the crew is running and the project is handed to it. The Get started page lists the full order. The two commands that matter here are:
tares factory crew up tares factory spec "upgrade the dependencies of the documentation website" -
Answer the spec session’s questions. The spec, the plan, the project’s AGENTS.md and the milestones with their acceptance checks go into Tares. Say yes to handing the project to the crew.
-
Answer the crew’s questions in the orchestrator’s session while it works. Each answer is recorded as you typed it.
-
At the end of each milestone, answer the orchestrator’s question about its assumptions. Say whether you keep them. To make an answer stand from now on, say so, for this project or for every project.
-
Open the project page in the console and unfold Decisions to read your questions and answers. Unfold Assumptions to see what the crew chose on its own and whether you kept it.
-
Unfold Tickets to see which builder held each upgrade ticket, its pull request and its review rounds. Unfold Sessions to open the recorded Claude Code session behind a change.
The page A project, end to end follows one real project through these folds, with screenshots of each.
What you get
- A readable record of every question the crew asked you during the upgrades, with your answer in your own words, newest first.
- A list of the crew’s own choices, such as a config file it swapped because the original did not load, each tied to its tickets and the builder that made it, with a note on whether you kept it.
- Ticket history that shows which builder held each upgrade, its pull request and how many review rounds it took.
- Recorded sessions, from the spec session to each builder, for the full conversation behind a change.
- A record that stays. Tares keeps the projects, tickets and answers, so the crew carries on from them when you stop and restart it.
- Merge approvals in Decisions if you want the crew to wait for your yes before every merge. Each approval is kept with the answer as typed.
When something else fits
The Decisions and Assumptions folds cover choices the crew asked you about or made on its own. For what a change did in code, use the pull request and its review rounds in the Tickets fold. For what moved across projects since yesterday, the Standup report on the Crew page summarizes done, started, in review, blocked and waiting items.