How the ecosystem fits¶
The five repositories form one runtime. Each owns one kind of authority, and Arbora presents those capabilities without duplicating them.
Component ownership¶
Arbora
The operator experience: browser presentation, local interaction state, accessible navigation, and a same-origin server boundary.
Arbora
The public runtime gateway: MCP, REST, A2A, identity, policy, fleet supervision, and WebUI composition.
agent-utilities
The agent control plane: agent decisions, orchestration, workflows, evaluation, and skills.
epistemic-graph
The durable multimodal engine: graph, SQL, RDF, vector, time, blobs, reasoning, provenance, and transactions.
agent-connector-sdk
The governed source boundary: typed discovery, reads, ingestion records, server registration, and write-back contracts.
One request, one owner at every step¶
-
Present
Arbora collects the operator's intent and renders typed events and results.
-
Admit
Arbora verifies identity, applies runtime policy, and selects the owned service boundary.
-
Act
agent-utilities runs agent behavior; connector services perform authorized external effects.
-
Commit
epistemic-graph validates and records durable state, evidence, provenance, and receipts.
What the WebUI consumes¶
| Surface | Authority | WebUI responsibility |
|---|---|---|
| Chat, sessions, goals, workflows, prompts, skills | agent-utilities through Arbora | Render state, collect input, and surface approvals |
| Graph, RDF, schema, objects, tables, code, documents, memories | epistemic-graph through Arbora | Provide guided and expert exploration without storing a second truth |
| MCP Apps, connector catalogs, source operations | Arbora and connector services | Discover typed capabilities and render governed invocation results |
| Identity, roles, request policy, fleet health | Arbora | Apply the server decision to navigation and interaction controls |
The browser never receives an Arbora service credential. The WebUI FastAPI host performs same-origin delegation using the verified request context injected by Arbora, and every downstream component remains authoritative only for its own contract.
Shared language¶
Use the ecosystem glossary for the canonical meaning of Arbora, the agent control plane, the knowledge engine, connector boundary, MCP, A2A, OWL, RDF, SHACL, and UQL.