/multipart-doc

Build a MULTI-PART DOCUMENT on the mesh: a top index node that consolidates section nodes via @@ embeds — sections individually editable, the index reading (and printing) as one document. Use for proposals, reports, brochures, RFP responses — anything with chapters that must also ship as one artifact. Pairs with /pdf-package for export.

• Instructions: You are building a **multi-part document**: one **index node** + one node per **section**, consolidated so the index reads — and prints — as a single document while every section stays its own node (editable, commentable, versioned, individually linkable). Reference implementations: `Globex/Proposal` (plain proposal) and `UWDeepfield/Overview` (glossy brochure). # 1. Shape - **Index node** (`{Space}/{Doc}`, nodeType `Markdown`): the document. Carries, in order — a title/hero block, the executive summary, a **Contents list**, the consolidated sections, a closing block. - **Section nodes** (`{Space}/{Doc}/{Section}`, nodeType `Markdown`): short PascalCase ids (`Situation`, `Offering`, `Approach`); each self-contained with its own `##` heading. - **The Contents list is the manifest** — a numbered list of links, one per section, each with a half-line abstract: ``` 1. **[The situation](/{Space}/{Doc}/Situation)** — where the process stands today. ``` - **Section ORDER is stated three times and they must agree: Contents order = embed order = `node.order`.** Give every section node an explicit `order` matching its position in the Contents list (`1, 2, 3 …`), set at create time (`"order": 2`) or with `patch {"order": 2}`; give the index node itself an `order` too within its Space (`10, 20, 30 …` in the Space's reading order). The side rail sorts children by `order`, then name — a section without `order` lands alphabetically and the rail no longer reads as the document. Reorder = edit the Contents list, the embed sequence AND the `order` fields together. # 2. Consolidation — the `@@` embeds After the Contents list, embed every section content-only, separated by rules: ``` --- @@{Space}/{Doc}/Situation/$Content --- @@{Space}/{Doc}/Offering/$Content ``` - **`$Content` embeds the section body only** — no node header, no comments (the platform hides embed headers by default; `$Content` is the explicit content-only form). - The `@@` must start its line. Do NOT paste sect…
• Auto mount: yes
• Launches sub thread: no