The register, on a demo firm.

Every request is tied to one client; nothing runs without a client ID

Every call carries a client_id; a request without one returns 400 in the demo run. Artefact: demo log, 4 requests, one rejected

With two demo clients loaded, client 1's output contains no client 2 records

Two demo clients loaded, client 1 output inspected line by line; no client 2 record appears. Artefact: two-client run log, output attached

Stored files and caches are separated per client

Storage paths are prefixed per client; the listing shows both prefixes. Artefact: storage listing, 2 prefixes

AI prompts contain only the current client's data

Prompt captured for the run contains one client's figures only. Artefact: prompt log, 1 client

Staff see only the clients assigned to them

Reason: Single-operator demo firm, no staff accounts to scope Artefact: reason recorded, no artefact possible

Nothing posts to the ledger until a named person approves it

The run stops at a draft; posting required an approval by the named person. Artefact: draft state screenshot plus approval log

Writes land as drafts by default

Default write mode is draft; the posted entry was posted by hand after review. Artefact: settings export

Running the tool twice does not post twice

The same run executed twice produced one posted entry; the second was deduplicated on the run key. Artefact: two-run log, 1 entry

Every posted entry can be reversed and traced to the run that created it

The posted entry was reversed in the demo company and traced back to the run that created it. Artefact: reversal log with run id

Amounts and accounts are validated against the chart of accounts before posting

An account code outside the chart of accounts was rejected before posting. Artefact: validation error log

No passwords or API keys in prompts, code, or shared documents

Code search for key-shaped strings returned no hits in prompts, code or documents. Artefact: search output, 0 hits

Keys live in a secrets store and are rotated when staff leave

Keys read from the secrets store at runtime; rotation recorded against the departure procedure. Artefact: secrets store listing, rotation record

Each connection has the narrowest access it needs (read-only unless it must write)

The QuickBooks connection holds the narrowest scope that still writes; read-only on everything else. Artefact: token scopes as returned by the provider

Sign-in required; no public link can reach client data

Demo data reachable only after sign-in; a logged-out request to the data path fails. Artefact: logged-out access test

Client data goes only to AI providers whose terms exclude training on it

The provider's training terms were read but not filed, and no terms-read-on date is recorded against the connection.

Each run logs who, when, which client, the inputs and the outputs

Each run logs who, when, which client, inputs and outputs. Artefact: run log, 2 entries

AI outputs are stored next to the source data they used

Each stored output sits beside the source rows it used. Artefact: output and source side by side

Logs are kept for a set period and tool users cannot edit them

Logs are kept, but the retention period is not set and the tool user can still edit them.

Errors are logged and alert a named person

A forced failure raised an alert to the named person within the demo run. Artefact: alert screenshot with timestamp

Any figure can be traced to its source in under five minutes.

A figure was traced to its source in the demo company in under 5 minutes. Artefact: timed walkthrough recording

A one-page handover: purpose, data used, owner, how to run it, how to stop it

One page covering purpose, data used, owner, how to run, how to stop. Artefact: the one-page handover

A second named person has run it end to end from the handover alone

The second named person ran it end to end from the handover, unaided. Artefact: handover run log with their name

Code and settings are in version control with change history

Code and settings in version control; the change history shows the run key change. Artefact: commit history export

Automated tests on demo data pass before every change

Automated tests on demo data pass before each change. Artefact: test output, all pass

One step turns the tool off, and the manual fallback is written down

One step turns it off; the manual fallback is written down and was followed once. Artefact: shutdown demo and the fallback page

Every client has one canonical key, and every system in the path maps to it; the same client created in two systems resolves to one record

Both systems resolve the same demo client to one canonical key; the match test returned one record. Artefact: the mapping table, plus the match test

A write that lands in one system and fails in the other is visible and reversible

A forced half-failure was visible in the reconciliation view and was reversed. Artefact: forced-failure test and the reversal log

The two sides of the path reconcile for a period, with every exception named

The two sides reconciled for one demo period; the one exception is named. Artefact: reconciliation sheet, 1 exception

Every synced figure carries the time it was pulled, and an out-of-date copy is visible to the person using it

Every synced figure carries the time it was pulled, and a stale copy is visible in the view. Artefact: view screenshot with pull times

Where a person re-keys data between two systems, it is a logged approval point with a name, never an unlogged step

No re-keying in this path; where a person does re-key, it is a logged approval with a name. Artefact: approval log, 1 named entry