Web console

The console is the substrate in a browser: a single-page app served beside the API, talking to the same public surface as every other client. It reads the whole graph and writes through the same public verbs, so nothing it does needs an endpoint no other client has.

Signing in is the same exchange ssctl makes: tenant name plus the current 6-digit code (authentication), with pasting an existing token as the fallback. What it offers:

• Overview: connection health, recent activity, pending merge requests, and every group with a live count per entity type. Every tile is a door to the page it summarizes.
• Data: browse groups, their entity types, and each type's collection; filter and page through entities. An entity opens on four tabs: its manifest, its activity (the entity's own slice of the changelog), its incoming edges, and its provenance, the per-property ledger (managed properties). Entities are writable here too: create and edit go out as the ordinary put.
• Stream: the changelog newest first, one row per committed change, expandable in place to its payload, faceted by type, group, actor, op, and time, and tailed live with Follow.
• Extensions: the extensions area, in two sub-views. Catalog lists available and installed extensions together, with All and Integrations facets and an Integration badge on provider rows; an extension's own page carries the lifecycle verbs (disable, enable, purge, uninstall) and starts the OAuth flow for an account. Connections shows configured provider accounts and their sync health, one row per account, over the native accountconfig accounts that integration extensions ship.
• Triggers: every trigger with its kind, callable, cursor, lag and parked count; a row expands to its run ledger and its parked deliveries, and wake, replay and per-failure retry are buttons on it.
• Agents: the declared agents and the llm rows they resolve. An agent row opens a chat surface that streams one run, and the transcript persists as ordinary thread and message entities. Alpha, like the agents themselves.
• Merge requests: the queue of proposed merges with the matcher's evidence, a field-by-field comparison of the two entities, and accept or reject, stating what recompute settles and that a merge is reversible.

Next: built-in entity types, the shipped vocabulary.