Review

Review brings together decisions that need an answer: work that would undo an earlier decision, changes waiting for approval, and knowledge that may be out of date. Each entry shows what is involved and who can decide.

Open Knowledge → Review in the project sidebar. You can work through questions here or discuss them with Dev or your agent. They see the same questions and can record your answer when you ask.

Find what needs you

The page has five tabs:

• Waiting on you: decisions, confirmation requests and proposed changes you can answer.
• Raised by you: questions involving work you requested.
• All waiting: the project's outstanding questions and changes.
• Possibly outdated: descriptive knowledge that may no longer be accurate.
• History: questions and changes already decided, with who answered and when.

Search by words or describe what you are looking for. Use the filters to narrow by state, involvement, kind of question, kind of record or person. Open an entry to read the records and the reason it was raised. Previous and next let you move through entries without returning to the list.

When work would undo a decision

DevSpec checks work against the intent of existing items, recorded decisions and conventions, and decision documents. A conflict means more than two records mentioning the same subject: the new work would undo something the project has agreed.

The question shows the earlier decision, the work that would change it, and whose OK is needed. When a record has several conflicts at once, a conflict stepper at the top of the panel shows each conflict as a numbered tab with its status pill and Previous / Next arrows, opening on the first unresolved conflict and advancing automatically to the next unresolved one as you answer.

While it waits, the agent can build and push the work on its own branch. It must not merge into the project's tracking branch, and the item cannot reach Done, until it has the required OK and has landed. An Experiment follows the same separate-branch approach. See Tasks.

Give your answer

If the question is yours to decide, choose:

• Go ahead: allow the change to the decision.
• No: leave the work on its own branch. Give a reason so the person working on it can change the approach, drop it or discuss an alternative.
• This doesn’t undo my decision (or This doesn’t undo the decision): allow the work because the check found a conflict that is not really there.

The answer and its reason stay in history.

If the work has already reached the tracking branch without its OK, the choices are Keep it or Undo it. Keeping it gives the missing OK. Undoing it creates follow-up work to put the decision back; it does not instantly reverse the code.

The states help you follow what happens next: Waiting for an OK, Answered no, Landed without its OK, Being put back and Settled. A Maintainer can reopen a settled question when it needs another look.

Who can give the OK

A decision belongs to the person who asked for it or adopted it, not simply to whoever typed or last edited the record.

Changing your own decision does not wait on someone else. You normally cannot approve your own work over another person's decision. The project lead can, and a Maintainer can when changing a Contributor's decision or a decision nobody owns; the decision's owner is told when their decision changes.

An experiment can ask to land once you are ready. Its owner or a Maintainer can allow it; a Reviewed Contributor's experiment needs a Maintainer. Any other decisions the experiment would undo also need their OK. See The project lead and Project roles.

Make the decision in conversation

You do not have to leave a session to use Review. Ask Dev or your agent to explain the question, then say what you want to do. They can record decisions you are allowed to make, including accepting a proposal or giving a change the OK.

Another person's agreement must come from them. If Dev or an agent understands that they agree, it can send them a request to confirm the proposed answer. The person sees it under Waiting on you and can confirm or decline it, here or through their own instruction to Dev or an agent. No agent needs to remain online for them to answer.

A confirmation request changes nothing until it is confirmed. Declining needs a reason. The project lead can decide a confirmation request instead, as themselves, and the person who requested it is told the outcome.

Talk it through first

Choose Talk it through or Talk it through instead when you need a conversation before deciding. You can start with Dev, choose an agent, or open a room and bring people in later.

The session includes the question and relevant records. Continue the discussion returns to it. Discussing a question does not settle it: the decision stays open until an answer is recorded.

Accept or decline a proposed change

A proposal is saved wording or a specific change waiting for approval. Open it to see who asked for it, the current record and what would replace it. Examples include new work from a Reviewed Contributor, amendments to agreed tasks, team rules, and knowledge created by automations.

Choose Accept this change or Accept this ruling to apply the proposal, or Decline to leave the record unchanged. Add a note to explain your answer. The page tells you who can decide; most proposals need a Maintainer, while a change to a protected decision follows that decision's approval rules.

Only the version you reviewed is accepted. If the proposal or the record has changed since you opened it, reopen it to read the current wording before deciding.

Accepting proposed work makes it available to work on; it does not start an agent. A proposal to replace or close another item shows that consequence before you accept it. See Link related items.

Team rule proposals also appear on Project settings → Agent rules. Until accepted, the existing rules remain in force. See Rules and instructions.

Keep descriptive knowledge accurate

Possibly outdated is for records describing how things are: insights, risks, guides, runbooks, plans and other reference material. A check may find that implemented work has made one inaccurate.

Read the reason and the record. If it is still right, choose Still accurate and explain why. If it is wrong, choose Edit, or retract a memory or archive an artifact that no longer applies. You can also ask Dev or your agent to make the correction. Do not dismiss the warning just to remove it from the list.

A Maintainer's ruling applies directly. A Contributor or Reviewed Contributor can propose a ruling for a Maintainer to accept; the flag stays visible meanwhile. Viewers can read and discuss the question.

Decisions, conventions and decision documents that a person asked for or adopted are protected intent, not descriptions to discard when the code changes. Their conflicts use the OK process above. Records an agent created without anyone asking remain background knowledge until someone adopts them, and can be checked for outdated information.

Flags also appear on the records in Memories and Resources, where you can open the same question. See Memories and Documents and artifacts.

Deal with duplicate records

A duplicate describes the same outcome as another record. It is different from a conflict, and different from work that deliberately replaces an earlier approach.

Ask Dev or your agent to compare the full records. Keep useful detail in the one you retain, then close the duplicate with a link to it. The history remains available. If they describe different outcomes, record that instead so the same unchanged pair is not raised again. See Tasks.

What the checks cost

Checking work against decisions and checking knowledge for outdated information are charged as Running your project. They count toward the project's spending limit, not anyone's personal allowance. While paid work is paused, those checks wait.

Reading Review and recording a decision is free. Asking Dev to help you understand a question is charged as a Dev reply. See Billing, usage and limits.

Get told when your answer is needed

Requests for your OK and confirmation requests appear in your notifications according to your notification preferences. The daily New questions in Review notice brings together new decisions and changes that concern you. Descriptive records that are merely possibly outdated stay in Possibly outdated, rather than notifying everyone. Turn on email for the relevant categories in Settings → Notifications if you want them in your inbox. See Notifications and messages.