ATLAS: the living workspace
A conversation can start a piece of work. ATLAS gives that work a place to live.
ATLAS is the document workspace of the Arcturion system: an Obsidian vault organized into numbered headquarters, with notes, references, projects and supporting material arranged by subject. A person can enter through a home page and follow the folders. An agent can retrieve relevant context through the Brain, follow a source pointer and arrive at the same material.
The goal is shared visibility. The structure should help a person understand where something belongs and help an agent find the context it needs without loading the entire vault.
πΊοΈ A fuller map of the vault
The current workspace spans numbered areas 01 through 18. The map below preserves that breadth and the shared floor names. Bracketed labels generalize private areas; they are not literal folder names. Decorative symbols in floor names are simplified for readability. The two 05 branches reflect the inspected layout.
This is a public structural map, not an export of the vault. Private documents, projects, people, accounts and configuration are omitted.
ATLAS/
βββ π Home.md
βββ MAP.md
βββ 01. Notebook & Comms HQ/
βββ 02. [Personal and family]/
βββ 03. Productivity HQ/
βββ 04. [Personal wellbeing]/
βββ 05. [Household]/
βββ 05. [Other private area]/
βββ 06. [Personal life and interests]/
βββ 07. Business HQ/
βββ 08. [Private administration]/
βββ 09. [Private administration]/
βββ 10. [Private administration]/
βββ 11. [Private administration]/
βββ 12. [Private administration and research]/
βββ 13. Content HQ/
βββ 14. [Personal reflection]/
βββ 15. Universe & Agentic HQ/
βββ 16. Systems HQ/
βββ 17. [Other private area]/
βββ 18. [Reflection and interests]/
Supporting infrastructure and archive areas are outside this map. The numbered areas are addresses for different kinds of work; they do not imply that every area uses identical subfolders or that a folder name grants access to its contents.
The shared working floors
| Floor | What the area brings into view |
|---|---|
| 01 Β· Notebook & Comms | A named home for notebook and communication material |
| 03 Β· Productivity | Calendars, projects and workflows |
| 07 Β· Business | Business work and its supporting assets and media |
| 13 Β· Content | The content library, brand assets, pipeline and research |
| 15 Β· Universe & Agentic | Agent guides, knowledge corpora, skills, connectors and automation guidance |
| 16 Β· Systems | System documentation, including governance and doctrine |
The personal areas show the other half of the design: one navigable workspace can support a person's wider life as well as their projects. Their private records do not need to be published to make the organization understandable.
πͺ From the front door to the working shelf
ATLAS has a root π Home.md and MAP.md. Each of the five shared and business floors inspected for this tour also has a home note. These give readers named navigation surfaces alongside the folders themselves. The Systems floor additionally has an _index.md; indexes are not assumed to exist everywhere.
The following are selected, observed shelves, with decorative symbols omitted. They are intentionally partial: no individual project or private document is listed.
03. Productivity HQ/
βββ π Home.md
βββ Calendars/
βββ Projects/
βββ Workflows/
13. Content HQ/
βββ π Home.md
βββ Brand Asset Library/
βββ Content Library/
βββ Content Pipeline/
βββ Hashtags & Research/
15. Universe & Agentic HQ/
βββ π Home.md
βββ Knowledge Corpora/
βββ Constellation/
βββ Guides/
βββ Agents/
βββ Skills & Connectors/
βββ Automations & Heartbeats/
These three examples show different organizing needs. Productivity separates planning and repeatable work. Content distinguishes a library of material from the pipeline that develops it. The agentic floor puts guidance about the constellation within reach of its knowledge, capabilities and recurring routines.
Business also has observed Assets/ and media/ shelves. Systems has Governance & Doctrine/. Those are glimpses of the current organization, not a promise that a particular project follows a universal template.
π€ Readable by people, retrievable by agents
The folders provide a stable visual route. Home notes and indexes offer another way in. Links connect related material across those locations without requiring every reference to become a second copy.
For an agent, the Brain provides a focused entry point. It indexes selected sources across the wider system and returns bounded context with source pointers. The agent can then inspect the original document and the folder around it. The query supplies a lead; the source supplies the material to check.
Scroll diagram to explore.
Both routes should make the work inspectable. A person should not have to reconstruct the last chat to understand a document. An agent should not have to read every folder to find one relevant source. Actual access, indexing coverage and retrieval quality depend on the installed system and the task's permissions.
π§© ATLAS within the four working areas
ATLAS is one part of the architecture. The other working areas serve different responsibilities:
| Area | Its contribution to the work |
|---|---|
| ATLAS | Documents, references and project material organized by subject |
| Agent workspaces | Each specialist's boot, identity, domain work, Knowledge, Memory and deliverables |
| Shared HQ | Shared governance, skills and coordination across agents |
| Runtime | Installed tools and services that carry out allowed operations |
The Brain connects selected sources across those four areas. It is the retrieval layer, not a fifth workspace and not a substitute for the source files. The system map shows the relationships; the Brain tour explains the index and retrieval path.
The Aster sample shows an agent's workspace in full. ATLAS has a broader subject-oriented role: it can hold material useful to several specialists and to the person they support. A reference can have one owning home and be linked from other places that need it. The architecture does not require copying every project into every agent's folder.
π Follow an invented project
Imagine a fictional project called Lumen Field Guide. Its name and the following route are invented to illustrate the architecture; they are not a disclosure of an existing project.
- Find the context. A person browses the appropriate ATLAS floor, or an agent queries the Brain and follows a source pointer to relevant material.
- Establish the work. The responsible agent clarifies the goal and creates working material in its domain area. Aster's sample shows how an orchestration role separates active projects, references and runbooks.
- Prepare the guide. The agent develops the draft and places the result with its deliverables for review. Supporting brand material could be referenced from the Content floor rather than copied repeatedly.
- Review and file. The person reviews the result. Approved document material can be added to an appropriate ATLAS location within the task's permissions. Preparing or filing a draft does not authorize publication.
- Leave a useful continuation. The agent records decisions and open work in its own Memory. Reusable understanding can be distilled into Knowledge. ATLAS holds the project material in its subject context; the Brain can retrieve it where it is indexed.
This is a human and agent working pattern, not an automated transaction. Filing, indexing, sending and publishing remain separate actions with their own evidence and permissions.
π Documents, Knowledge and Memory
ATLAS, Knowledge and Memory are related concepts with different jobs.
ATLAS organizes material by subject. It is the wider document workspace. An agent's Knowledge holds reusable understanding: methods, patterns, standards, lessons and references. Its Memory preserves continuity: decisions, sessions, preferences, people and pointers.
A project guide may live in ATLAS. A reusable way to write a better guide may belong in an agent's Knowledge. The record of which version was reviewed and what remains open belongs in Memory. Useful links can connect all three without erasing their separate purposes.
The sample workspace guide expands that distinction with its complete Knowledge and Memory shelves.
π‘οΈ Preserve the workspace, check the source
The local ATLAS instructions make its existing structure additive only: preserve existing folders and notes rather than renaming, moving or deleting them. This describes the owning rule; it does not claim every possible tool enforces it.
An index can lag behind a document. A home page can contain an outdated reference. A retrieved passage can miss something important. For consequential work, return to the original material and check its current context before relying on it.
This public tour shares the organizing approach. It includes no private vault, account connections, live records, synchronization service or access to the Founder's workspace.
π± Explore and contribute
Start with the complete Aster workspace to see how a specialist's folders support the work. Read the bounded boot design to see how it starts with identity and selects further context.
For a separate public toolset for document-based memory, Arcturion Memory provides audit, index, deduplication and recall tools. It is a smaller standalone project with its own setup and synthetic examples. Documentation improvements and carefully scoped examples are welcome in the relevant repositories.