Best trigger conditions
- First 90 days in role or platform reset.
- Post-incident risk review and board follow-up.
- Need objective risk baseline before roadmap commitments.
CTO path
Get a decision-ready risk baseline without consulting overhead.
Use this when leadership needs clarity on where technical risk concentrates, what change amplifies impact, and what should be handled first.
What this gives leadership
- Top risk folders and blast-radius concentration.
- Evidence-linked claim set for engineering verification.
- Explicit unknowns and confidence context.
Delivery outputs
Fast baseline pack.
Leadership view
- `exec-risk-1pager.md`
- `risk-overview.md` and recommendation summary
- Risk maps and matrix for prioritization framing
Engineering verification view
- `evidence-index.json` and `evidence.json`
- `blast.json`, `edges.json`, and folder graph outputs
- `unknowns.json` for explicit blind spots