Format
Core package, guides, transforms
dedocs is layered on purpose. The exact package core stays authoritative. Guides help orientation. Transforms are readable commands on top of that core.
Shape of a file
The top-level file starts with one `\dedocs[...]` header, then optional guide blocks, optional transform blocks, and finally the explicit package parts.
Loading format shape...
1. Core package
Every package part is present. UTF-8 parts stay readable. Binary parts stay base64. Untouched content is preserved exactly when the package is rebuilt.
\part[path="word/document.xml", mediaType="application/xml", encoding="utf8", bytes="...", sha256="...", boundary="..."]
...
\end{part}2. Guide layer
Guides are generated, never authoritative. They exist to help humans and AI orient quickly without scanning raw OOXML first.
\guide[name="document-paragraphs", part="word/document.xml", format="paragraphs", boundary="..."]
\p[index="0000", style="Heading1"] Introduction
\p[index="0001"] This is the first paragraph of the introduction.
\end{guide}3. Transform layer
Transforms are the human-readable semantic commands. They compile onto exact package parts and fail loudly when anchors drift.