The workflow

How it works

A prompt asks for an output. A workflow defines the stages an output passes through before it can be trusted. You trigger it by email; the ingest loop runs the stages; this page is the window.

Send an email to the ingest inbox

Subject: Deck: Q2 win review
Body:   Build a leadership deck from the attached. Audience is the board.
        (attach your sources — spreadsheets, decks, PDFs, exports)

Or skip attachments and name existing vault material: "use the ACCESS analysis and the Saturn award." A text works too for the naming case (it forwards in as email), but attachments need real email.

Source prep. Inventory the sources — ID, owner, date, status — split facts from assumptions, log every conflict.
Structure. Before any slide or formula, a spec: a deck's narrative spine and claim headlines, or a workbook's tab architecture.
Creation. Build constrained by the packet and the spec. Storyboard before render; raw data before assumptions before outputs.
Verification. A second model reads it as a hostile reviewer and enumerates problems without fixing them, looping back to the builder until the edits stop landing.

The operating ruleUse AI everywhere, but don't let it hide the truth layer. Every claim knows where it came from, every calculation knows what it depends on, every assumption is labeled as one.