How Arbora fits¶
Arbora is the platform edge and composition root. It is the running process that receives requests, establishes authority, and projects independently owned capabilities through one governed surface.
One request, five clear owners¶
| Layer | Owns | Arbora relationship |
|---|---|---|
| Agent Web UI | Browser interaction, chat presentation, and local UI state | Hosted by Arbora with an injected application composer. |
| Agent Terminal UI | Terminal and headless operation | Uses Arbora REST today; conversational ACP chat remains an explicit contract gap. |
| Geniusbot | Desktop cockpit for chat, graph, fleet, and health | Uses the governed Arbora gateway for its primary panels. |
| Messaging channels | Chat and voice entrypoints | Hosted and supervised by Arbora; adapters and the inbound router remain owned by agent-utilities. |
| Arbora | MCP, REST, A2A, request policy, fleet supervision, and process lifecycle | Authenticates, composes, routes, supervises, and projects. |
| agent-utilities | Agent decisions, workflows, evaluations, and skills | Provides typed application services to Arbora. |
| epistemic-graph | Durable multimodal state, RDF/OWL/SHACL reasoning, queries, and provenance | Provides generated storage and reasoning contracts. |
| agent-connector-sdk | Connector servers, source synchronization, and governed source effects | Defines the services admitted into the Arbora fleet. |
Runtime flow¶
- ReceiveAgent Web UI, Agent Terminal UI, Geniusbot, messaging, MCP, REST, and A2A converge on one Arbora process.
- AuthorizeArbora verifies identity, tenant, scope, and action policy.
- DelegateAgent work reaches agent-utilities. Source work reaches an admitted connector.
- CommitGoverned reads and mutations reach epistemic-graph with evidence and provenance.
- ProjectArbora returns the same result through the caller's selected transport.
Composition invariants¶
- MCP and REST handlers meet at the same application boundary.
- The serving lifecycle owns one FastMCP loop and one fleet multiplexer.
- Durable state and semantic reasoning are performed by epistemic-graph.
- Agent policy and workflow decisions are performed by agent-utilities.
- Connector credentials and vendor effects stay inside connector services.
- Browser presentation and local interaction state stay inside Agent WebUI.
- Missing authority produces an explicit unavailable result; Arbora does not manufacture state or success receipts.
Use the capability status page for the exact surface exposed by the current package.