DeckUse
The lossless PowerPoint runtime for agents.
Existing-PPTX editing is current. Controlled creation and commands remain release-scoped; Word and Excel are planned.
Product pathABOUT DECKFLOW
Document execution should be precise, inspectable, and fit for the job.
DeckFlow gives AI agents and teams distinct paths for working with real documents without flattening every task into one generic tool.
Product orientation
Three primary Products, three distinct responsibilities.
DeckOps
The document intelligence pipeline for agents.
Its format-specific IR contract is future-state and is not proven by the public legacy repository.
Product pathDeckHTML
The web-content and editable-document bridge.
Web-to-PPTX or PNG is current at v0.6.4; PPTX-to-web is testing and dedicated DOCX routes are planned.
Product pathDeckProbe and DeckRender are independent supporting projects. Parse belongs inside DeckOps. Architecture does not prove current formats, operations, interfaces, preservation, or fidelity.
Operating principles
Evidence-led by design.
- 01
Precision before spectacle
Document work should keep the requested change, result, and review boundary visible instead of hiding them behind generic AI output.
- 02
Evidence before capability
Versions, source, fixtures, lifecycle, and limitations determine what the website can claim.
- 03
The job decides the path
Solutions describe the workflow to complete. Products own the technical contract and implementation depth.
Open-source and license boundary
Open-source infrastructure, with mixed project licenses.
- DeckUse
- AGPL-3.0
- DeckHTML, DeckProbe, and DeckRender
- MIT
- DeckOps
- No effective repository license yet
Next steps