Problem
Agent ecosystems become unsafe to explain when documentation accidentally doubles as an operational control surface.
Private core · public architecture
Yggdrasil
Private nine-realm local ecosystem with a deliberately non-operational public architecture model.
Overview
Design
Responsibilities are separated into bounded realms for agents, memory, interfaces, creative generation, tools, evidence and automation.
Outcome
A public mental model for a private system, useful for understanding boundaries without creating a remote control plane.
Verification
The website verifies the disclosure boundary rather than claiming public access to the private implementation.
Multi-agentLocal-firstPersistent memoryAutomationAI systemsOrchestrationMemory
Selected case studies
Yggdrasil
Private nine-realm local ecosystem with a deliberately non-operational public architecture model.
- 01Problem
Agent ecosystems become unsafe to explain when documentation accidentally doubles as an operational control surface.
- 02Design approach
Responsibilities are separated into bounded realms for agents, memory, interfaces, creative generation, tools, evidence and automation.
- 03Limits of this case
The website exposes architecture only: no remote execution, memory access, credentials or private clone path.
Verified Project State · 16.1
Evidence and observation dates
The website verifies the disclosure boundary rather than claiming public access to the private implementation.
Review due · Review window: 21 days
- Evidence date
- Record reviewed
- Snapshot evaluated
Source activity, the date of review and the website release are different events. A new website release does not renew this project’s evidence.
Open the dated state ledgerProject Intelligence 3 · 2026-08-18
Living state
Governed local orchestration, bounded realms, evidence-aware automation and reliable relay-backed workflows.
What changed
The public model now emphasizes authority boundaries and system relationships instead of operational access.
Updated 2026-08-18 · 21d freshness window
What’s next
- Harden governed execution
- Improve evidence continuity
- Keep realm boundaries explicit
Public dependencies
- SEBAS · governance_peer — Both systems emphasize local authority, approvals and bounded execution.
- ABEL · model_orchestration_peer — Model routing is represented as a bounded subsystem concern.
- Forja Yggdrasil · supports_workflows — Governed orchestration patterns support creative workflow design.
phase:activemulti-agent orchestrationgovernancepersistent private contextbounded automation
Architecture
- bounded realms
- operator-facing interfaces
- governance
- memory and evidence
- creative generation
- tools
- automation
- model experimentation
Components
Asgard
Governance, identity and authority boundaries.
Midgard
Operator-facing applications and inspectable interfaces.
Jotunheim
Knowledge and evidence boundaries.
Muspelheim
Creative-generation responsibility without public datasets or endpoints.
Niflheim
Long-lived private persistence and memory.
Svartalfheim
Low-level tools and implementation surfaces.
Vanaheim
Automation and auxiliary services.
Helheim
Controlled model experimentation.
Alfheim
Visual and interface expression.
Decisions
Separate responsibility by realm
Distinct authority and responsibility boundaries are easier to inspect than one unrestricted agent surface.
Publish architecture, not control authority
The public site can explain the system without becoming a route into private execution or memory.
Timeline
- Nine-realm public architecture modelmilestone · documented
- Private operational coremilestone · bounded
- Architecture is public; execution, memory, credentials and source remain private — public_boundaryevidence · 2026-08-11
Experiments
yggdrasil
Status: bounded
Open bounded Lab →Releases
No project-specific public release record.
Evidence
Architecture is public; execution, memory, credentials and source remain private
Architecture is public; execution, memory, credentials and source remain private
source-contract · checked 2026-08-11 · fresh until 2027-08-11
Boundaries
The website exposes architecture only: no remote execution, memory access, credentials or private clone path.
- No private memory payloads, credentials, workstation access, agent invocation or internal endpoints are published.
Start with a defined scope
For a collaboration, describe what you are building, what is constrained and the result you need. Public prototypes and architecture pages are not a promise of a finished commercial service.