World-Office: Conformance-Driven Progress on an Independent Office Suite
Office documents are the hardest interoperability problem in any sovereign digital workplace. Mail, files, and chat have mature open-source answers; the office stack — editing docx, xlsx, and pptx reliably in the browser — is where sovereignty projects still struggle. World-Office is openEduSuite's attempt to close that gap: an independent office suite written in Rust, whose progress is measured by conformance tests rather than claims.
From Prototype to Production
The project started with a server prototype that proved the concept but not the engineering bar. That first implementation was retired in September 2026. The production document server today is a native Rust codebase — a docx renderer and its own OOXML processing crates — serving the suite's editors, with WOPI as the integration layer into OpenCloud so that files open and save directly from the cloud storage users already work in.
Current state, in one view:
| Component | Status |
|---|---|
Document editor (docx) |
In production use |
Spreadsheet editor (xlsx) |
Ported to the production stack |
Slide editor (pptx) |
Ported to the production stack |
| PDF export | Native implementation |
| Collaboration server integration | WOPI against OpenCloud |
Measured, Not Claimed
The defining rule of the project: no feature counts as done until an automated test compares its output against an oracle. Three mechanisms carry that rule:
A feature register with stable IDs. Every required behaviour lives in a versioned register of feature IDs, and a drift gate fails CI when product code and register disagree. The current register tracks a stable set of document-format features.
Cross-engine conformance. The renderer's output is normalised into an intermediate representation and scored against reference renders. On simple documents the text-geometry fidelity against the reference render reaches 1.0; on table-heavy documents it is around 0.85 — an honest number that tells us exactly where layout work remains. Visual pixel gates use published baselines rather than vanity thresholds; the headers-and-footers gate, for example, records its starting point openly at 17.2 percent and tightens from there.
A differential formula oracle for spreadsheets. A growing suite of spreadsheet cases compares the World-Office formula engine against a reference implementation. The first 30-case baseline scores 8 of 30 — the baseline exists precisely so that every improvement is visible, with roughly 450 spreadsheet functions on the roadmap.
Decided Scope
Rebuilding an office suite needs boundaries as much as code. The scope decisions taken so far:
- Formats: OOXML (
docx,xlsx,pptx) and ODF (odt,ods,odp), covering both major format families. - Parity reference: the OnlyOffice® web GUI serves as the visual and behavioural compatibility target; LibreOffice® remains a secondary format-interop cross-check.
- Out of scope: exotic legacy formats and diagram formats — the surrounding file stack already routes such files correctly, including a MIME-type fix that made Visio drawings open reliably again.
Lessons from Building in the Open
Three lessons worth passing on:
- Automation needs guardrails. A scheduled automation job once wiped uncommitted work on the development server. The work was recovered by replaying session transcripts — and the job was fixed. Agents and timers that touch a repository must never be allowed to destroy uncommitted state.
- Test infrastructure lives apart from product code. The conformance harness, register, and corpora live in their own repository, so product crates stay clean and the register versions independently.
- Honest baselines beat vanity metrics. Publishing an 8/30 or 17.2 percent number feels uncomfortable and is exactly why it works: progress becomes a ratchet, not a marketing line.
What's Next
- Spreadsheet formula coverage — climbing the differential oracle toward the full function set.
- ODF depth — bringing
odt,ods, andodphandling to the same conformance standard as OOXML. - Spreadsheet and presentation conformance — extending the register-and-oracle pattern beyond documents.
Call to Action
- Follow the work: the conformance methodology and harness design are documented in the project repository.
- Test with us: real-world documents are the most instructive corpus — broken files teach a renderer the most.
- Get involved: join the openEduSuite community if document sovereignty is on your agenda.
Documents are where sovereignty is won or lost — so we measure, not promise.
Trademark notice: OnlyOffice® is a registered trademark of Ascensio System SIA. LibreOffice® is a registered trademark of The Document Foundation. World-Office is an independent project and is not affiliated with, endorsed by, or sponsored by either party. All other product names are trademarks of their respective owners.
