Where can I read back what the crew decided during small features in a documentation website?

Tares keeps that record on the project page for your documentation website, in the Decisions, Assumptions, Tickets and Sessions folds. Decisions holds every question the crew asked you, with your answer in your own words. Assumptions lists each choice the crew made without asking, and whether you kept it.

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, so you can read only the part you need. The same folds apply to any project, including one that builds small features for a documentation website.

• Decisions lists every question the crew asked you and your answer, newest first. The answer is stored as you typed it, up to 4,000 characters.
• Assumptions lists 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 a sensible answer, writes it down as an assumption and carries on.
• Tickets shows milestones with their acceptance checks, and each ticket with the builder that held it, its pull request and its review rounds.
• Sessions holds the recorded Claude Code sessions, from the spec session to each builder.

You give answers in the orchestrator’s session. Tares finds your answer there 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.

At the end of each milestone, the orchestrator brings you its assumptions in one question. Until then they show as open, each with the tickets it touches and the builder that made it.

Set it up

1. Open the Crew page in the console, at http://127.0.0.1:8787/crew on a local Tares. Open projects are listed with their builders, and finished projects are folded below.
2. Open the project page for your documentation website. The four steps across the top, Spec, Build, Review and Done, show where the build stands, and the progress bar has one segment per ticket.
3. Unfold Decisions to read each question and your answer, newest first. Merge approvals appear here too if the project waits for your yes before every merge.
4. Unfold Assumptions to see each choice the crew made alone. Each entry names the tickets it touches and the builder that made it.
5. Unfold Tickets to see which builder held each ticket, its pull request and how many review rounds it took. Unfold Sessions to open the recorded session behind a change.
6. To make an answer stand from now on, say so in the orchestrator’s session, for this project or for every project.

If you have no project yet, hand one to the crew first. The setup steps are on Get started. Once the crew is up, plan the project from the repo:

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

The spec session asks you questions, and the result goes into Tares as a spec, a plan, an AGENTS.md for the project and milestones with acceptance checks. All of it is readable later in the Docs fold. For a full walk through one build, including a Decisions fold with five answered questions, read A project, end to end.

What you get

• One page that works as an audit trail of the build. You can see what the crew asked, what you answered and what it assumed, without searching old terminal output.
• Your answers stay in your own words, not a summary. A recorded answer holds up to 4,000 characters.
• A clear line between what you decided and what the crew decided. Assumptions show whether you kept each one.
• A route from a decision back to the work. Tickets point to the builder, the pull request and the review rounds, and Sessions holds the recorded session.
• A record that lasts. When you run tares factory crew down to stop the stations, Tares keeps the projects, tickets and answers, so the crew carries on from them when you bring it back up.
• The Docs fold keeps the starting prompt, spec, plan and AGENTS.md next to the decisions. You can edit those docs there.

One limit to know: a reply stored before Tares fixed long-reply matching stays cut. Paste the missing lines once more and the full answer is recorded.

When something else fits

• To see what moved across all projects at a glance, use Standup on the Crew page. It reports what is done, started, in review, blocked and waiting on you, since yesterday, over 7 days or between dates you pick.
• To read the code changes themselves, use the GitHub fold, which lists the repos the project changes and their open and merged pull requests. Decisions and Assumptions record the reasoning, not the diff.
• To change course mid-build, talk to the orchestrator rather than editing the record.

Related