Specialists work in bounded offices with distinct tasks, approved inputs, reviewable outputs and enforced policy. New roles below are proposed integration patterns.
22 specialist office concepts are shown. New portraits are preliminary illustrations; role-specific permissions remain governed independently of artwork.
TEN NEW GOVERNED SPECIALIST OFFICES
Build teams, not a pile of unrestricted bots.
Every office has an explicit job, inputs, outputs, review gates and an audit trail. Development, marketing, operations and personal care stay in separate domains. These are proposed integration patterns—not a claim of deployed autonomous staff.
An agent asks to allocate resources, use a tool, or perform a protected operation.
02 / decideXMAN policy daemon
The daemon checks request identity, policy, current limits, and actual system state.
03 / approveOperator authorization
Routine permitted work can proceed; sensitive or privileged actions require explicit approval.
04 / enforceBounded executor
Rootless Podman executes supported actions; a separate privileged executor is a future design.
05 / verifyReadback and audit
Reconcile container state, journal the outcome, and notify the requester.
NO DIRECT ROOT AUTHORITY.Human-approved privileged execution is planned, not yet independently qualified.
Within policy → automatically granted. A bounded +32 MiB Podman resource request is enforced and read back; an outcome is recorded.Interactive illustration based on one reported integration test; this page performs no system operations.