Deliverables
What a mandate can hand back today, what is written but never yet produced by an agent, and what does not exist at all.
Four kinds of thing come out of a desk, and they are not equally proven. This page separates them by evidence, not by ambition.
| Deliverable | What it is | Evidence |
|---|---|---|
| Canvas module | A chart or a panel opened on the canvas by a tool call, filled from a registry preset. | Observed in live runs |
| Trace | One line per phase, per tool, per process, with the raw output available underneath. | Observed in live runs |
| Blocked result | A named refusal when the question cannot be answered at the as-of date, or when no engine exists. | Observed in a live run |
| Workbook (.xlsx) | A spreadsheet whose formulas stay live, pointing at the declared facts. Written natively and reopened for verification. | Written, tested and packaged — never produced by an agent |
| Deck (.pptx) | A 16:9 committee deck rendered from the same dossier as the workbook, so the figures cannot diverge. | Written, tested and packaged — never produced by an agent |
| Memo (.pdf) | An A4 memo with selectable text; a page carrying no text is refused. | Written, tested and packaged — never produced by an agent |
| Bundle of the three | All formats or none, with a sealed manifest carrying digests, sources, computed values and limits. | Written, tested and packaged — never produced by an agent |
#The workbook contract
A workbook is not a rendering of an answer. It is six sheets, and the separation between them is the point: Cover, Inputs, Model, Output, Sources, Checks. Assumptions live apart from facts, facts live apart from the calculation, and the calculation is a formula rather than a value someone typed.
- A fact carries a label, a value, a unit, a period and a source identifier. A fact without a source is refused before the file is written.
- A source identifier points at a declared source, never at a bare URL — two facts from the same document must point at the same document.
- Output and Checks carry real formulas, so the file recomputes when an input changes.
- A check states what was expected, what was obtained and a tolerance, and reports pass or gap.
- The file is reopened by a different library than the one that wrote it. A file that does not reopen is deleted rather than shipped.
- The writer returns a fingerprint: byte count, SHA-256, sheet count, fact count, check count.
Two separate libraries do the writing and the re-reading, deliberately. A single library that both wrote and read back would share its own bugs with itself, and a corrupted file would validate cleanly. The formats themselves are a published international standard, not a private container 3.
EvidenceEvery step of that chain has a test: the tool call, the deposit, the composition, the file on disk, the reopening, the formulas found again. What has not happened is a real agent, in a real session, calling the tool. Until that is observed, the engine is not declared delivered 2.
#Why a missing format is refused early
A request for a deck is refused before any process starts, and the refusal names the missing engine. This is not politeness. An earlier version accepted the request and spent 9.4 million tokens discovering, at the end, that nothing could produce the file. Preflight turns that into a refusal that costs nothing, and the refusal was observed on screen.
LimitNo deck and no PDF is drawn anywhere on this site. Drawing one in HTML to fill the gap would be the only false thing here.
#How this page will be updated
The table above has one row per format and one evidence column. When the core exports a signed manifest of what it can produce, this page reads that manifest and the rows change state on their own. Nothing here needs rewriting for a format to move from tested to observed.
#Sources
- Finexia OS — product state at 0.0.23FinexiaInternal document, not published
- Finexia OS — handover report 0.0.22FinexiaInternal document, not published
- ISO/IEC 29500 — Office Open XML File FormatsISO/IEChttps://www.iso.org/standard/71691.html
Read next
More in Product
- The deskA recorded run of the app, chapter by chapter, from its captures.
- Mission WorkspaceWork, Deliverables, Sources, Activity — one scrolling panel, no conversation in it yet.
- The notchWho is working, what landed, and Stop — without bringing the window back.
- DemonstrationsNine chapters, from the first launch to the workbook that leaves the desk.
- Finexia CasefileOne mission on the installed application, chapter by chapter — including what it did not produce.
- ProvenanceEvery conclusion keeps its trail back to a dated source.
- SecurityCapabilities per role, keys in the keychain, no write path to a broker.