Decisions and review

A decision in Mios represents an agreed technical choice, architectural rule, or project requirement. Mios tracks the history of each decision, who authored it, and what earlier decisions it replaced.

How decisions are proposed

Decisions enter Mios through two primary pathways:

1. Extraction from connected sources: When Mios indexes pull request discussions, architecture design documents, or technical chat threads, its analysis engine detects when the team agrees on a path forward.
2. Proposals from coding agents: When an agent finishes a task in Claude Code or Codex, the stop hook analyzes the changes made during the session and proposes newly established patterns to Mios.

All newly proposed decisions start in a pending state, waiting for human confirmation.

The Review queue ("Needs you")

To review proposed decisions, go to Review (/pages/review) at https://app.mios-ai.com.

Each card displays the proposed decision statement, the rationale extracted from discussion, and direct links to the source documents. You have four available actions:

• Adopt: Validates the decision. It becomes part of the authoritative project memory and is immediately served to coding agents.
• Reject: Dismisses the decision. It is removed from the active queue and will not be suggested to agents.
• Edit: Adjusts the title or wording of the decision before adopting it.
• Undo: Reverts a recent review action if a decision was adopted or rejected by mistake.

Auto-adopted decisions

When multiple distinct and authoritative documents explicitly state the same decision, Mios can automatically mark the decision as auto-adopted.

Auto-adopted decisions are active immediately, but they remain visible in the review queue so team members can inspect or adjust them at any time.

Replacing and superseding decisions

Engineering requirements evolve over time. When a newly proposed decision conflicts with or replaces an earlier decision, Mios flags the relationship.

In the review card, Mios highlights the conflicting prior decision under its contested entries list. When you adopt the new decision:

1. The new decision becomes the active guideline for the project.
2. The older decision is marked as superseded, preserving historical context without confusing agents.
3. Coding agents working on future tasks see the updated decision along with a reference to the replaced decision.