Best trigger conditions
- Inherited repo or system with unclear risk concentration.
- Modernization, migration, or vendor-selection decision in flight.
- Need to sequence next 30 to 90 days before delivery expands.
Modernization path
Get a clearer decision before inherited-system work spreads.
Use this when a team has inherited a messy system, needs to decide what to modernize first, or wants a harder technical read before migration, rescue, or roadmap commitments.
What this gives the decision owner
- Architecture decision memo with risk framing.
- Explicit unknowns and confidence context.
- Priority sequencing for what to tackle first and what to defer.
Delivery outputs
Fixed-scope decision pack.
Decision layer
- Architecture decision memo
- Priority sequencing for next 30 to 90 days
- One readout for alignment and next-step clarity
Evidence layer
- `evidence-index.json` and supporting artifact pack
- `blast.json`, `edges.json`, and impact concentration outputs
- `unknowns.json` for explicit blind spots