The system around an agent
A task moves through more than a prompt. It needs a place to find context, a workspace for doing the work, tools to act, and a person who can review the result. The private architecture described here separates those responsibilities into four working areas, connected by the Brain.
Scroll diagram to explore.
The lines show relationships, not a guarantee that every connection is automatic or active. The Brain is the connective layer across the four areas; it is not another working area in this map.
| Area | Role in the documented architecture |
|---|---|
| ATLAS | Organizes documents and other materials in subject areas; access and filing depend on their context. See ATLAS. |
| Agent constellation | Specialized workspaces hold each agent's identity, domain work, local governance and deliverables. |
| Shared HQ | Holds shared governance, skills, tools, project coordination and cross-agent context. |
| Runtime | Houses installed execution, services, dependencies and caches. An existing source tree remains with its declared owner; this diagram does not imply moving it. |
| Brain | Indexes selected sources and retrieves bounded context with references. See the Brain. |
The source instructions assign knowledge governance to COVENANT and Brain engineering to ALTAIR, with shared review for changes crossing those responsibilities. A role in a document is not proof of how a particular host enforced it or whether a service is healthy.
Follow one piece of work
Imagine an agent asked to prepare a project guide. It can consult the shared rules and skills, retrieve relevant context through the Brain, and work in its own domain area. The working guide can be placed with that agent's deliverables for review; important document materials may have an appropriate home in ATLAS. A tool or service in the runtime may help, subject to the task's permissions. The person reviews what changed and the evidence for it.
That is a conceptual route, not an automatic transaction or a promise that all documents synchronize. Actual destinations, authority and checks depend on the work. The fictional sample agent illustrates workspace navigation without connecting to the private system. Separately, the linked public tool repositories offer their own examples and contribution paths; they are not replicas of the whole private system.