Landscape Maps¶
This section is the analytical support layer inside 03 - Execution. It turns long-form research reports into visual and decision-oriented summaries that help prioritize work packages and opportunities.
Why This Section Exists¶
The university research is dense and cross-cutting. A good ecosystem map should make it obvious:
- which problem spaces matter most
- which methods sit underneath them
- which labs or people should be mapped next
- where RapidDraft should engage versus just monitor
Recurring Map Types¶
| Map Type | Purpose | Decision It Should Unlock |
|---|---|---|
| Problem to Method to Lab | shows how a product problem maps to technical methods and then to candidate labs | where to enrich next |
| Work Package x Lab | compares candidate strength across work packages | which lane deserves outreach first |
| Physics x Readiness | highlights where research is deep versus collaboration-ready | where to monitor versus engage |
| RapidDraft Engagement Overlay | marks where we are active, targeting, or only watching | what to deprioritize despite interesting signal |
Current Starter Map¶
Rules¶
- Add a map only if it helps prioritize action, not just summarize research.
- If a map does not change a work-package or opportunity decision, it probably belongs in source notes instead.
- Keep map pages explainable enough that an agent can reuse them without rereading the raw reports.
Open Questions¶
- Should these maps stay in Mermaid and Markdown tables, or later move to generated SVGs?
- Do we want one summary page per problem space once the leads layer grows?
Sources¶
- Structure review and synthesis from the May 15, 2026 working session