A Drafting Sequencing Specification for the Document Engineering Textbook Series

The Document Engineering textbook series (Vol 0– 5: Foundation, File Systems, Markdown, LaTeX, Citations, Diagrams) for Vietnamese learners aged 14 and up is constructed through parallel sub-agent dispatch — a writing-production architecture in which multiple drafting agents work concurrently on chapter-level deliverables under a single human orchestrator. Parallel dispatch collapses calendar time relative to solo human pace but exposes a coordination question that solo authorship hides: in what order, and in what concurrency pattern, should the volumes be drafted such that each subsequent volume can cite, reference, and extend the previous one without re-drafting the prior volume? This paper specifies the drafting sequencing for the series. It reframes the original V1-X-001 question (release sequencing, commercial) into a production-internal question (drafting sequencing, no commercial gating per program-level scope rule) and derives a four-phase dispatch roadmap from three sources: the cognitive prerequisite ordering recorded in the series architecture document; the curriculum-sequencing literature originating with Reigeluth's elaboration theory and the prerequisite-mapping tradition that runs from Gagne to contemporary instructional-design practice; and the softwareengineering dependency-graph literature on Design Structure Matrices, information hiding, topological build systems, and parallel-execution coordination from open-source documentation projects. The derived roadmap dispatches Phase 3 as Vol 0 + Vol 1 + Vol 2 in parallel (all three depend only on the architecture document, not on each other at draft-creation time), Phase 4 as Vol 3 + Vol 4 in parallel conditional on Phase 3 audit pass, and Phase 5 as Vol 5 conditional on Phase 4 audit pass. Five operational rules — parallelism-safety, blockeridentification, dispatch-batch-size, audit-gate, and rollback — are specified at a level executable by an orchestrator agent. The roadmap matches what the elix-researches program actually executed between 2026-04-22 and 2026-04-26; this paper extracts the implicit specification into an explicit one and adds the literature anchoring that converts the operational pattern into a reusable artefact. Three open questions — automation of the audit gate, cross-paper concurrency rules under multi-textbook conditions, and the boundary between draft sequencing and edit sequencing — are flagged for downstream Layer H work.