What does the crew do when the plan does not cover a decision while it works on internal refactors?

Tares has the crew pick the sensible answer, write it down as an assumption and carry on, so the build does not stop for a gap in the plan. At the end of each milestone, the orchestrator brings you all the assumptions together in one question, and you keep or change them. Every assumption stays on the project page with its tickets and the builder that made it.

How it works

When a builder meets something the plan does not cover, it does not stop and wait for you. It takes the sensible answer, records it as an assumption and keeps working on its ticket.

• Recording. Each assumption names the tickets it touches and the builder that made it. Mid-build, assumptions are open.
• Collecting. At the end of each milestone, the orchestrator brings you its assumptions in one question in its session. You review them as a set, not one interruption at a time.
• Deciding. You answer in your own words. The answer goes into the Decisions fold as you typed it, up to 4,000 characters. To make an answer stand from now on, say so, for this project or for every project.
• Tracking. The Assumptions fold on the project page lists every choice the crew made on its own, and whether you kept it.

The project in A project, end to end shows this. Over three milestones the crew recorded five assumptions, for example:

• The working doc named vitest.config.ts, which fails to load on the repo’s Node version, so the builder used vitest.config.mts.
• Sitters already inactive in production kept open-ended slots. The builder left existing data alone, flagged it in the pull request and left any production fix to the person.
• The CI job for database tests ran on the same Node version as the unit tests, not the one in the working doc.

The orchestrator asked about them at the end of each milestone, and the person kept all five.

Set it up

You do not configure assumptions separately. They are part of how the crew works once a project is handed over. If you have not set up the crew yet, follow Get started.

1. Bring up the crew. At this step you choose how far the crew may go, and the Crew page shows your choice under How far the crew may go.

   tares factory crew up

2. Plan the project. A spec session produces the spec, the plan, an AGENTS.md for the project and milestones with acceptance checks.

   tares factory spec "what you want to build"

3. Say yes to handing the project to the crew. The orchestrator picks it up and starts a builder for the first milestone.

4. Open the project page and watch the Assumptions fold. Open assumptions list the tickets they touch and the builder that made them.

5. When the orchestrator asks at the end of a milestone, answer in its session. Keep the assumptions you agree with and change the ones you do not. Say so if an answer should stand for this project or for every project.

6. Read the Decisions fold to see every question the crew asked and your answer, newest first.

What you get

• Work that keeps moving. A gap in the plan does not stop a builder. It records the choice and continues with its ticket.
• One review per milestone. You look at the crew’s own choices together, at a natural checkpoint, instead of answering them one by one as they come up.
• A visible record. The Assumptions fold shows each choice, the tickets it touches, the builder that made it and whether you kept it.
• Your answers in your words. Each answer is stored in the Decisions fold as you typed it, and you can make it stand for the project or for every project.
• Flagged side effects. In the example project, the builder flagged an assumption about existing production data in the pull request and left any fix to the person.

When something else fits

• Some questions only you can answer, such as trusting the repo folder in Claude Code once or giving Tares a GitHub token. These come as separate questions and appear at the top of the Crew page, not as assumptions.
• If you want a say before a merge, one project in the example waited for the person’s yes before every merge, so most of its decisions were merge approvals. You choose how far the crew may go at tares factory crew up.
• To steer a ticket in progress, talk to the orchestrator. You can also open the station’s session in a terminal when it is waiting for you.

Related