Decision Signs
A profile of how your team makes calls, computed from the project's decision history.
A Decision Sign describes how your team decides: how much evidence it wants, how far ahead it plans, how much risk it takes, how fast it moves, and how often it weighs tradeoffs. It is computed from the decisions recorded in the project, not from a questionnaire.

Where to find it
Sidebar → Decision Signs. You can also open it from Settings → Account → View Decision Sign.
What the page shows
- Your archetype: a name and a one-line description of your team's style.
- Three counts: Recent decisions, Validated hypotheses and Invalidated hypotheses.
- Reasoning Traits: five bars, each with a percentage and a line explaining the figure.
With no decisions in the project, the page shows No decision signs yet. See Decisions for how decisions get into Tattva.
The five traits
Each trait is worked out from the project's latest 100 decisions and their assumptions and actions:
| Trait | Based on |
|---|---|
| Evidence Threshold | The share of assumptions that were validated |
| Time Horizon | The average horizon of the decisions' actions, against 90 days |
| Risk Posture | How low the average confidence of the actions is. Lower confidence means more risk taken. |
| Decision Speed | How many decisions the project has recorded, against 50 |
| Tradeoff Awareness | How many tradeoffs each action lists on average, against 3 |
The archetypes
Tattva picks the first one that fits:
| Archetype | When |
|---|---|
| The Calibrated Optimizer | High evidence threshold and low risk posture |
| The Patient Strategist | Long time horizon and a fairly high evidence threshold |
| The Iterative Operator | High decision speed and high risk posture |
| The Balanced Generalist | None of the above |
The archetype changes as decisions accumulate. With only a handful of decisions, treat it as a first impression.

Why it is useful
- Self-awareness. If a call does not fit your usual pattern, that is a reason to slow down or get a second opinion.
- Onboarding. A new team member sees the team's style on one page.
- Balance. A team with high speed but low evidence threshold knows where to tighten up.
Tips
- Record decisions with their assumptions and tradeoffs. Tradeoffs listed on actions feed Tradeoff Awareness; assumptions feed Evidence Threshold.
- Capture outcomes. Use Capture outcome on a decision in Ontology › Make › Data › Decisions to compare the result with what you expected.