Operators with Narrow Hands

Curators Read; Operators Write — Narrowly

Most of the team reads. But some jobs are writes, and pretending otherwise leaves you doing the same mechanical task by hand every week. The reference system’s answer is a second kind of team member, the operator: chartered like a curator, with an even tighter surface, whose SOP is a single kind of write.

Three operators, abstracted, show the pattern:

The form filler. A recurring web form — ten required fields, always the same shape — that needs to be filled from trip details. The operator opens a headed browser session (you can see it), fills every field from values the chief of staff passes verbatim, and stops. It never clicks Submit. You look at the filled form and click. The only judgment in the task (deriving the pickup time from the flight) stays with the chief of staff; the operator does typing, and it never navigates beyond the target form.

The narrator. Turns text into audio. It has a classification gate written into its charter: cloud text-to-speech only when the dispatch carries classification: public; on-device synthesis for everything else. It does not extract the text, does not classify it (that is the chief of staff’s judgment), and does not deliver the result — the channel coordinator owns delivery. One job, three refusals.

The draft creator. An email curator promoted, by decision record, to one write verb: create a draft in the mailbox, threaded correctly, with body text supplied verbatim by the chief of staff. Never send, never delete. The send prohibition is the whole point — the draft appears in your drafts folder, you read it, you send it.

The Pattern

• Verbs are enumerated, not implied. “Create event” is allowed; “update event” is not — until a separate decision record adds “patch summary and description, on events it created itself.” Each promotion is one verb, one record, one reverse-if.
• The human keeps the irreversible click. Submit, send, pay, sign. The operator’s output is always something you inspect and complete.
• Values are passed verbatim. The operator does not derive, infer, or improve. If a value is missing, it stops and says which one.
• Classification gates anything that leaves the machine. Public → cloud service allowed. Anything else → on-device or not at all. The gate is in the operator’s charter, not just the chief of staff’s judgment, so it holds even when the dispatch is careless.
• One operator, one job. The narrator does not deliver; the form filler does not book; the draft creator does not send.

Why Not Just Let the Chief of Staff Do It

Because the chief of staff holds no tool access, and that rule does not get an exception for convenience. When the reference system needed audio, the chief of staff called the speech API directly for a one-off probe — acceptable as an experiment, and the decision record for the operator hire says exactly that: “per the team architecture, tool access belongs with a chartered member, not with the chief of staff.” The experiment became a hire the same week.

Standing Duties Are Still Delegated

Some writes recur on a trigger rather than a request. Before any trip: manage the car-rental booking, research the destination’s driving rules, check the pickup timing against the flight. These are standing duties of the chief of staff — recorded as such — and each write inside them goes through the relevant operator. The chief of staff owns the checklist; the operators own the hands.

When an Operator Gets It Wrong

Because the output is always inspectable before the irreversible step, an operator’s mistake costs a minute, not a booking. But it still goes in the feedback log — and the entry usually produces a charter clause, not a scolding. “Never raise a data-integrity flag from one part of a multi-part email; diff the parts first” is a rule that exists because an operator once manufactured a booking defect from a plaintext fallback.

#operators · #writes · #authority · #delegation