Decisions
A record of a call your team made or proposed, with the assumptions it rests on, the evidence behind it and, later, the outcome.
A decision is a structured record of a call: what was decided, why, what it should achieve, and which assumptions would prove it wrong. Tattva keeps decisions alongside your data, so you can later check whether the call worked.

Where decisions come from
You don't type decisions into a form. Tattva finds or produces them:
- From your documents. When you upload meeting notes, strategy notes or RCA write-ups as
.mdor.txtfiles on Sources, Tattva pulls out the decisions they record: the statement, the context, the expected outcome, the alternatives and the assumptions. A metric document, one with a section holding a SQL query, is not read for decisions: its metrics become definitions in Review. - From discussions. Documents also contain open debates that are not commitments yet. These appear as Discussions. When one becomes a real call, click Convert to decision →.
- From tracker runs. A tracker question in RCA or forecast mode records its finding as a proposed decision: the top cause, the recommended actions, and the assumptions to watch.
New decisions start as proposed.
What a decision holds
- The statement: the call in one line.
- Rationale and context: why it was made.
- Expected outcome and a horizon: what should happen, and by when.
- Alternatives considered: what was rejected.
- Assumptions: each with an "Invalidates if:" condition and the metrics to watch.
- Evidence: the document passages or data behind it.
- Actions: for decisions from an analysis, the steps, each with an expected result, confidence, horizon and tradeoffs.
- Outcomes: measured results, added later.
Where to see decisions
The decisions list (/decisions). It is not in the sidebar. Type /decisions after your Tattva address, or click Browse decisions → on the Reports page while the project has no reports. Each card shows the statement, who created it, when, and how many assumptions and actions it has. The Outcome Ledger below compares expected with actual results.
The decision page (/reasoning/decision/<id>). Click a card in the list. Three tabs:
- Summarised: the top cause and its confidence, the Implementation Sequence of actions, and the Key Assumptions.
- Deep dive: all the Evidence, and the Hypotheses to Watch with what would invalidate each.
- Trail: the inputs at decision time (ontology version, how fresh the data was, status) and how many evidence rows, hypotheses and actions it has.

Ontology › Make › Data › Decisions. The working view, with actions. Expand a decision to read its rationale, alternatives, assumptions and evidence. From here you can:
- Capture outcome: measure the watched metrics now and record a verdict (on track, at risk, off track, invalidated or confirmed).
- Convert to discussion →: it was not really a commitment yet.
- Remove as decision: it should not be tracked. The decision is archived.
The Discussions tab next to it lists open threads, with Convert to decision →.
Statuses
proposed, accepted, invalidated, resolved, archived. Decisions start as proposed. Remove as decision and Convert to discussion → archive them.
Why decisions matter
- You can defend a call later. "Why did we do this?" has one answer, with the evidence as it was at the time.
- You learn whether calls work. Capturing outcomes against the expected result builds the Outcome Ledger.
- You see how your team decides. Decision Signs reads your decision history.
Related
- Track a decision: the step-by-step workflow
- Decision Signs
- Trackers