Resources
This section is the support layer for the university wiki. It houses evidence, operating decisions, coverage reconciliation, and compact authoring guidance.
Resource Stack
| Resource |
Use It When |
Primary Page |
| Evidence and intake |
you need to verify where a claim came from or what has been routed already |
this page |
| Coverage artifacts |
you need counts, routing outcomes, or the full non-promoted name set |
Coverage and Routing and Professor and Lead Coverage Register |
| Operating decisions |
you need the durable structural rules for the wiki |
Operating Decisions |
| Authoring guidance |
you need to add or reshape a page without overgrowing the wiki |
Authoring Guide |
Evidence and Intake Policy
- Raw deep-research reports stay here as evidence.
- The working memory should move into focus areas, work packages, execution pages, and leads.
- Agents should not need to reread the same long report once the relevant knowledge has been routed.
- Source paths should be recorded relative to the shared
TextCAD/ root so the same references stay readable on both Windows and macOS Codex setups.
Current Intake Set
| Source |
Status |
Route Outcome |
deep-research-report.md |
routed and promoted |
core strategy, ranking logic, first-wave people, WP-01 to WP-05 |
deep-research-report Balanced.md |
routed and promoted |
Bavaria priority map, applied Hochschule logic, packaging and DFM lanes |
deep-research-report Monster.md |
routed with source-only long tail |
expanded people and lab candidates, WP-06 to WP-09, second-wave references |
RapidDraft Academic & Applied Research Partner Mapping (Monster Brief, v1).md |
routed with source-only supplement |
ecosystem maps, TUM/Hochschule/Fraunhofer stack, benchmark and sourcing support |
Intake Workflow
- Read source report.
- Route findings into focus areas.
- Promote durable collaboration units into work packages.
- Create lead or opportunity records only when they help action.
- Reconcile what was promoted, routed, or kept source-only in a coverage page.
Coverage Ledger
Authoring Notes
- Blank reference templates are intentionally kept one click deeper through the Authoring Guide, not promoted directly in the main nav.
Open Questions
- Should source digests be added here later for very long reports?
- Do we want the next coverage pass to include direct CRM-field extraction status?
- Should the resource layer later separate evidence, authoring, and operations into distinct sub-index pages?
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