Skip to content

Overstory: operator experience for Arbora

See the work. Guide the agent. Explore the evidence.

Overstory brings conversations, governed actions, workflows, fleet activity, and epistemic knowledge into one role-aware browser workspace.

Canopy light Explore workspace with a synthetic research brief and the persistent assistant.

Canopy light with synthetic demo data and the persistent assistant. Open Appearance to choose Canopy light or dark and Glass or Opaque framing. See the workspace gallery and screenshot refresh guide.

One interface, explicit authority

This repository owns
Browser presentation, accessible route composition, local interaction state, and the WebUI FastAPI boundary.
Arbora owns
Public routing, verified identity, runtime policy, fleet supervision, and composition of this UI.
The platform owns elsewhere
Agent behavior lives in agent-utilities, durable knowledge in epistemic-graph, and source effects in connector services.

Choose the operator's path

Try it

Install the Overstory integration, start one local composition, and open the browser workspace.

Open the start guide →

What operators can do

  • Hold agent conversations with sources, tool activity, and approval prompts.
  • Build workflows and inspect active sessions, goals, schedules, and fleet health.
  • Use Understory to move between graph, RDF, schema, object, table, document, code, and memory views.
  • Discover MCP Apps and connector capabilities through the Arbora boundary.
  • Apply the same role-aware navigation and server authorization model across the complete workspace.

Request flow

  1. Interact

    The operator chats, explores knowledge, approves an action, or runs a workflow.

  2. Govern

    The same-origin WebUI host and Arbora verify identity, route the request, and apply policy.

  3. Run

    agent-utilities runs agent behavior while epistemic-graph and connector services perform their owned operations.

  4. Observe

    Typed events, evidence, and governed results return to the browser without service credentials crossing the boundary.

Explore the interface

Specification delivery

Open the specification delivery dashboard for current specification status, delivery timelines, velocity and burndown, and open pull request and issue snapshots. It refreshes with each main-branch push. Unknown completion dates and unavailable history are labeled explicitly; individual requirements and pull requests do not count as completed specifications.