Skip to content

Give agents the right wayto work withrealdocuments.

Keep a document in state. Complete one bounded task. Or move between Office files and HTML.

Choose a productUse a ready-to-use Solution
What shape is the document job?Choose by responsibility
01The agent will return to the same document.Continue the work in state.DeckUse02The input, task, and result are bounded.Finish one document task.DeckOps03The job moves Office content into or out of the web.Bridge Office files and HTML.DeckHTML
DeckUse + DeckOps share DeckFlow RuntimeDeckHTML is independent

Start with the lifetime of the work.

These are three different responsibilities, not three levels of one tool. The architecture should become useful only after the product choice is clear.

01
Iterative · stateful

Keep working on the document.

DeckUse is the execution model for continued document work: explicit operations, persistent working state, validation, and traceable output.

Best fit · the document remains part of the workflow
workspace / quarterly-review.pptx
  1. 01initidentify working document
  2. 02inspect / querylocate supported content
  3. 03applyexecute explicit operation
  4. 04validatecheck the intended result
  5. 05commitretain the next known state
Real release-scoped contract · illustrative document · evidence boundary required
02
Task-oriented · lightweight

Complete the task and move on.

DeckOps is the execution model for a bounded document job. It takes one explicit task from input to result without asking the agent to maintain a long-lived workspace.

Best fit · one clear task, with PDF as the clearest entry case
Input
report.pdf

one document

Explicit task
Parse to IR

then use supported operations

Result
task artifact

with limits attached

Grounded explanatory artifact · current verbs remain release-scoped
03
Office ↔ HTML

Bridge Office files and HTML.

DeckHTML is the independent interoperability product for moving document content between Office and browser-native workflows. Exact formats and directions stay release-specific.

Best fit · the document-to-web relationship is the job
PPTXDOCXXLSX
Q3 operating review
deck.html
<main data-deckhtml>  <h1>Q3 Review</h1>  <section>…</section></main>
Grounded explanatory artifact · Office formats, directions, and fidelity remain release-scoped

One Runtime, two deliberate ways to work.

Choose the working model that matches the job. DeckUse keeps document context alive; DeckOps keeps one task focused and bounded.

How should the agent carry the work?DeckFlow Runtime
When the document stays in the workflow

DeckUse

A persistent document workspace for repeated, explicit changes across an ongoing agent workflow.

  • Retain working stateReturn to the same logical document
  • Apply explicit operationsMake scoped, reviewable changes
  • Validate and traceCheck the result before work continues
Choose DeckUse
When the job has a clear stopping point

DeckOps

A task-scoped execution path for one document, one explicit job, and a bounded result.

  • Define one taskKeep input, intent, and outcome explicit
  • Package supported operationsUse the capabilities available in the release
  • Return result and limitsClose the job with a clear boundary
Choose DeckOps
Available when the job calls for them
InspectProbe for bounded document evidence
RenderCreate visual representations for review

Capabilities are composed around the job and remain release-scoped.

Compare the execution models

Office files, meet the web.

DeckHTML is the dedicated interoperability layer between Office documents and HTML. Use it when content needs to enter browser-native workflows—or return to the Office files people already review, present, and share.

View DeckHTML source
Office workspaceFamiliar files
Presentation.pptx
Document.docx
Workbook.xlsx
Quarterly operating review
Office → HTML
DeckHTML
HTML → Office
Browser workflowStructured HTML
deck.htmlHTML5
1<article>2 <h1>Quarterly review</h1>3 <section data-chart>…</section>4</article>
Quarterly review
Bring documents into web workflowsGenerate, automate, edit, or deliver through HTML-based systems.
Return web output to familiar filesContinue review, presentation, and collaboration in Office workflows.
Grounded explanatory · Office formats, conversion directions, editability, and fidelity remain release-specific

Need a presentation result now?

Translate, Generate, and Revamp are ready-to-use Solutions for existing presentation work. They are direct service entrances—not additional Products.

These services sit under Presentation Workflows. Document Automation, Document Intelligence, Document Governance, and Presentation Workflows remain the four job-led Solution families.

Explore all Solutions
Solution familyStart from the jobRoute without changing Product IA
Document Automation

Automate a document job with visible operations and results.

DeckUse, DeckOps, or DeckHTML by the actual task.

Document Intelligence

Preserve structure before an agent reasons or acts.

DeckOps direction; DeckUse for current PowerPoint work.

Document Governance

Keep operations, evidence, and output inspectable.

DeckUse or DeckOps under their own lifecycle.

Presentation Workflows

Translate, generate, revamp, or deliver presentation work.

Use the services above; use DeckHTML for web-authored delivery.

Choose the Product. Then choose the interface.

Quickstarts, APIs, SDKs, CLI, source, examples, and Playground are adoption paths—not a second Product hierarchy. Only confirmed destinations enter implementation.

Explore developer paths