Hierarchical Issue Map

Stakeholder → Key Business Question → Sub-question. The structural backbone the rest of the model and AI layer reason against.

Why this exists

The issue map is the structural backbone for the rest of the platform — not a Q&A surface. Every KBQ ties to (a) the drivers on Scenarios that resolve it, (b) the levers on Strategy that respond to it, and (c) the evidence grounding the answer. It forces analysts and reviewers to agree on what we need to know before debating numbers. AI narrative belongs downstream (Overview, Strategy fit, What-changed) where it can ground in quantified scenarios — not here, where answers should still come from analyst-curated evidence.

Coverage gap: 1 of 6 KBQs have no linked evidence yet. These are flagged below — ground them before they hit a deck.

Need a new question? Add custom KBQs from the Market Foundation page. Add a KBQ

Sub-questions (2)

What is the elasticity of access to rebate depth?
kbq4.1
Which top 3 PBMs require outcomes contracting?
kbq4.2

Need to ground this question? Upload a source and pin a chunk →

Linked from Market Foundation. Drop new sources into the Evidence Library to ground KBQs before they hit a deck.