Documentation
Plan

45 of 187 pages

AI Product Studio

When Evidence Is Not Recorded

What the notice “Saved — but its evidence could not be recorded” means, what the studio owner’s banner tells you, and what, if anything, you need to do.

What happened

Every decision is saved first, and its evidence is written to the ledger straight afterwards, in the same request. Very occasionally the save succeeds and the ledger cannot be written at that moment. The Studio does not undo your change to keep the two in step: a gate decision carries audit entries, a merge hold and sometimes a rework request, and rolling those back would trade a missing ledger entry for a missing control.

So instead:

  1. Your change is kept. The notice says Saved because it is.
  2. The gap is put on record, in a separate store, naming each event that could not be recorded.
  3. Our team is alerted.
  4. The studio’s owner is told, in the product.

What to do when you see the notice

Do not repeat the action to “make sure”. A decision recorded twice is two decisions. Nothing needs doing again.

The missing evidence is added the next time that record is saved — the next decision on the same gate, for example. To check, open the artefact’s Passport: its chain and source lines say what is on the records but not yet in the ledger.

The owner’s banner

If you own the studio, a banner appears at the top of every Studio page. Only you see it; members and reviewers do not.

One notice per hour, however many saves were affected in that hour, so an outage is one message rather than a flood.
What it says — how many changes were affected and when, that they were saved, that our team has been alerted, and a list of the artefacts with a link to each one’s passport.
The state beside each artefact — recorded since once the missing entries are in the ledger; not recorded while any is still missing; unknown when it cannot be shown either way. Unknown is never shown as recorded.
Mark as read dismisses it for you. Doing so is audited.
What it does not hold — no names, and nothing about the cause. It is a notification, not evidence, and it is removed after 90 days. The record of the gap itself is kept.

There is no email. If you do not open the Studio you are not told, so for a sustained problem our team contacts the owners affected.

How the passport shows it afterwards

The passport saysMeaning
On the records but not yet in the ledgerSaved, evidence not yet recorded. The next save of that record adds it
Recorded lateThe entry was written well after its event: attested later, not at the time
LostThe event could not be recorded when it happened and the record has since moved on, so the ledger never will hold it. The passport keeps saying so, with the fingerprint the event had when the write failed

A passport that could not read its evidence gaps when it was issued says so, and a verifier counts that against it.

All Guardrails, Evidence & Passport documentation

Build v0.3.2 · deployed 2026-10-19T23:52:31Z