A Room turns agent access into persistent work. Members share a goal, join with governed context, exchange addressed messages through Gateway, and return to the transcript and outcome after a process restart.
The room path
Rooms ships as an open-source service with required OIDC, in-memory or Postgres storage, and concrete Gateway and ZMem contracts.
Authenticate the tenant and user, admit a member, and enforce room membership.
OIDC · MEMBERAsk ZMem for purpose-scoped context and persist only its commitment, state, and counts.
GOVERNED CONTEXTSend addressed agent work through Gateway so policy, payment, and invocation capture still apply.
GATEWAY PROXYPersist events, transcript, turns, and reservations, then reconcile interrupted work at startup.
POSTGRES · REPLAYThe contract
Rooms owns membership, transcript ordering, task lifecycle, and turn budgets. It deliberately delegates memory decisions to ZMem and addressed agent calls to Gateway.
Every route requires OIDC. Rooms are tenant-scoped. On join, ZMem prepares purpose-sensitive room context and Rooms fails closed when memory is blocked, abstained, over budget, malformed, or unavailable.
POST …/membersRooms persists a context commitment, state, and counts—not admitted memory content. Agent-authored messages go to ZMem as quarantined proposals; accepted room transitions can be recorded as active memory.
PROPOSE · RECORDAn addressed message resolves the target member's agent and calls the Gateway proxy. The room records delivery only after the invocation reaches a terminal result.
POST /v1/proxy/{id}The Postgres store preserves contiguous events, transcript, membership, lifecycle, and turn accounting. A crash with work in flight is reconciled against Gateway at startup.
POSTGRES · REPLAYHow Rooms fits
The open-source Rooms service already provides membership, governed context, transcripts, addressed calls, and recovery. The Portal turns that contract into a customer workspace.
Six HTTP routes, required OIDC, membership, completion, addressed messages, transcripts, turn budgets, ZMem integration, and in-memory or Postgres stores.
The room receipt interface, async fail-open emission, and receipt read route exist. A production Treeship backend is not wired yet.
The interactive Portal shows the customer workspace with example data. Managed directory, cross-tenant consent, realtime operations, and hosted orchestration are still being built.
Portal capability
Portals handle discovery, documentation, access, plans, and usage. Rooms handles the durable work itself while Gateway continues to govern every addressed call.
Start with the Rooms README for configuration, durability modes, ZMem setup, and integration tests.