package-exact · static site · MIT license

dedocs

Single-file source for exact `.docx` packages. One inspectable text artifact for the whole package, explicit semantic commands on top, exact OOXML underneath.

sample-report.dedocs -> document preview
dedocs source
Loading sample...
document view
Loading preview...

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.

.docx Word package
.dedocs single-file source
git + AI review and editing surface

Make real document edits with explicit commands

Command
\replace-text[part="word/document.xml", count="1"]
<<
Guide-level effect

This is the first paragraph of the introduction. It contains some text about platform governance and political advertising.platform governance, political advertising, and auditability.

Command
\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=""]
<<
What changes in the package

...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

Command
\insert-table-after[part="", index="0003", expectedText="Methods", expectedStyle="Heading1", caption="Table 1. Example metrics", style="", headers=""]
<<
Document preview

Table 1. Example metrics

MetricValue
Ads collected268,635
Confirmed advertisers192

Every .docx becomes one readable source file

The exact package core stays intact. Guides help orientation. Semantic transforms stay explicit and inspectable.

dedocs excerpt
Loading format...
Guide preview
Loading guide...

Read the full format overview →

Exact core, readable commands, static proof

Core

Package exactness

Untouched package parts round-trip byte-for-byte. XML stays UTF-8. Binary stays base64.

Guides

Readable orientation

Generated paragraph guides keep humans and AI oriented without becoming the source of truth.

Transforms

Strict semantic edits

Commands are visible, scoped, and fail loudly when anchors drift or expectations stop matching.

Verification

Part-by-part proof

Compare original and rebuilt `.docx` packages directly and see exactly which parts changed.

Prompt surface

AI-native working file

Give an agent one source file instead of a zip archive plus an OOXML directory tree.

Static docs

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/.