# Verdicts and disagreement

> The three verdicts an adviser can give, why consensus is never required, and why adviser views never decide for you.

Status: Available

Each final view references one proposal version and states a verdict:

| Verdict | Meaning |
| :--- | :--- |
| `APPROVED` | The adviser supports this version of the proposal. |
| `REJECTED` | The adviser opposes it and keeps the objection on the record. |
| `INSUFFICIENT_EVIDENCE` | The adviser cannot judge it with the evidence available, and says what is missing. |

## Disagreement by design

Two approvals and one rejection are a valid outcome. A meeting is never extended to manufacture unanimity, and a polished summary must not erase an objection, missing evidence or an adviser's dissent. In the recorded example, the Marketing Manager's `INSUFFICIENT_EVIDENCE` stays beside the recommendation.

## Your decision is separate

Adviser views and your decision are separate records. In the recorded example the decision stays `pending`: inspect both with [`decision`](/docs/guides/history-and-decision/). In the live preview, explicitly accept, reject, modify, defer or request investigation; no majority makes that choice for you. A material modification preserves old views as stale for the resulting proposal.

Confidence scores (0 to 100, the adviser's declared assurance, never a calibrated probability or a voting weight) are included in the implemented live meeting contract; the recorded decision does not include them. [Live workflow and qualification limits](/docs/first-real-meeting/).