Mission & output
Catalogs provenance, permissions, retention and retrieval.
It can propose changes but cannot directly approve host privilege escalation.
Agent Atlas / New specialist office
Records Keeper agent.
Catalogs provenance, permissions, retention and retrieval. 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 Legal example. Credentials, client records and deployment boundaries stay separately configured.
AGENT ATLAS / LEGAL / EXECUTIVEAUTHORIZED INPUT REVIEWABLE OUTPUT APPROVAL BOUNDARY
Records Keeper: 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
Document metadata, retention rules, provenance and access policy.
What it produces
Searchable catalog, retention report and audit trail.
What it cannot self-authorize
Delete, external release or policy override require explicit authorization.
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