Use this block as the direct handoff from suite discovery into projects/PROMPT-GENERATE-PROJECT-PACK.md. Keep the headings and field names stable.
1. Project identity and suite shape
- project directory name:
- project title:
- suite/documents:
- intended deliverables:
- short charter:
2. Normative scope and boundaries
- in scope:
- out of scope:
- cross-document boundaries:
- required clean-room capabilities:
3. Authoritative corpus and evidence routing
- authoritative source corpus:
- informative/background material:
- runtime or observed-evidence surfaces:
- authority rule when sources disagree:
- section-to-source routing notes:
4. Project-specific references and dependencies
- normative references:
- informative references:
- internal dependencies:
- terminology owners:
- citation hygiene exceptions, if any:
5. Front-matter inputs that remain project-specific
- per-document titles:
- authors/editors and affiliations:
- stream / submission type / intended status:
- abstract anchors:
- provenance or special boilerplate rules:
- metadata overrides to inherited defaults:
6. Planned briefs
For each planned briefs/<name>.md file, provide:
- document owned
- scope
- normative heart
- dependencies
- exclusions
- edge cases
7. Optional examples or staged support material
- example seeds needed:
- if yes, files to create under
examples/: - staged support material under
references/: