Product·The record

Every action, the check behind it
and who said yes.

The assistant and agents write everything they do to one append-only record. Each entry holds what arrived, the facts used, the check that let it run and who approved it. Open any decision and trace it end to end.

Book a discovery call→

One decision, end to end

Example records from a finance inbox. Select a row to see what arrived, what the agent knew, the check that applied and who approved it.

Example recordsfinance inbox

Example recordDR-4471

Invoice 88431 from Meridian Supplies matched and filed

what arrivedPDF invoice 88431 for £2,480.00, received in the finance inbox at 09:04

facts usedOrder MO-2209 at £2,480.00 and a goods receipt signed 11 March. Supplier terms of 30 days, a Finance department fact.

the checkInvoice matching is at level 1, so every item waits in the review queue.

what it didProposed the match to MO-2209 and the receipt, then filed the invoice against the order once approved.

who approvedPriya Raman, accounts lead, in the review queue at 09:12

sourcesThree documents attached, each at the version used

Approved by a personThe action, the check and the approval sit in one entry.

Append-only

Entries are only ever added. The database refuses to let the application edit or delete what the assistant or an agent did. When a person overrides a decision, the override is a new entry.

Tamper-evident history

Significant changes to shared memory are chained with cryptographic hashes. A deleted or back-dated entry shows up when the chain is checked.

Refusals are kept too

When the assistant can’t back an answer, it says so. The refusal and its reason go on the record with the same weight as anything it did.

Read within permissions

Opening the record follows your document permissions. You see what an agent read only if you can open that document yourself.

Shared memory, every fact scoped and sourced

Each fact is scoped to the organisation, a department, a role or a single source, and keeps the document it came from. When two facts disagree, a person settles it.

Example · facts behind invoice 88439

ORGANISATIONThe financial year ends on 31 MarchCurrentFinance policy, version 4

DEPARTMENT · FINANCESupplier terms are 30 days unless a contract says otherwiseCurrentPayables procedure

ROLE · ACCOUNTS LEADSigns off supplier credit notes up to £5,000CurrentDelegated authority schedule

SOURCE · RATE CARDNorthgate Freight, £38.00 per standard palletSupersededRate card 2026-01, still readable and dated

SOURCE · RATE LETTERNorthgate Freight, £41.50 per pallet from 1 MarchSent to a personConflicts with the contract, which fixes rates until 30 June

When the rate letter arrived, the January rate stayed on file, marked as superseded. The letter disagrees with the contract, so the conflict went to the accounts lead to settle.

“Logging who approved what is employee monitoring.”

The record exists so the team can answer for the work. It isn’t there to rate people. Approvers can be pseudonymised in the record, and for Germany and France we bring a works-council pack.

Evidence for an internal review

Internal audit, risk and your data protection officer read the same record your team works from. One decision can be followed from the email that started it to the person who approved it.

How the record is protected →

NextRuns on your Microsoft 365 or Google Workspace.Agents start from an email, a Teams or Slack message, a file or a schedule, and work in about 200 business apps.Integrations →

See one decision traced from what arrived to who approved it.