Decisions

A decision is a record of a choice your team made, kept where the work is rather than in the chat it came from. Six months later the question "why is it done this way" has an answer with a name and a date on it.

Decisions are workspace-wide. They sit in their own section, and they also turn up on the tasks, pages and goals they touch.

What a decision holds

  • A title and the decision itself.
  • A number, D-1, D-2 and so on, unique in the workspace. The number is handed out by the database rather than by whichever screen created the decision, so every way of making one numbers the same way and no two can collide. Decisions that existed before numbering was added were numbered too, oldest first.
  • A status: proposed, decided, or superseded.
  • Who decided it and when, when it has been decided.
  • Tags, for finding it again.
  • Links to the tasks, pages and goals it affects.

Two ways one gets written

A person writes it. New decision, in the Decisions section. Use this for the choice made in a meeting or a corridor, which is otherwise the kind that survives only in somebody's memory.

An agent's question becomes one. When you answer an agent that asked you something, the answer is kept as a decision automatically. That one carries more than a hand-written note: the question as the agent put it, the options it offered and what each would have cost, which files it had read, who answered, and a link back to the run and the task. You decided something in a second and the reasoning survives anyway.

See Tasks and pull requests for how an agent asks.

Superseding, rather than editing

When a decision is replaced, the new one supersedes the old rather than overwriting it. The old decision stays, marked superseded and pointing forward to its replacement; the new one points back.

That is the difference between a record and a note. A note tells you what you think now. A record tells you what you thought then, and when you changed your mind, which is the part that matters when you are working out how you ended up here.

Finding them again

  • By tag. Tags are stored lowercased, and the tag filter is too, so Billing and billing find the same decisions and you do not have to remember which you typed.
  • On the work they touch. A decision linked to a task shows on that task, so the person picking it up reads the choice without going looking.
  • In the work graph, where a decision is a node like any other, connected to what it affects.

Contradictions

Ithura can look across related decisions and point out ones that appear to contradict each other. It is a prompt to go and look, not a verdict: it reads the text and tells you what seems inconsistent, and you decide whether it is. This one needs the AI assistant, which runs on your workspace's own model key. See Setting up AI.

Who can do what

ActionNeeds
Read decisionsMember access
Create, change or delete oneMember access
Link one to a task, page or goalMember access

Guests do not see decisions.

Troubleshooting

What you seeWhat it means
A decision you expected is not in the listCheck the tag filter. Tags match case-insensitively, but a filter you forgot is still a filter.
An old decision still shows alongside its replacementThat is deliberate. A superseded decision is kept and marked, not removed.
An agent's answer did not become a decisionOnly an answer to a question the agent actually asked becomes one. A comment on the task is a comment.
Contradictions are unavailableThat feature needs the AI assistant and a model key. The rest of Decisions works without either.