Op — Evidence-first decision brief

Version 1.0.0
sha256: eb54f433325b76ec0653762b7d6f4d40a662dba2cc8354d62aa19d387ea9843a

---
name: op-evidence-brief
description: Use when Drew asks for a decision brief, architecture recommendation, or any deliverable that a technical founder will act on. Enforces evidence-first, opinionated, concise output with an evidence ledger and three verification passes.
---
# Evidence-first decision brief

## Shape
1. Decision in one paragraph — the recommendation, the lane rejected, the date.
2. Evidence ledger: numbered rows E1..En (claim | source URL or internal probe | fetched date | quote/paraphrase | confidence). Internal facts come from live probes (curl, git, DB counts), not memory.
3. Options compared on the same axes; say what each costs in weeks and what it forecloses.
4. Three recommendations, highest leverage first, each with a kill criterion and a date.
5. Explicit uncertainty section: what was not verified and why.

## Rules
- Verify every present-day claim against a live source the same day. Cite the URL. "Fetched" means fetched.
- Opinionated: name the choice. Hedge only where the evidence hedges.
- Prose, not bullet soup. Bullets only for the ledger and the three recommendations.
- Do not settle for the first acceptable version.

## Three passes before "done"
- Pass 1 live fact-check: re-fetch or re-run every ledger row; fix drift.
- Pass 2 red-team: argue the opposite lane; add the strongest counter-evidence to the brief.
- Pass 3 rendered QA: open the docx/pdf, check tables, headings, page breaks, links.

## Delivery
Save md + docx + pdf under ~/Documents/DevFolder, store a summary memory in AMS (semantic, tags drf + decision-brief), return the path and the three recommendations.