Decisions

“What did we decide?” has one answer in Minga: a list of decided cards and decision comments, newest first. There is no separate decisions page to keep up to date. Each decision sits on the record it changed.

Decided cards

A card you decided is already a decision record: what was proposed, the agent’s reasoning, your answer, who decided and when. That covers most decisions: a brief edit, a milestone moved into Now, a review pick, an answered question.

Decision comments

Some decisions are made in chat, and Lea applies them directly, with no card. For those she posts a decision comment on the item or goal the decision shaped, in one or two sentences: what, why, and where it came from.

DECISION · Oct 12 · Lea, from chat                                on DIC-130 2.4 First minute
No account step in 2.4. Why: every extra screen costs activation (G-2); sync can wait for 3.0.

The record holds what is true now (the spec, the brief). The card or the comment holds why and when, like a commit message. Decisions about the whole project belong in the brief; the card that changed the brief records why.

You can post decision comments too: from your own Claude Code or Codex session, comment with decision: true on an item or goal. The repo import uses this for the biggest past choices of an existing project.

The Saved line

When you decide, ask for or report something in chat, Lea writes it into the record it changes in the same turn. Under each of her replies, the app adds a Saved line, built from what the reply actually did:

Saved · DIC-131 Moved to Later · DIC-130 Decision: no account step in 2.4
Proposed · P-40
Not saved · DIC-136: the item changed meanwhile

Saved lists the records the reply changed and what changed, Proposed the cards it opened for you, and Not saved any write that failed. Each chip opens its record. A reply that changed nothing has no Saved line.

Where you see decisions

• Overview › Decisions: the latest five, and “more” to expand the list. Permission prompts are left out; they are not project decisions.
• The record’s history: an item’s or goal’s activity shows its decision comments and the cards that changed it.
• Over MCP: read_project includes the recent decisions.

Correcting a decision

• A wrong record (a spec, the brief, an item): edit it directly. Your edit wins, and Lea hears that a person changed it on purpose.
• A wrong decision comment: reply to it, or tell Lea in chat. She fixes the record and posts a correcting decision comment.