A
Constellation architectureDocumentation

Aster: an Arcturion orchestration workspace

Open the folder and you should be able to understand the agent’s job. Open its boot manifest and the agent should be able to find its bearings.

Aster is a fictional coordinator for a constellation of specialists. Its workspace has a place for deciding direction, handing work to the right agent, checking the health of the constellation, maintaining the brand, and keeping the wider system coherent. Those responsibilities give the folders their names.

This example is a structural adaptation of ARCTURUS’s current working layout, inspected at the directory level. It includes the operating pages and domain organization that make that workspace recognizable. The identity and document text are newly written examples. Real projects, personal material, memory records, logs, configuration, editor data and legacy backups stay private.

πŸ—ΊοΈ The complete public workspace

Every folder is expanded below, together with every substantive file and all four relative symbolic links. Only the small .gitkeep placeholders used to retain empty folders are hidden from the display. An arrow means β€œanother route to this source.”

sample-agent/
β”œβ”€β”€ 00 πŸ›‘ Governance/
β”‚   β”œβ”€β”€ Example references/
β”‚   β”‚   β”œβ”€β”€ Arcturion Code.md
β”‚   β”‚   └── Founder_core.md
β”‚   β”œβ”€β”€ Laws/
β”‚   └── Rules/
β”œβ”€β”€ 000 πŸ€– Aster/
β”‚   β”œβ”€β”€ Boot/
β”‚   β”‚   β”œβ”€β”€ context/
β”‚   β”‚   β”œβ”€β”€ 🏠 home.md
β”‚   β”‚   β”œβ”€β”€ Arcturion Code.md β†’ ../../00 πŸ›‘ Governance/Example references/Arcturion Code.md
β”‚   β”‚   β”œβ”€β”€ Duties.md
β”‚   β”‚   β”œβ”€β”€ Founder_core.md β†’ ../../00 πŸ›‘ Governance/Example references/Founder_core.md
β”‚   β”‚   β”œβ”€β”€ Founder.md
β”‚   β”‚   β”œβ”€β”€ Interagent Context.md
β”‚   β”‚   β”œβ”€β”€ Map.md
β”‚   β”‚   β”œβ”€β”€ Objectives.md
β”‚   β”‚   β”œβ”€β”€ operating_intelligence.md
β”‚   β”‚   β”œβ”€β”€ Queue.md
β”‚   β”‚   β”œβ”€β”€ soul.md
β”‚   β”‚   └── voice.md
β”‚   β”œβ”€β”€ dashboard/
β”‚   β”œβ”€β”€ Heartbeats & Automations/
β”‚   β”œβ”€β”€ Identity/
β”‚   β”œβ”€β”€ Inbox/
β”‚   β”‚   └── README.md
β”‚   β”œβ”€β”€ Knowledge/
β”‚   β”‚   β”œβ”€β”€ Foundations/
β”‚   β”‚   β”œβ”€β”€ Founder/
β”‚   β”‚   β”œβ”€β”€ Lessons/
β”‚   β”‚   β”œβ”€β”€ Methods/
β”‚   β”‚   β”œβ”€β”€ Patterns/
β”‚   β”‚   β”œβ”€β”€ Sources/
β”‚   β”‚   β”œβ”€β”€ Standards/
β”‚   β”‚   β”œβ”€β”€ CONTEXT_HOME_MAP.md
β”‚   β”‚   └── LINK_MANIFEST.md
β”‚   β”œβ”€β”€ Memory/
β”‚   β”‚   β”œβ”€β”€ Decisions/
β”‚   β”‚   β”œβ”€β”€ People/
β”‚   β”‚   β”œβ”€β”€ Pointers/
β”‚   β”‚   β”œβ”€β”€ Preferences/
β”‚   β”‚   └── Sessions/
β”‚   β”œβ”€β”€ Photo/
β”‚   β”œβ”€β”€ Skills/
β”‚   β”‚   └── README.md
β”‚   β”œβ”€β”€ Tools/
β”‚   β”‚   └── README.md
β”‚   └── 09_Linked_Surfaces β†’ ../09_Linked_Surfaces
β”œβ”€β”€ 01 πŸ–₯️ Jurisdiction Overview/
β”œβ”€β”€ 02 🎯 Strategy & North Star/
β”‚   β”œβ”€β”€ Backlog/
β”‚   β”œβ”€β”€ Projects/
β”‚   β”‚   β”œβ”€β”€ Active/
β”‚   β”‚   β”œβ”€β”€ Completed/
β”‚   β”‚   └── Superseded/
β”‚   β”œβ”€β”€ Reference/
β”‚   β”œβ”€β”€ Runbooks/
β”‚   └── Systems/
β”œβ”€β”€ 03 πŸ•ΈοΈ Orchestration & Dispatch/
β”‚   β”œβ”€β”€ Backlog/
β”‚   β”œβ”€β”€ Projects/
β”‚   β”‚   β”œβ”€β”€ Active/
β”‚   β”‚   β”œβ”€β”€ Completed/
β”‚   β”‚   └── Superseded/
β”‚   β”œβ”€β”€ Reference/
β”‚   β”œβ”€β”€ Runbooks/
β”‚   β”œβ”€β”€ Systems/
β”‚   └── Tools/
β”œβ”€β”€ 04 ⭐ Constellation Health/
β”‚   β”œβ”€β”€ Backlog/
β”‚   β”œβ”€β”€ Projects/
β”‚   β”‚   β”œβ”€β”€ Active/
β”‚   β”‚   β”œβ”€β”€ Completed/
β”‚   β”‚   └── Superseded/
β”‚   β”œβ”€β”€ Reference/
β”‚   β”œβ”€β”€ Runbooks/
β”‚   └── Systems/
β”œβ”€β”€ 05 πŸ›°οΈ Arcturion Group & Brand/
β”‚   β”œβ”€β”€ Backlog/
β”‚   β”œβ”€β”€ Projects/
β”‚   β”‚   β”œβ”€β”€ Active/
β”‚   β”‚   β”œβ”€β”€ Completed/
β”‚   β”‚   └── Superseded/
β”‚   β”œβ”€β”€ Reference/
β”‚   β”œβ”€β”€ Runbooks/
β”‚   └── Systems/
β”œβ”€β”€ 06 🧬 Prong Coherence/
β”‚   β”œβ”€β”€ Backlog/
β”‚   β”œβ”€β”€ Projects/
β”‚   β”‚   β”œβ”€β”€ Active/
β”‚   β”‚   β”œβ”€β”€ Completed/
β”‚   β”‚   └── Superseded/
β”‚   β”œβ”€β”€ Reference/
β”‚   β”œβ”€β”€ Runbooks/
β”‚   └── Systems/
β”œβ”€β”€ 07 πŸš€ Growth & Revenue/
β”‚   β”œβ”€β”€ Backlog/
β”‚   β”œβ”€β”€ Projects/
β”‚   β”‚   β”œβ”€β”€ Active/
β”‚   β”‚   β”œβ”€β”€ Completed/
β”‚   β”‚   └── Superseded/
β”‚   β”œβ”€β”€ Reference/
β”‚   β”œβ”€β”€ Runbooks/
β”‚   └── Systems/
β”œβ”€β”€ 09_Linked_Surfaces/
β”œβ”€β”€ 77 πŸ›  Back Office/
β”‚   β”œβ”€β”€ _templates/
β”‚   β”œβ”€β”€ prompts/
β”‚   └── scripts/
β”œβ”€β”€ 88 πŸ“¦ Deliverables/
β”‚   β”œβ”€β”€ Automation-Outputs/
β”‚   β”œβ”€β”€ Logs/
β”‚   β”œβ”€β”€ Outbox/
β”‚   β”œβ”€β”€ Scripts/
β”‚   └── State/
β”œβ”€β”€ 99 πŸ—„οΈ Archive/
β”‚   β”œβ”€β”€ Safe_to_delete/
β”‚   └── Sunsetting/
β”œβ”€β”€ tools/
β”‚   β”œβ”€β”€ render_entrypoints.py
β”‚   └── test_render_entrypoints.py
β”œβ”€β”€ _canonical_home β†’ 000 πŸ€– Aster
β”œβ”€β”€ AGENTS.md
β”œβ”€β”€ ANTIGRAVITY.md
β”œβ”€β”€ CLAUDE.md
β”œβ”€β”€ entrypoints.json
β”œβ”€β”€ GEMINI.md
β”œβ”€β”€ HERMES.md
└── README.md

🧭 The floors describe the job

The numbered floors give a person a dependable route through the workspace. They also give the agent explicit places to find context, do work and leave a result.

Floor What it is for
00 πŸ›‘ Governance/ Local laws, rules and shared conduct references
000 πŸ€– Aster/ Identity, orientation, learning, continuity and working guidance
01 πŸ–₯️ Jurisdiction Overview/ A readable front door: what this agent owns and where to look
02 🎯 Strategy & North Star/ Direction, priorities and the reasoning behind the work
03 πŸ•ΈοΈ Orchestration & Dispatch/ Coordination, specialist handoffs and dispatch tooling
04 ⭐ Constellation Health/ The condition of the agent network and work that improves it
05 πŸ›°οΈ Arcturion Group & Brand/ The organization’s presentation and brand work
06 🧬 Prong Coherence/ How ATLAS, agent workspaces, shared HQ and runtime fit together
07 πŸš€ Growth & Revenue/ Growth work, opportunities and business experiments
09_Linked_Surfaces/ Navigation to shared resources owned elsewhere
77 πŸ›  Back Office/ Templates, prompts and internal scripts
88 πŸ“¦ Deliverables/ Outputs and supporting records prepared for a handoff
99 πŸ—„οΈ Archive/ Work leaving active use

These are the responsibilities of an orchestration role. An engineer or researcher would have different domain names. The pattern worth carrying forward is a clear remit for each floor, a recognizable inner workspace, and visible places for active work and its results.

πŸ€– The inner workspace: who, where, what next

Boot gives the agent its bearings

The entry point is Boot/🏠 home.md. The operating pages around it answer different questions:

File or shelf The question it answers
soul.md Who is this agent, and what are its role and boundaries?
voice.md How should it communicate?
Founder_core.md and Founder.md Whom does it serve, and what is the working relationship?
Arcturion Code.md Where is the shared conduct reference?
Map.md Where does the agent’s work belong?
Duties.md What responsibilities continue beyond a single task?
Objectives.md What outcomes should guide its work?
Queue.md What is currently being worked on, and what comes next?
Interagent Context.md What information makes a specialist handoff useful?
operating_intelligence.md What working guidance is relevant to a reasoning-heavy task?
context/ Where can selected task context be kept?

A queue and a session record have different jobs: the queue points forward to active work; a session record preserves enough history to continue. Duties describe an ongoing remit; objectives describe the outcomes being pursued. Giving those ideas separate homes makes the workspace easier to inspect and maintain.

The operating pages are available for navigation and task selection. Their presence in Boot does not mean they are all loaded at every start. The documented adaptive design protects the identity kernel and selects the other material when the task calls for it.

The rest of the core supports the work

Shelf Purpose
Identity/ A place for identity-related reference or development; canonical soul and voice remain in Boot
Inbox/ Incoming requests and information awaiting triage
Skills/ Instructions for performing a kind of work
Tools/ Guidance for using particular capabilities
Heartbeats & Automations/ Descriptions and operating instructions for recurring routines
dashboard/ A place for a readable working overview
Photo/ Visual identity material

These are recognizable locations from the modern source layout. Empty shelves reserve an address; they do not install a dashboard, connect a service or start a schedule.

πŸ“š Knowledge and Memory serve different jobs

Knowledge holds reusable understanding. Memory preserves the history and relationships that give ongoing work its context. Both persist outside a conversation; neither is the model’s temporary context window.

πŸ“š Knowledge πŸ—‚οΈ Memory
Apply reusable understanding to the next task Continue with an accurate record of what happened
Methods, standards, patterns, lessons and references Decisions, sessions, preferences, people and source pointers
β€œHow to review a repository before publication” β€œThis release was approved with these limits and this evidence”
Improve the next piece of work Preserve the history behind the current one

The Knowledge shelves

Shelf What belongs here
Foundations/ The concepts and background the agent’s craft rests on
Founder/ Curated working knowledge about serving the person the agent supports, with appropriate privacy and authority
Lessons/ Specific learning distilled from experience, including its limits
Methods/ Repeatable ways to perform a task
Patterns/ Useful arrangements or approaches that recur across tasks
Sources/ References and provenance supporting the agent’s understanding
Standards/ The criteria used to judge the quality of work

A method can be revised when better evidence arrives. A lesson should preserve the circumstances that limit where it applies. Placement in Knowledge does not make a statement universally true or grant it authority over current instructions.

The Memory shelves

Shelf What belongs here
Decisions/ What was decided, by whom, why, with what scope and supporting evidence
People/ Relevant relationship context, limited to information appropriate to retain
Pointers/ Where a source or artifact lives, so the agent can return to the original
Preferences/ Recorded choices and corrections, including when they apply
Sessions/ Continuity records: the goal, progress, open work, artifacts and verification

The same event can contribute to both shelves. In an invented release example, Memory records the approved version and the checks that passed. Knowledge holds a reusable release-review method learned from that work. The method can link back to its evidence without copying the entire session into a second home.

Knowledge/Founder and Memory/Preferences therefore have different emphases: the first organizes useful understanding; the second preserves specific recorded choices and corrections. Neither replaces a current instruction or permission check.

In the documented private design, the Brain retrieves relevant context and points back to its sources. An agent asks a focused question and reads the material needed for the task; it does not bulk-load Knowledge or Memory at boot. This sample contains empty shelves and does not include that retrieval service.

πŸ› οΈ Work lives directly on its domain floor

Each domain has Backlog/, Projects/, Reference/, Runbooks/ and Systems/ directly beneath it. Projects are divided into Active/, Completed/ and Superseded/. The orchestration floor also has a Tools/ shelf for its domain-specific tooling.

Shelf What belongs there
Backlog/ Work to consider or prioritize
Projects/Active/ Projects being worked on
Projects/Completed/ Completed project records
Projects/Superseded/ Projects or approaches replaced by later work
Reference/ Material supporting that domain
Runbooks/ Instructions for repeatable operations
Systems/ Descriptions of the systems the domain relies on or maintains

This matches the inspected modern domain organization. A person can move from strategy to orchestration and recognize the same working shelves. An agent can move from a goal to an active project or a runbook through named locations.

The domain reference shelf supports a subject; the inner Knowledge shelves organize the agent’s reusable learning. Give a document a clear owning home and link to it where useful, so revisions do not leave competing copies behind.

πŸ”„ Follow a piece of work

Imagine a request to prepare a public field guide for a fictional project.

  1. Receive it. The request enters the working conversation or Inbox. The agent identifies the goal, scope and permissions.
  2. Get oriented. The manifest establishes the role. The relevant map, duties, objectives and current queue clarify ownership and the next action.
  3. Retrieve context. The agent asks the Brain for relevant material and follows source pointers. It selects the applicable domain guidance, skills and tools.
  4. Do the work. A coordination task belongs on the orchestration floor; its project material has a home in Projects/Active/. A handoff carries the task, evidence, allowed scope and next action.
  5. Prepare the result. Work for review goes to Deliverables, with a clear account of what was checked and what remains uncertain.
  6. Preserve continuity. Memory records the decisions and continuation state. Reusable learning can be distilled into Knowledge. Finished or replaced project records move to the appropriate lifecycle shelf.

That is a working pattern for people and agents to follow. The folders themselves do not automate those moves.

βš™οΈ Back office, deliverables and archive

Back Office keeps _templates/, prompts/ and scripts/ together. These are the reusable materials behind the work.

Deliverables provides places for Automation-Outputs/, Logs/, Outbox/, Scripts/ and State/. These are neutral output categories retained for this public adaptation; actual private deliverable and project names are omitted. An Outbox deposit stages a handoff. It does not send anything, establish approval or prove publication.

Archive retains Sunsetting/ and Safe_to_delete/ as example lifecycle categories. The latter’s name alone grants no permission to delete. These example categories do not reproduce the real workspace’s private archive contents.

πŸ”— One reference, several routes

The four symbolic links keep navigation connected without making duplicate copies:

Link Destination inside this sample
_canonical_home 000 πŸ€– Aster/
000 πŸ€– Aster/09_Linked_Surfaces The root 09_Linked_Surfaces/
000 πŸ€– Aster/Boot/Founder_core.md 00 πŸ›‘ Governance/Example references/Founder_core.md
000 πŸ€– Aster/Boot/Arcturion Code.md 00 πŸ›‘ Governance/Example references/Arcturion Code.md

The shared-reference text is fictional and all destinations stay inside this example. No real workspace’s absolute link targets were copied.

Knowledge also includes CONTEXT_HOME_MAP.md and LINK_MANIFEST.md, two navigation-file types observed in the source workspace. Their contents here are newly written, local explanatory notes.

πŸš€ A bounded boot, then the context the task needs

The five root instruction filesβ€”AGENTS.md, ANTIGRAVITY.md, CLAUDE.md, GEMINI.md and HERMES.mdβ€”point to the same manifest. Their first lines identify the harness; the remaining bytes match. Which file a particular host reads depends on its configuration.

In the inspected private adaptive design, the protected kernel preserves identity, a shared operating card and a small routing block exactly. Source-defined ceilings allow 10,000 estimated tokens for identity and 14,000 for the complete kernel: identity plus a 3,500-token card and a 500-token routing block.

That fits within the 15k boot design target. Task context is selected separately. These figures describe source-defined limits, not a measured live session or a provider tokenizer count; provider system prompts and tool definitions are outside that ceiling.

The public example depicts the design. It supplies no private Brain, controller, automatic context injection, compaction or cross-host enforcement.

πŸ§ͺ Check and adapt it

The entry files are generated from entrypoints.json by tools/render_entrypoints.py. From sample-agent/, check for drift:

python3 tools/render_entrypoints.py --root . --check

After intentionally changing the local manifest, regenerate and review the entry files:

python3 tools/render_entrypoints.py --root . --write

From the repository root, check the structure, local links, relative symbolic links and generated pointers:

python3 scripts/check_architecture.py

When adapting this workspace, name the agent’s actual remit and domain floors, then write its own identity, duties and working guidance. Preserve a clear boundary between prepared work and an authorized external action. Review existing identity, Knowledge and Memory separately before sharing them.

This is a complete public example of one modern orchestration layout. It is not an export of a private agent or a claim that every specialist uses identical folders.

Example document directory

Browse the sample’s reference pages and entry pointers.