Coverage and Routing

This page reconciles the four university source reports against the current university wiki and the merged v2 structure.

Status Summary

Item	Count	Status
Source reports reviewed	4	complete
Named professors, leads, directors, or research contacts cataloged	95	complete for current source set
Problem-led focus-area pages promoted	6	complete for first pass
Method and capability pages promoted	7	complete for first pass
Work packages promoted	9	complete for first pass
Opportunities promoted	6	complete for first pass
People promoted to standalone pages	16	complete for first pass
Labs promoted to standalone pages	7	complete for first pass
Landscape maps promoted	2	complete for first pass
Unresolved source files	0	all source files routed

Source-by-Source Routing

Source File	Coverage State	Main Outcomes
deep-research-report.md	promoted and routed	operating strategy, Bavaria priority logic, TUM/HM/FAU first-wave lanes, WP-01 to WP-05 seeds
deep-research-report Balanced.md	promoted and routed	applied Hochschulen versus TU logic, packaging and Kempten lane, Munich-first action framing
deep-research-report Monster.md	routed with source-only supplement	expanded ranking set, second-wave people and lab candidates, WP-06 to WP-09 support
RapidDraft Academic & Applied Research Partner Mapping (Monster Brief, v1).md	routed with source-only supplement	ecosystem logic, TUM plus Hochschule plus Fraunhofer stack, benchmark and long-tail sourcing

Promoted Outputs

Action Layer

• 6 problem-led focus pages define where RapidDraft should engage.
• 7 method and capability pages define the technical-method layer inside focus areas.
• 9 work packages define collaboration-ready technical units.
• 6 opportunity pages define the first prepared opportunity queue.
• 2 landscape maps support prioritization inside execution.

Lead Layer

• 16 people are promoted because they directly support a work package or opportunity.
• 7 labs are promoted because they group multiple relevant signals.
• 95 named professors, leads, directors, or research contacts are cataloged in the coverage register.
• Lower-priority names and clusters remain routed in the source layer until they justify action.

Referenced But Not Yet Promoted

These names and clusters are captured in the source layer and index pages, but not yet promoted into standalone action records:

• Nils Meyer
• Tobias Dueser
• Thomas Schaeffer
• Florian Nuetzel
• Tobias Laumer
• Klaus Drechsler
• Ruediger Daub
• Mirko Meboldt
• Jivka Ovtcharova
• Jochen Garcke
• Sabine Roller
• Roland Lachmayer
• OTH Regensburg digital-twin cluster
• KIT IMI and LESC
• KIT IPEK
• Fraunhofer SCAI NDV
• DLR Virtual Product House

Routing Decision Rules Used

• Promote to a work package if the report suggests a reusable technical collaboration unit.
• Promote to a person page if the name is directly useful for outreach, CRM, or Apollo enrichment.
• Promote to a lab page if more than one person or work package clearly points to the same capability container.
• Keep long-tail rankings and benchmarks as source-only when they improve context but do not change the next action.

Remaining Gap

The source folder is fully routed, but not every referenced name is intentionally promoted. That is by design:

• the wiki stays action-first instead of collapsing into a giant directory
• the source layer still preserves second-wave names for later expansion

Open Questions

• Which referenced names should move into the first Apollo-enrichment batch after outreach triage?
• Should the next pass create a dedicated Regensburg cluster and TU Darmstadt lab container?

Sources

• TextCAD/04_Marketing and Outreach/13_Universities/deep-research-report.md
• TextCAD/04_Marketing and Outreach/13_Universities/deep-research-report Balanced.md
• TextCAD/04_Marketing and Outreach/13_Universities/deep-research-report Monster.md
• TextCAD/04_Marketing and Outreach/13_Universities/RapidDraft Academic & Applied Research Partner Mapping (Monster Brief, v1).md