# Decision memo (trade memo)

Written by the Decider role from the whole packet. One page. Saved with the date in its name, for example `2026-10-06-MNQ-memo.md`, or pasted into your journal's notes column.

```text
DECISION MEMO — {setup name} — {instrument} — {date}

1. Summary:      {one sentence}
2. Rules:       PASS {n} · FAIL {n} · CAN'T TELL {n}
3. Best point for:   {one line} (source: {section})
4. Best point against: {one line} (source: {section}) · ANSWERED / PARTLY / UNANSWERED
5. Risk:        TEAM {OPEN/CLOSED} · budget {money}/{R} · trades left {n} · blackouts {times}
6. Card:        entry {…} · stop {…} · target {…} · size {…} · {y}R to target · valid {hh:mm–hh:mm}
7. Score:       {1–5} — rubric line: "{quote}"
8. Becomes a 1 if:   1) {observable event} 2) {observable event}
9. Verdict:      TAKE IF TRIGGERED / PASS / WAIT — reason: {one line}  (the execution agent acts on this line)
```

## Scoring rubric (the same lines as the Decider prompt and the team setup)
- **1** — any context rule FAIL, any no-trade condition met, the Risk Manager says CLOSED, or the card is outside the risk budget.
- **2** — rules pass, but two or more context rules are CAN'T TELL, or the Bear has an unanswered point about event risk or location.
- **3** — rules pass, at most one CAN'T TELL, the Bear's best point is partly answered.
- **4** — all context rules PASS, the regime fits the setup, the Bear's points are answered with evidence, the card is inside budget.
- **5** — everything in 4, plus the watch zone sits at a level named in the Analyst brief, and no scheduled event inside the card's valid window.

The score describes the quality of the evidence for this plan, by your rules. It is not a probability and it is not a prediction.