Flows and evidence packs

Closing a quarter is one job that may contain three requests and a publish. Afterwards the question is not "which approvals were there in October" but "what happened on the Q3 close". A flow answers that question, and an evidence pack is the answer written down.

What a flow is#

A flow groups the approvals, reviews, requests for information and reports that belong to one piece of work. Usually an agent starts one when a job will take more than one request, and adds each request to it as it makes it. Nothing is added to a flow from its page.

A flow groups; it does not drive. It has no order of its own and no step waits on another: each request inside it is decided exactly as it would be on its own. An agent that wants to do one thing after another simply does them in that order.

Reading a flow#

Flows lists the pieces of work in progress and those finished. Each shows who started it, how many steps it has, and how many are waiting on somebody.

A flow's own page lists its steps — each approval, review, request or report, with its status, linking to where it is read — and a timeline of everything that happened across all of them in the order it happened: who asked, who approved or rejected, who asked for changes, who answered, what was published, what was commented on, and the gate's checks. A report that belongs to a flow links to it as well.

Finishing or calling off a flow#

Only whoever started a flow can close it, and only while it is open. If a flow was started as you — by an AI tool connected under your name, for instance — its page offers you two buttons. A flow started by an agent identity is closed by that agent.

Mark it done

The job is finished. The history records it as completed.

Call it off

The job was abandoned. The history records it as called off, which is not the same thing.

Evidence packs#

An evidence pack is everything recorded about one piece of work, for an auditor, a client or a colleague who was not there. There are two kinds of subject: a flow, and a report — the approvals, reviews and requests that point at it, and its own history of versions.

What a pack contains

• The subject: what it is, its status, who started it and when, and the organisation.
• Every step: who asked, whether an agent asked, who was asked, and what each of them said with their note, in order.
• For an approval: the description, the risk, the key factors and links, the questions and answers, and the concerns your organisation's ethics rules raised, beside the approver's reason for going ahead.
• For a review: the instructions, the verdicts and notes, and how many comment threads were opened.
• For a request for information: the questions and every submitted answer. Drafts are not included.
• The timeline: every recorded event, with who did it and when.
• Legal holds in force over the subject when the pack was taken. See Security, audit and legal holds.
• An integrity block: a SHA-256 digest of the pack itself.

The digest shows that a pack has not been altered since it left Deliverd. It says nothing about the records themselves; what stands behind those is that the audit log refuses updates and deletions at the database level — tamper-evident history. The pack says both of these things in its own words.

Downloading one

Organisation owners and administrators see an evidence pack panel on a flow's page and on a report's page. Anyone else can read the flow but not export it: a pack is a portable copy of the notes, verdicts and answers, and once downloaded it has left the product.

A pack is a file: share it the way you would share any other. Your organisation's audit log records the same events by date rather than by piece of work.