Mission & output
Designs interfaces, accessibility, layouts and experiences.
It can propose changes but cannot directly approve host privilege escalation.
Agent Atlas / New specialist office
Web Designer agent.
Designs interfaces, accessibility, layouts and experiences. A specialized, inspectable job rather than unrestricted system authority.
◈
Scope & boundaries
Actions remain within role-specific tools, information boundaries and operator policy.
This preliminary office concept is associated with the Media example. Credentials, client records and deployment boundaries stay separately configured.
AGENT ATLAS / MEDIA / SIDEAUTHORIZED INPUT REVIEWABLE OUTPUT APPROVAL BOUNDARY
Web Designer: the job, not just the avatar.
An illustrative office design for a specialized agent. A role card is not proof of a deployed integration: tools, credentials, boundaries and verification must be configured and tested.
What it receives
Design brief, component library, accessibility rules and content structure.
What it produces
Prototype, responsive layouts, testing evidence.
What it cannot self-authorize
Publishing and credential use delegated to a separately authorized publisher.
Authority comes from policies, mounts, accounts and the independent manager—not a character description or a prompt. Read the XMAN approval model →
ROLE-SPECIFIC INPUTSSCOPED CREDENTIALSHUMAN REVIEWAUDITABLE HANDOFFS