Where can I read back what the crew decided during docs updates in a Go microservice?

Tares keeps what the crew decided on the project page for your docs updates work in a Go microservice. Open the Decisions fold to read every question the crew asked and your answer in your own words, newest first. The Assumptions fold lists the choices the crew made on its own and whether you kept them.

How it works

Every project you hand to the crew gets a page of its own, the record of the whole build. Your docs updates project in a Go microservice gets the same page as any other project. The page shows four steps across the top: Spec, Build, Review and Done. Below them, each part of the record folds open.

Four folds make up the audit trail:

• Decisions holds every question the crew asked you and your answer, in your own words, newest first. If the project waits for your yes before every merge, the merge approvals appear here, each with the answer as you typed it.
• Assumptions holds every choice the crew made on its own, and whether you kept it. While the project builds, assumptions are open. Each one names the tickets it touches and the builder that made it.
• Tickets holds the 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.

The page also has Docs, GitHub and Crew folds. The Docs fold holds the starting prompt, the spec, the plan and the project’s AGENTS.md. For a full walkthrough of one real project, see A project, end to end.

You answer the crew’s questions in the orchestrator’s session. When the crew meets something the plan does not cover, it picks a 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 the Decisions fold.

Set it up

1. Hand the project to the crew. In the repo, run the spec command and answer Claude Code’s questions.

tares factory spec

2. Answer the crew’s questions in the orchestrator’s session as the build goes. Questions waiting for you also appear at the top of the Crew page in the console and on the project page.
3. Open the Crew page in the console and pick your project from the list of open projects. Finished projects are folded below.
4. Open the Decisions fold to read each question and your answer, newest first.
5. Open the Assumptions fold to see each choice the crew made on its own, whether you kept it, and for open ones the tickets and builder involved.
6. Open the Tickets and Sessions folds when you want the pull requests, review rounds and recorded sessions for the work.
7. To make an answer stand from now on, say so in your answer, for this project or for every project.
8. When the work is done, stop the crew. Tares keeps the projects, tickets and answers, so you can read them back later and the crew carries on from them when you start it again.

tares factory crew down
tares factory crew up

What you get

• One page per project where you read back every question the crew asked and what you answered, in your own words.
• A clear split between decisions you made and assumptions the crew made, so you can see what you kept.
• Assumptions that name their tickets and the builder that made them while a project builds.
• Milestones, tickets, pull requests and review rounds in the Tickets fold, so you can see how the work progressed.
• Recorded Claude Code sessions in the Sessions fold, from the spec session to each builder.
• Records that stay in place after the project is Done. Tares marks the project Done with your own words and moves it to the finished list on the Crew page.
• Answers that persist when you stop the crew with tares factory crew down.

When something else fits

The project page is the place to read back one project’s decisions. It does not replace the places where the work itself lives. The GitHub fold lists the repos the project changes, where each is checked out, and its open and merged pull requests. Read the pull request itself for the code and review comments.

If you want to change how the crew works on the next piece of work, the Docs fold is where you edit the AGENTS.md and memory, shared by every project or specific to one. An edit there changes what sessions read, while the Decisions and Assumptions folds stay a record of what already happened.

To pick up a finished project again, hand it to the crew again, for example with a follow-up spec.

Related