Operations · walkthrough
One supervised run, end to end
Sample — illustrative, not a real client's record. Every name, number and reference on this page is fictional.
A fictional studio, Harbor Lane Studio, runs a fictional agent, Ledger Assistant, to prepare a weekly client summary. This page follows that one run through the operations console exactly as an owner would see it — what ran, what the stream recorded, where policy stopped it, who decided, and what the client received.
1 · The run
At 18:00 on a fictional Tuesday, Ledger Assistant starts its scheduled weekly summary run for a fictional client, North Pier Books. The workspace records the run's start, its mandate (read the week's order notes, draft a summary, send nothing without approval) and the tools it may use.
2 · The event stream
| Time (fictional) | Event | Recorded as |
|---|---|---|
| 18:00 | Run started under the weekly-summary mandate | run.started |
| 18:02 | Read 42 fictional order notes for the week | source.read |
| 18:05 | Draft summary prepared; no message sent | draft.created |
| 18:06 | Attempted to attach a file outside the mandate's grant window | policy.exception |
| 18:07 | Run paused automatically; owner notified | run.paused |
3 · The policy exception
The attachment attempt fell outside the recorded grant window, so the policy engine stopped the run and opened an exception instead of letting the agent improvise. The exception names the event, the mandate line it crossed, and what the agent was reaching for — nothing about the attempt is hidden from the owner.
4 · The approval decision (casefile)
The fictional owner reviews the exception in a casefile and decides: deny the attachment, approve the summary draft for sending without it. The decision, the decider and the time are recorded on the casefile, and the run resumes only inside the narrowed instruction. A second request in the same run — to reuse last week's figures — is denied outright, and that denial is recorded too.
5 · The signed statement and handoff report
At the end of the period the workspace issues a signed statement covering the run: the events above, the exception, both decisions, and the checks performed on the stream's chain. The client handoff report pairs that statement with a readable brief — what ran, what was stopped, what was decided — and a follow-up checklist (here: renew the grant window before next week's run). The statement attests the records the workspace received; it does not prove the fictional summary was correct, and on a real workspace it would not prove an action happened either.
Statement reference on this page: fictional — SAMPLE-SIG-0001. Signature, hashes and identifiers in a real statement can be verified independently; the ones printed here cannot, because the run never happened.