Skip to main content
This page is the honest, current state — updated as we go, never aspirational.
Proven in production (pre-existing Vexa): the Runtime (meeting bots are browser workloads), transcription → transcript.v1, redis streaming. Built & proven live — the dispatch core (M1): a unit.v1 dispatch runs in a runtime-spawned, isolated container (the generic-agent worker), over a bind-mounted workspace, carrying a per-dispatch signed identity token, streaming UnitEvents on unit:<id>:out → SSE. The in-process path is retired (agents never run in the control plane). Chat memory is durable — session + transcript are saved in the workspace, so a fresh container resumes the conversation. Verified end-to-end on docker and through the terminal chat. See Execution. Designed & frozen (this site): the seven primitives, the identity layer (kagenti-aligned), the governance model. Sound and kept: the terminal workbench + surfaces, the generic event ingress, the generic tool mechanism, the redis scheduler. Next: finish M1 — the bucket-backed (minio) workspace store + warm-reuse (touch / idle-enforcer). Then M2 — the live meeting dispatch.

Delivery tracker

The planned features, the modules each touches, and status. The core features are ⬜ planned; Calendar is deferred. See Identity for the auth and encryption detail.
FeatureStatusModule(s) it touches
Auth spine — opaque token → User → scoped access end-to-end⬜ plannedcore/identity (admin-api), core/gateway
Owner-check adoption — wire OwnerOnlyPolicy / can_access onto every meeting path (chat · stream · start · process)⬜ plannedcore/agent, core/meetings, core/identity
Real meetings list — the live, persisted list of a user’s meetings on the surface⬜ plannedcore/meetings (meeting-api), core/gateway, clients/terminal
Routines: scheduled meetings — a routine.v1 / schedule.v1 job that joins on a cron⬜ plannedcore/runtime (scheduler), core/agent, core/meetings
Docs ↔ meetings binding — bind a workspace doc to a meeting (capture → governed action)⬜ plannedcore/agent (workspace.v1), core/meetings, clients/terminal
WebSocket coverage — the /ws multiplex fanning transcripts · bot status · chat⬜ plannedcore/gateway (ws.v1), core/meetings, clients/terminal
Bucket encryption — per-workspace envelope encryption; keys brokered, decrypted only in-container⬜ plannedcore/identity, core/agent (workspace.v1), core/runtime
Transcript encryption — encrypt transcripts at rest in the meetings database (the SSOT); protect the redis carrier (auth/TLS/ACLs)⬜ plannedcore/meetings, core/identity
User-token encryption — store API tokens hashed/encrypted at rest, not cleartext⬜ plannedcore/identity (admin-api)
Calendar (deferred) — calendar-driven auto-join🟦 deferredcore/runtime, core/meetings