thesis-tex-writeback

Thesis TeX Writeback

Triggers & routing

• Trigger: tex writeback, thesis tex writeback, md back to tex, chapter writeback, thesis delivery layer synchronization.
• Use when: The chapter main line, terminology, symbols, and figure/table plan are already basically stable at the Markdown layer and need to enter the TeX delivery layer.
• Skip if: The structure is not yet stable, or it is still in the chapter-level restructuring stage.
• Network: none.
• Guardrail: Do not reinvent the structure here; prioritize sending structural issues back to the Markdown layer for handling; the TeX layer is responsible for delivery, not for rethinking.

Inputs

• codex_md/00_thesis_outline.md
• Markdown of each chapter after restructuring
• codex_md/terminology_glossary.md
• codex_md/symbol_metric_table.md
• codex_md/figure_plan.md
• Existing chapters/*.tex

Outputs

• Updated chapters/*.tex
• TeX-synchronized versions of related figures, formulas, and cross-references

Load Order

Always read:

• references/overview.md
• references/writeback_rules.md
• references/consistency_checks.md

Machine-readable contract:

• assets/tex_writeback_contract.json

Workflow

1. Use the Markdown intermediate layer as the source of truth to determine chapter-level and section-level structure
2. Write the stable content back to chapters/*.tex
3. Synchronize figures, formulas, tables, and cross-references
4. Synchronize chapter-opening introductions, chapter-ending summaries, and necessary transition sentences
5. Record which issues must be rolled back to the Markdown layer rather than being forcibly fixed in the TeX layer

Key Rule

If the issue is essentially:

• Unclear chapter role
• Unstable main line
• Insufficient evidence
• Inconsistent terminology

then it should not remain in the tex layer to be solved.