dedocs
Single-file source for exact `.docx` packages. One inspectable text artifact for the whole package, explicit semantic commands on top, exact OOXML underneath.
Loading sample...
Your document, three ways
Word remains the source ecosystem. dedocs gives you a text-native working surface. Git and AI get a single file instead of a zip archive.
Make real document edits with explicit commands
\replace-text[part="word/document.xml", count="1"]
<<
This is the first paragraph of the introduction. It contains some text about platform governance and political advertising.platform governance, political advertising, and auditability.
\insert-comment[part="", index="0001", match="platform governance", count="", expectedText="This is the first paragraph of the introduction. It contains some text about platform governance and political advertising.", expectedStyle="", author="Dedocs", date=""]
<<
...text about platform governance comment: Clarify the exact policy boundary here.
Touched parts: word/document.xml, word/comments.xml, word/_rels/document.xml.rels, [Content_Types].xml
\insert-table-after[part="", index="0003", expectedText="Methods", expectedStyle="Heading1", caption="Table 1. Example metrics", style="", headers=""]
<<
Table 1. Example metrics
| Metric | Value |
|---|---|
| Ads collected | 268,635 |
| Confirmed advertisers | 192 |
Every .docx becomes one readable source file
The exact package core stays intact. Guides help orientation. Semantic transforms stay explicit and inspectable.
Loading format...
Exact core, readable commands, static proof
Package exactness
Untouched package parts round-trip byte-for-byte. XML stays UTF-8. Binary stays base64.
Readable orientation
Generated paragraph guides keep humans and AI oriented without becoming the source of truth.
Strict semantic edits
Commands are visible, scoped, and fail loudly when anchors drift or expectations stop matching.
Part-by-part proof
Compare original and rebuilt `.docx` packages directly and see exactly which parts changed.
AI-native working file
Give an agent one source file instead of a zip archive plus an OOXML directory tree.
No hidden backend
The site, samples, and downloads are generated from the repository itself and served as static files.
Built to be inspectable before it is magical
Why agents can work with it
The file is plain text, bounded, explicit, and deterministic. Guides and transforms reduce the amount of raw OOXML an agent has to reason about.
Where the boundary stays hard
The browser can preview transform effects. Exact package compile and verification still run in the CLI, where the real `.docx` tooling belongs.
Current semantic surface
Clone the repo and run the proof loop
git clone https://github.com/jqdwdty/dedocs.git && cd dedocs
Then run npm test and npm run build:site. Everything on this site is served from committed static files in docs/.