SiSu RevOps

M8  /  L8.4  /  about 12 minutes

The remote surface, the rollout brief, and knowing when to leave

Why this matters

You have a workflow, the register you wrote in L8.3 and a failure plan. Now somebody senior wants three more people doing it, and they will ask questions you have not thought about: who approved this, what can it see, what happens when it is wrong, and what does our security team say.

Answer those badly and the answer is no. Answer them in a document, before you are asked, and the answer is usually yes with conditions, which is the outcome you want.

What you will be able to do

  • Describe the remote surface accurately, including what it does not change.
  • Write a one to two page rollout brief a manager can approve or reject on its own terms.
  • State the audit position in both halves, honestly.
  • Name the conditions under which a workflow should leave this tool.

The remote surface, and the caution that comes with it

Dispatch lets you trigger work from your phone: you send a task from the Claude mobile app, the desktop agent picks it up, executes it with your local files and connectors, and messages you when the result is ready. Reported scope from a phone trigger: spinning up subagents, reading and writing local folders, connecting to MCP servers such as Gmail, Google Drive and Slack, and executing files.

Parallel tasks run genuinely in parallel, each with its own context, file access and connectors, and you can move between them. Any hard cap on concurrency is unverified: plan for "several", not a number.

Computer use lets Claude drive applications on your computer for tasks assigned through Dispatch. It is not available in the Linux beta, and the Linux beta's scope is itself unverified.

The revenue application, concretely: from a taxi you send "run the renewal risk pass and the account brief for the account I am seeing at 2", and you read the output when it lands. A real hour saved on a real day.

The caution, equally concretely: a task triggered remotely has exactly the folder access you granted in Module 2, and you are not there to steer it. The directory boundary being the real boundary applies harder when you are not watching. Fenced properly, nothing changes; fenced badly, this is the moment it matters. Re-read the SharedRoot disclosure and the mitigation posture in Module 2 before making remote triggering part of your routine.

The rollout brief

ops/rollout-brief.md, one to two pages, which you write now from the seed at templates/M8/rollout-brief.md in your practice pack, for a manager who will ask hard questions. Six sections, and the fifth is the one that gets it approved.

1. Which workflows are approved, at which blast-radius class, with which approver. A table: workflow, class (read-only, draft-only, writes-to-system), named approver, reversal plan if applicable. Anything not on the table is not approved, which is the point of a table.

2. Workspace layout and fenced folders. From Module 2: which folder is granted, what is deliberately not in it, who checks. Whatever is in the folder is in scope, so the folder is the control.

3. The never list. From Module 3, plus what Modules 5 to 8 added: the survivor decision on a duplicate merge, the forecast call, the QBR narrative and the ask, anything that touches money, anything customer-facing without a named reviewer.

4. Who reviews what before anything reaches a customer. From Module 7's review-gate.md, which you wrote in L7.4, referenced, not repeated.

5. The audit position, in both halves. Say both, in this order:

What exists. On Enterprise there is an admin dashboard and an Analytics API giving per-day aggregated Cowork usage, per-user activity, skill and connector invocations, and DAU/WAU/MAU, plus role-based access controls, spend limits and use controls, and OpenTelemetry events covering tool and connector calls, files read or modified, skills used, and whether each AI-initiated action was approved manually or automatically, compatible with SIEM pipelines. Real telemetry, genuinely useful.

What does not exist. The Compliance API and Audit Logs do not cover Cowork. Telemetry is not the compliance audit log a regulated team may be required to hold. For any workflow that touches a system of record, our audit trail is the one we build: the run log, the before-state export, and the named approver per run.

Say both halves. A manager who learns the second half from somebody else stops believing the first. A manager who reads both in your document concludes you should own this.

6. The usage position. One shared pool across chat, Claude Code and Cowork, with a 5-hour rolling window plus a weekly cap, and heavy multi-step work consuming materially more allowance than chat. Two consequences a manager needs: a team that moves reporting into this tool should expect chat allowance to be affected, and spend limits exist on the enterprise plan. Never teach a number for the allowance: the published figures are unverified and change, so teach the shape and link out.

Knowing when to leave

A course that never tells you to stop using the thing it is selling is selling rather than teaching. Keep this list. Any one of these means the workflow has outgrown this tool.

Exit criterion What it looks like in practice
It needs an event trigger with low latency "Alert the AE within the hour when a deal moves to Stage 3." No event triggers exist, and the cadence-plus-check latency is not acceptable. Move the trigger to the CRM or a workflow engine. Keep the analysis.
It must run at an exact time without fail The commission file that finance needs on the 3rd. Scheduling is convenience automation. Move it.
It must be auditable in a way you cannot evidence A regulated process needing a compliance audit log. The gap is real today. Move it, or keep it draft-only forever with a human applying every change through the system's own change process.
It is now stable, deterministic and high volume The same transformation on 40,000 rows every night, unchanged for six months. A purpose-built pipeline is cheaper and faster, and the judgment that justified an agent has been designed out.
The verification cost has grown past the work You spend 40 minutes checking output that takes 30 minutes to produce by hand. The Module 4 rule reasserting itself. The honest answer is to stop.

Two things about that table. Leaving is a success state: a workflow that graduated to a pipeline was specified by you, and the brief, rules file and run log are the handover document. And most of what you build will not leave. The list exists so the two or three that should, do, rather than being defended for another year because somebody built them.

Try this now Draft section 5 of your own rollout brief. Here is the version that decides the meeting, written for a real team:

## 5. Audit position

We can evidence, per run: the brief that ran, the inputs, the reconciliation
result, the sample checked, the exceptions raised, and the named person who
reviewed the output. That evidence lives in 50-runs/RUN-LOG.md and in the dated
output files, both inside our own workspace, both under our normal file
retention.

On Enterprise, the platform gives per-day aggregated usage, per-user activity,
skill and connector invocations, RBAC, spend limits, and OpenTelemetry events
covering tool and connector calls, files read or modified and whether each
AI-initiated action was approved manually or automatically, SIEM compatible.

The Compliance API and Audit Logs do not cover Cowork.
Platform telemetry is not the same thing as a compliance audit log.

What this means for the proposal in front of you: every workflow in section 1 is
read-only or draft-only, so no system of record is changed by an agent and the
audit gap does not bite. The moment we propose promoting one to
writes-to-system, this section has to be re-approved by <security owner>, and
the promotion conditions in 40-reference/field-policy.md apply in full.

The last paragraph makes the document approvable: no blanket yes, just what is in scope now and the event that would require asking again.

What you keep

  • ops/rollout-brief.md, one to two pages, six sections, ready to send.
  • The exit criteria list, kept alongside the register, re-read once a quarter.

Check yourself

  1. A rollout brief omits the audit position entirely. Name what a manager cannot decide without it, and what they will probably decide instead.
  2. Three workflows: (a) a nightly transformation of 40,000 rows, unchanged for six months, verified clean every time; (b) a weekly renewal risk list; (c) a Monday pipeline pack. Which should graduate off this tool, and what is the deciding criterion?
  3. Your VP says "so it can just watch the CRM and tell us when something changes". Answer in two sentences, then say what you can offer instead and what it costs in latency.
  4. A colleague wants to trigger the hygiene pass from their phone while travelling. Name the one thing you check first, and why the answer is different from when they run it at their desk.

Where this goes next

LAB-08, the exercise sheet in labs/LAB-08 of your practice pack (start with its README), runs the retention pack and the register on the shipped dataset, then on your own book behind the redaction gate, including the execution-mode pre-flight you start early and read at the next session.

Then the capstone, on your track. Whatever you build, it requires a register entry and a failure plan: the part that proves you understood what you were operating.

Two things to do in the week after you finish, worth more than another module:

  1. Run one workflow twice, for real, with the run log filled in both times. Everything here is theory until the second run happens on a week you did not feel like it.
  2. Re-read the exit criteria against what you built. If one of your workflows already meets one, say so out loud to whoever you built it for. That sentence is the most credible thing you can say about this work.