How-to guides
Generating Documents
Turn a task's work into a polished, checked, editable file; Word, PDF, Excel, or PowerPoint; with a record of where every fact came from.
When OOMU produces a deliverable, it doesn't just dump text. It builds a real office file from a structured model, renders it, and checks it looks right, then keeps that file; with its version history and provenance; in the Documents door.
What OOMU can produce
| Output | What you get |
|---|---|
| Word document and PDF | An editable .docx plus an easy-to-share PDF, from the same source. |
| Excel spreadsheet | An editable .xlsx with real formulas, formatting, and charts that recalculate. |
| PowerPoint presentation | An editable slide deck with templates and speaker notes. |
Each is generated by a packaged, version-pinned builder running in a contained process; not by model-written code. The model describes *what* the document should contain; OOMU builds the actual file.
Step 1; Ask for a deliverable
You get a document by asking for one, in Chat, a workflow, or a Routine; *"write this up as a Word brief and a PDF," "put these figures in a spreadsheet with a total row," "make a five-slide summary."* OOMU assembles the content, then builds the file and registers it under the current Project and Task.
For factual documents built from your Project or task inputs, OOMU attaches source references to the content, so a claim can be traced back to the file or step it came from.
Step 2; Preview and read OOMU's checks
Open the document in Documents to see it rendered inside OOMU; a page preview and an outline of the contents. OOMU runs its own verification and tells you the result plainly:
- "OOMU checked that every page looks right."; the file was rendered and mechanically inspected for blank pages, clipped or overlapping content, missing fonts, and overflow.
- "OOMU has not finished checking every page."; verification is still running, or couldn't complete.
For spreadsheets, formulas are recalculated; for presentations, slides are rendered and visually checked. A document is never marked finished on the strength of "bytes were written"; the structural and visual checks have to pass first.
Step 3; Revise in plain language
Choose Make a change and describe the edit; *"add a risks section," "make the totals bold," "cut slide 3."* OOMU patches the underlying structured model and produces a new version. Every version is kept, with its build status, verification result, source summary, and file size, so you can compare or roll back.
Step 4; Export
Choose Export and pick what to write; the Word document, the PDF, or both (spreadsheets and decks export their native file). Exporting writes to a location you explicitly grant; OOMU builds into private staging until that grant succeeds. Alongside the files, OOMU saves a small verification receipt; a signed record of the file hashes, the task that produced them, the builder identity, and the verification outcome.
Why the receipt matters. The receipt is what lets you (or a colleague, or an auditor) confirm months later that a specific PDF is the exact file OOMU produced and verified; not something altered afterward.
Related
- Building Automated Workflows: produce documents as a workflow step.
- Scheduling Routines: generate and deliver a document on a schedule.
- The Delegated-Work Loop: how documents fit the evidence model.