Skip to main content

Public architecture

Follow declared relationships, not an invented stack.

This view is derived from repository-owned documentation manifests at the revisions in the source lock. An arrow states its relationship explicitly; the reading journeys do not imply dependencies.

Pan the full-size diagram: swipe or scroll, or focus the canvas and use the arrow keys.

Public repository relationshipsProvider and consumer relationships declared by owning repositories. Focus the visual to pan at full size, or open its complete text alternative.
Diagram as text

Nodes

  • AEP aep
  • AEP Service aep-service
  • Agent stack agent-stack
  • Agentic Principles agentic-principles
  • AgentIDE agentide
  • Agent Plugins agentplugins
  • Connectors connectors
  • Docs System docs-system
  • Engineering Protocols engineering-protocols
  • Entity Runtime entity-runtime
  • ESS ess
  • Eventlog eventlog
  • Extensions extensions
  • Harness harness
  • Identity identity
  • LLM llm
  • Mandate mandate
  • MCP mcp
  • Metaharness metaharness
  • Agent interaction research research
  • Secrets secrets
  • Service SDK service-sdk
  • Substrate substrate
  • beyond10x website
  • Workflow workflow
  • Workspace workspace
  • Worktree worktree

Relationships

  1. AEP to AEP Service: specifies
  2. AEP to Entity Runtime: uses
  3. AEP Service to AEP: implements
  4. AEP Service to Entity Runtime: uses
  5. Agentic Principles to AEP: informs
  6. AgentIDE to ESS: uses
  7. Agent Plugins to AEP: supports
  8. Agent Plugins to ESS: supports
  9. Connectors to Eventlog: uses
  10. Connectors to Identity: uses
  11. Engineering Protocols to AEP Service: specifies
  12. Eventlog to Identity: supports
  13. Eventlog to Workflow: supports
  14. Extensions to ESS: uses
  15. Identity to Eventlog: uses
  16. Metaharness to Harness: drives
  17. Agent interaction research to AEP: informs
  18. Agent interaction research to Agentic Principles: informs
  19. Agent interaction research to Agent Plugins: informs
  20. Secrets to Connectors: supports
  21. Secrets to Identity: uses
  22. Service SDK to ESS: uses
  23. Service SDK to Eventlog: uses
  24. beyond10x to AEP: introduces
  25. beyond10x to AEP Service: introduces
  26. beyond10x to Agentic Principles: introduces
  27. beyond10x to AgentIDE: introduces
  28. beyond10x to Agent Plugins: introduces
  29. beyond10x to Docs System: introduces
  30. beyond10x to Entity Runtime: introduces
  31. beyond10x to ESS: introduces
  32. beyond10x to Eventlog: introduces
  33. beyond10x to Identity: introduces
  34. beyond10x to MCP: introduces
  35. beyond10x to Agent interaction research: introduces
  36. beyond10x to Workflow: introduces
  37. beyond10x to Workspace: introduces
  38. beyond10x to Worktree: introduces
  39. Workflow to AEP: uses
  40. Workflow to Eventlog: uses
  41. Workflow to Identity: uses
  42. Worktree to Agent Plugins: supports

Download the deterministic graph projection.

Agent stack

One owner per layer

Seven layers from products down to model providers. A layer depends only on the layers below it. Recorded in the organization's architecture decisions 0096 to 0101 (2026-10-20), 0105 and 0106 (2026-10-22).

Open the agent stack as an interactive page: the layers assemble as you scroll, a call travels down them, and every term links to its definition and repository.

Pan the full-size diagram: swipe or scroll, or focus the canvas and use the arrow keys.

The agent stack: one owner per layerSeven layers from products down to model providers, with each layer's responsibilities and the repositories and libraries that own it.Download source
Layers as text

Products (Agency, loom-coder, swarm, agentide) are what a person uses; loom-coder has no repository yet. Applications (takt, b10x-loom, conductor) build on loom-sdk; conductor sits on top of Agency. L3, the governed runtime, is Loom. L2, the harness interface, is metaharness. L1 is harness, Claude Code and Codex, with tools. L0, the model call, is llm and inference. Providers (Anthropic, OpenAI, self-hosted through llm-gateway) are outside beyond10x.

Pan the full-size diagram: swipe or scroll, or focus the canvas and use the arrow keys.

How a request travels through the agent stackThe products on top, then from the operator through takt and Loom, then either straight to llm for Loom's own decisions or through metaharness to harness, Claude Code or Codex, down to the model providers.Download source
Request path as text

The operator gives takt an intent or a story. takt opens a case in Loom through loom-sdk. Loom calls llm directly for short decisions (classify, select, fill arguments) and runs agent work as a session through metaharness, which drives harness, Claude Code or Codex. Those call llm, which calls the provider. Commission in Loom applies the proposed change.

Definitions

Each term, the layer it names, and the repositories that own it.
TermLayerWhat it doesOwned by
Model callL0One turn in, one turn out: messages and tools in; text, tool calls and usage out. Owns provider wires, credential presentation, routes and cost; custody and OAuth2 refresh of a credential belong to Connectors.llm (GitHub), inference, llm-gateway
HarnessL1The agent loop: turns, prompt assembly, tool round trips, compaction, session and transcript, budgets. Claude Code and Codex are vendor harnesses; tools holds the tool contracts.harness (GitHub), tools
Meta-harnessL2Starts any harness behind one event stream and one command set, allows, denies or rewrites each tool call, and records every session as trace-ir/1.metaharness (GitHub)
Agent runtimeL3 · governed runtimeLoom; loom-sdk is its library. Opens a case on a protocol and lets a model act only through the actions the case admits at that moment. Calls llm for its own short decisions and metaharness for agent work.Loom
Applicationabove L3An end-to-end use of the stack, built on loom-sdk. takt delivers stories and counts nothing done until a validator records the evidence; it manages agents and is not one. conductor coordinates Claude Code sessions across the repositories of one organization and sits on top of Agency.takt, conductor
Productabove the applicationsWhat a person uses on top of the stack. Agency is where the operator manages agents, work, teams, auth and tools; control-plane converges into it. loom-coder is a Loom-based coding agent with a command line and a web version; it has no repository yet.Agency, loom-coder, swarm, agentide