Decisions

Decisions are the answers you gave. The platform keeps them because an implementation is only as reviewable as the reasoning behind it, and "why is it like this?" is the question that gets asked six months later when nobody remembers.

Where decisions come from

Mostly from preflight — the clarification an implementation asks for before it writes code. See Implementing a feature. Anything you answer there is recorded here.

Two views of the same thing

Project decision heads. The current answer to each question, across the project. This is the "what do we do about X here" view, and it is what a new person should read.

Per-feature launch history. Each feature's implementation launches, in order, with the answers that applied to each. A feature implemented three times has three rounds recorded, not one.

What is immutable, and why

Within a launch, the handoff baseline is fixed and stage-boundary adoptions are appended rather than overwritten. A launch's record is therefore a description of what was actually decided while that work happened, not a description of what you would decide today.

This matters when you are investigating something that went wrong: a record that quietly updated itself would tell you the wrong story about a run that has already finished.

Answers are carried, not asked again

A feature's answers carry into every later implementation of it: after a discarded or failed attempt, after a finished one you reopen, and from a module run to its member features and back. Re-answering questions you have already answered is not review — it is friction, and it invites a different answer the second time for no reason other than fatigue.

The launch that carried them shows a Carried over round first, naming the attempt the answers came from. When something preflight reads has changed since, the launch also runs a short check of only that change, and any new question it asks appears as the next round. To answer everything again instead, start Preflight and tick Ask every question again.

Superseded launches

A launch that was replaced because preflight ran again is excluded from the project-wide view; its replacement is the current answer. The history is still there against the feature.

Reading decisions from the command line

The Repave CLI exposes the same records — repave decisions list, with flags for a feature, a launch, or every feature in the project, and a text filter across question, answer and category. This is how an agent working in a Repave IDE session finds out what was already decided instead of asking you again. See the Repave CLI.