agent-surfaceAn explicit agent surface for your frontend

If a component or capability is not explicitly annotated, it does not exist for the agent. Semantic, typed, lifecycle-aware, deny-by-default. Specification and v0.1 implementation, published as 0.x.

Start with the Vision

Conceptual Model

Core API

Devices Page Walkthrough

Capabilities, not DOM

Components register semantic observations and actions (view:devices.table.selectRows) — never clicks, selectors, coordinates, or screenshots.

Two planes, never blurred

Domain operations stay oRPC procedures exposed via orpc-agent; the frontend only references them contextually, with UI-bound inputs. No duplication, ever.

Governed by the runtime

Composable policies, single-use confirmation evidence, typed errors, staleness rejection, audit events. The runtime decides — not the model.

Testable without an LLM

The surface is a typed contract — discovery, invocation, confirmation, and staleness are asserted deterministically with the testing package.

How to read these docs

Pick the path that matches why you're here:

"Give me the idea in 10 minutes" — Vision, then the five-sentence summary at the top of Concepts, then skim the devices-page walkthrough.
"I'm building an app with this" — Concepts → React API → oRPC Integration → the devices-page example (the one runnable, tested app in the repo). For a server-side loop, the Mastra + assistant-ui wiring guide sketches the shape — hand-written snippets, not an executable package.
"I'm implementing the library" — Architecture → Core API → Errors → Testing → Implementation Plan. The decision log explains every non-obvious choice; the Spec Corrections RFC records the P0 protocol corrections (D21–D26) and the Maintainer Directive is the standing execution contract.
"I'm reviewing this for security" — Policies & Security end to end, then Non-Goals and the honest-limits notes in the Completeness Review.