Where can I read back what the crew decided during docs updates in a documentation website?

Tares keeps every decision the crew makes on a docs updates project on that project’s page in the console. Open the Decisions fold to read each question the crew asked you and your answer, in your own words. The Assumptions, Tickets and Sessions folds sit beside it as the rest of the audit trail.

How it works

Every project you hand to the software factory for Claude Code gets its own page, the record of the whole build. A docs updates project for a documentation website gets the same page as any other project. Open the Crew page in the console (http://127.0.0.1:8787/crew locally), pick the project, and fold open the part of the record you want.

• Decisions lists every question the crew asked you, with your answer, newest first. The answer is stored as you typed it, and a recorded answer holds up to 4,000 characters.
• Assumptions lists every choice the crew made on its own when the plan did not cover something, and whether you kept it. Each assumption names the tickets it touches and the builder that made it.
• Tickets shows the milestones with their acceptance checks, and each ticket with the builder that held it, its pull request and its review rounds.
• Sessions lists the recorded Claude Code sessions, from the spec session to each builder.

You answer the crew’s questions in the orchestrator’s session. Tares then finds your answer in that session by matching it line by line. A long pasted reply with several lines or paragraphs matches in full, because Tares keeps up to 20,000 characters of your turn for the match, and the tags Claude Code wraps around pasted text do not stop it. A reply stored before this fix stays cut, so paste the missing lines once more.

At the end of each milestone the orchestrator brings you its assumptions together in one question. Your answer to that question is what marks them kept. To make an answer stand from now on, say so, for this project or for every project.

Set it up

1. Check that Claude Code is signed in, that gh is signed in with write access to the repos the crew works in, and that git, jq and curl are installed.
2. Install the CLI with uv tool install tares (or brew install glassflow/tap/tares).
3. On a local Tares, start it with tares up. In a second terminal, start the MCP endpoint every crew session shares. On Tares Cloud, run tares login instead and pick your workspace in the browser. There is no MCP endpoint to start there.
4. Give Tares access to GitHub, in Settings > GitHub for a local Tares or Connect GitHub on Tares Cloud.
5. Bring up the crew, then plan the docs work.
6. Answer the crew’s questions in the orchestrator’s session, then open the project page and read the Decisions fold.

tares up
tares mcp --transport streamable-http
tares factory crew up
tares factory spec "what you want to build"

The commands run in that order, with tares mcp in its own terminal. For a full walk through a real project, including the five questions it raised and the five assumptions it kept, read A project, end to end. If you are new to the factory, start with Get started.

What you get

• A written record of each call you made, in your own words, that you can read back after the build is over.
• A list of every choice the crew made without asking you, so you can see what it assumed and whether you kept it.
• A ticket-level trail of who built what: the builder, the pull request and the review rounds for each ticket.
• The recorded sessions, so you can trace a decision back to the conversation behind it.
• A Standup report, top right on the Crew page. It lists what is done, started, in review, blocked (with the reason) and waiting on you, with pull request links, for the last day, the last 7 days or dates you pick.
• A record that lasts. When a project finishes, it moves to the finished list on the Crew page. Running tares factory crew down stops the stations, and Tares keeps the projects, tickets and answers.

When something else fits

• To change a decision, talk to the orchestrator. The project page is the record, not the place where you steer the work.
• For the starting prompt, spec, plan and AGENTS.md of the project, use the Docs fold instead of Decisions.

Related