Front Matter Writer (compatibility router)

Triggers & routing

• Trigger: front matter writer, introduction writer, related work writer, abstract writer, discussion writer, conclusion writer, 引言, 相关工作, 摘要, 讨论, 结论.

Purpose: produce the paper-level shell while preserving the current output contract and approval gate.

Load Order

Always read:

• references/overview.md

Read by task:

• references/abstract_archetypes.md for sections/abstract.md
• references/context_projection.md when adjusting how chapter briefs are projected into Introduction / Related Work context
• references/introduction_jobs.md for Introduction body files
• references/related_work_positioning.md for Related Work body files
• references/discussion_conclusion_patterns.md for sections/discussion.md and sections/conclusion.md
• references/forbidden_stems.md before revising any reader-facing prose
• references/examples_good.md and references/examples_bad.md for calibration only

Machine-readable assets:

• assets/front_matter_context.schema.json
• assets/front_matter_context_schema.json (compatibility alias for checklist-aligned naming)
• assets/front_matter_contract.json
• assets/front_matter_templates.json
• assets/front_matter_context_projection.json

Inputs

Required:

• DECISIONS.md with Approve C2
• outline/outline.yml
• outline/mapping.tsv
• citations/ref.bib

Optional but useful:

• GOAL.md
• queries.md
• papers/retrieval_report.md
• papers/core_set.csv
• outline/coverage_report.md
• outline/writer_context_packs.jsonl

Outputs

Keep the current output contract:

• sections/abstract.md
• sections/S<sec_id>.md for front-matter H2 bodies
• sections/discussion.md
• sections/conclusion.md
• output/FRONT_MATTER_REPORT.md
• output/FRONT_MATTER_CONTEXT.json, including the base template bank, any selected domain overlay, and their repository-relative SHA-256 hashes

Compatibility mode