Home/Proof/The operation record
From request to result and recovery review
Follow an operation. Inspect what stays on record.
OP-000217 is the worked example: Dana cannot print at the front desk, Marcus authorizes from his board, the print spooler on SRV-ACCT-02 is restarted under an eight-minute lease, and the server supplies the result. The recording is still being captured; until it is published, use the live run to inspect each stage and its evidence.
Where the player goes being recorded
There is no recording here yet.
We are not going to stage this one. It is being captured off a live system, on a real operation, and it is not finished. When it is, it will sit in this frame with the chapter marks below it.
Until then the fifteen-minute live version does more anyway — you pick the claim, we run it, and you get to interrupt.
lease 8m · the machine confirmed it
locked · chain 9f3a…c47e
The shape of it
Four actors. The humans are on screen twice.
Read the timeline first and the chapter notes second. The reason to watch a whole operation rather than a highlight is that the shape is the argument: the work is continuous, the human attention is not, and exactly one line in the whole thing comes from the machine that was changed.
Chapter by chapter
What each stretch contains, and the one thing to watch for.
If you only have a minute, the chapters that matter are 00:35, 02:00 and 02:55 — the human's say-so, the machine's answer, and the undo. The rest is context for those three.
00:00 · The ticket arrives
Dana, on the front desk at a medical practice, writes in Teams that she can't print scripts and there are patients waiting. That is the whole intake — no form, no portal, no category dropdown. The message becomes a request with a typed outcome attached to it.
00:20 · The plan
A certified procedure is selected — not written. You see the outcome it claims, the target it will touch, the verification that will decide whether it worked, and the reversal, all before anything is authorized.
00:35 · The authorization
Marcus reads the plan on his delivery board and authorizes it. One click, about fifteen seconds of his attention, and his name and the time are written into the operation — not into a separate approval system that someone will have to line up later.
00:50 · The lease
Admin rights are minted for this operation on this target, for eight minutes. The amber band on the screen is a countdown, and it is the only privilege anywhere in the recording. No shared administrator account is used at any point.
01:20 · The work
The print spooler on SRV-ACCT-02 is restarted by a signed job. The credential that authenticated the connection was resolved from a reference the model cannot read, and it was resolved before any of this existed.
02:00 · The machine confirms
An independent check runs on SRV-ACCT-02 and the server answers: service running, queue clear. That answer — not a status chip, not a summary — is what goes into the record. If it had come back wrong, the same field would say so.
02:20 · The user is told
Dana gets a message in the same thread she started: you're fixed. From her side the entire event was three messages and a working printer, with no stranger driving her mouse and no scheduled call-back.
02:40 · The record
The receipt opens: who asked, who authorized, what privilege was borrowed and when it expired, the job that ran, the machine's own answer, the declared undo, and a fingerprint of the record before it. One reference number covers all of it.
02:55 · The rollback
The reversal that was declared at 00:20 is executed on the same target. It does not open a second ticket and it does not start a new operation — it lands in this one, and it is verified the same way the change was.
Two clocks, and we will not blur them
The recording is three minutes. The operation was not.
Every vendor video is cut, and most of them quietly imply the elapsed time on screen is the elapsed time in the world. Ours is cut too, so here is the honest mapping between the recording's clock and the one written into the record.
To be plain about what this page is: the recording described here does not exist yet. Everything above is the walkthrough of what it will contain, written now so that when the file lands you can check it against this page rather than the other way round. If any chapter turns out not to show what this page says it shows, that is a defect on our side and we would like to hear about it.
The last twenty seconds
The part most demos leave out.
Anyone can record a fix. The interesting stretch is 02:40 to 02:55 — opening the record and then undoing the change while the record is still on screen.
- The receipt is assembled by the platform, not written by the model. The confirmation row can only carry what the target answered.
- A failed operation gets the same record. "No response captured" is a real recorded outcome, not a gap.
- The rollback runs under a fresh lease and produces its own verified result inside the same operation.
- One reference number resolves the whole thing, months later, for someone who was not there.
We are deliberately narrow about session capture. This page describes an operation record — the authorization, the privilege, the job, the machine's answer and the undo. It is not a claim of full multi-surface session replay; see Governed Sessions for what remote access does and does not cover today.
Until the file lands
Three ways to check the same claims today.
The live fifteen minutes
The same operation, unedited, with you choosing which claim we run and interrupting whenever you like. It is strictly better than the recording and it is available now.
Book a demo →The screens themselves
The surfaces the recording walks through, captured from the operator console and captioned with what to look at on each one.
Live screens →The written test
Six yes/no tests you can put to us and to anyone else on your shortlist, with a blank scorecard to take into the room.
The Verified Operation Spec →Better than a video
Watch it happen instead, and pick the ticket yourself.
Fifteen minutes: a real ticket resolved end to end, the record opened, the rollback executed. Bring the hardest question from your last client audit and we will answer it on the call.