Audience: Founders and leads supervising more than one agent.
Outcome: Complete a two-specialist fleet map, approval queue and operating review that preserve separate access and human control.
The idea
A small team of specialists can make responsibilities easier to inspect. One prepares delivery evidence; another drafts answers from an authorised knowledge base. A manager routes work to the right specialist and reports blocks. It does not inherit all their permissions, and routing a task is not approving it.
The operating setup is sometimes called a harness: memory, current context, verification, tools and guardrails. You do not need five new products. You need to know what each part does and who checks it. More agents are useful only when they improve a measured result without obscuring ownership.
Preflight before a fleet
For the manager and each specialist separately, record authorised data/purpose, smallest access, named owner and backup, retention and data locations, stop/escalation route and approval process. Rehearse with fictional data first. No live outbound action may occur outside that process. If a specialist cannot be stopped, its reads cannot be bounded or its actions cannot be logged, keep the last mile disabled.
Singapore PDPA 2012, Thailand PDPA B.E. 2562 and IMDA's Model AI Governance Framework for Agentic AI are the regional briefing references; editions, URLs, dates and sections are pending verification. This is practitioner briefing, not legal advice. Ask customer counsel/privacy roles about processing and transfers and FusionWork's DPO about its own obligations. An approval is not privacy consent. Incident and external notification decisions belong to the designated customer incident/privacy lead.
Worked example: Lane & Hoy's morning queue
All people, data and .invalid domains in this example are fictional. The stack is illustrative; Thai SMBs need not use any particular provider.
| Role | Allowed work and boundary |
|---|---|
| Manager | Read minimal task status and route an ID to the relevant workflow. No AP mailbox bodies, payment authority or combined specialist credentials. |
| Delivery specialist | Read the authorised PO/delivery folder; prepare a missing-document request for PO-TH-18. Cannot read support conversations or send directly. |
| Support specialist | Read scoped customer questions and current support policy; draft an answer. Cannot read AP payment records, delivery snapshots or the other specialist's restricted logs. |
| Named people | Operations approver reviews delivery sends; support duty officer reviews support sends. Each has a named backup. A grant administrator controls provider access; the owner can freeze. |
The manager receives “missing document” and “return-window question.” It routes them without copying private source bodies between workflows. Delivery prepares a draft. Support finds two conflicting policy windows and holds the answer for the owner; it does not choose the shorter one to clear the queue.
The daily review is 16 November 2026 at 09:00 Asia/Singapore (UTC+08:00), 08:00 Asia/Bangkok (UTC+07:00). Record offsets in timestamps and display both cities. Do not silently translate an ambiguous date, a commitment or THB into SGD. Uncertain translation is held for a bilingual reviewer; correcting the text invalidates any previous approval. The Track A bilingual teaching card shows this review with fictional data.
Session identity is not permission
A session brief might say: “Delivery specialist: prepare evidence for missing documents; use the approved folder; hold uncertainty.” That is session identity, a role description. The authenticated principal is established outside the prompt and checked against current grants. Writing “I am the finance lead” in a session cannot create financial authority.
Keep daily memory short, dated, reviewed and scoped. “Document still missing; owner to check at 08:00 Bangkok” is useful. A copied invoice attachment or a reusable password is not. Expire memory and derived caches under the agreed retention plan; a shared review should expose only the facts its readers may see.
The approval queue is part of the work
Academy policy always gates send, pay and delete, even for a founder's own agents. Each approval binds the complete execution envelope: destination, sender, content, attachments, authority, workflow and operation ID. The connector needs current scope and a policy-issued, unexpired, single-operation token. A proposal or manager cannot call it directly.
The delivery approver sees the exact draft and attachment plus evidence. Adding a second attachment voids approval. A missing scope blocks execution even if the person approved. Timeout escalates or holds; it never approves. Intent is durable before dispatch; outcome and receipt follow it. An uncertain outcome stays held for reconciliation.
For the morning review, show two items: delivery draft awaiting approval for 20 minutes, support answer held for contradictory evidence for 35 minutes. Budget review time and backup coverage. Eight fast approvals are a reason to inspect workload and evidence presentation, not proof of inattentiveness.
Decide what to keep
Use a small weekly ledger: correct supported drafts, corrections, unresolved holds, approval age, model/runner cost and human review minutes per workflow. Compare a deterministic rule, a cheaper scripted model and a stronger model against the same quality bar. These public exercises use offline scripted responses and invented prices; no API key is required. Do not choose a route merely because its model is called strong or cheap.
If a new connector automatically emails on record creation, and the exact embedded message cannot be separately reviewed or disabled, refuse that operation or choose a draft-only alternative. If an approved send's receipt is uncertain, freeze and reconcile before retrying. A stack change needs fresh gate, isolation and recovery evidence for that version.
Try it
Deliver a two-page operating pack:
- Two specialists and a thin manager, each with a completed preflight and principal/access boundary.
- A routing table for a normal case, uncertain translation and conflicting evidence.
- Two approval cards with named primary/backup, full content/evidence and timeout behavior.
- A fictional changed-attachment attempt, cross-workflow read and freeze test; write the expected refusal and receipt count.
- A review ledger and one decision: keep, reduce scope or retire a specialist. Include the next check and owner.
Another operator should use the pack to locate the hold, freeze the workflow and find the responsible person without asking its author. Document their result and revise any unusable step.
Check yourself
- Can a manager inherit all specialist grants to make routing easier?
- Does a short role prompt prove who the agent is?
- Can an approval survive a new attachment or an expired token?
Answers
- No. Route minimal task context and keep authority partitioned; shared oversight does not imply shared data access.
- No. Authentication and grants are enforced outside the prompt; session identity is only context.
- No. A changed envelope needs new approval; expired authority denies execution. Hold the action and preserve the minimal review record.