Skip to main content
Version: Target · roadmap

Context: rooms & sessions

What the platform holds for the station. There is no key to write: this page says what exists, so you can write the rules that use it.

The room​

A room is a person's space with the station. It has a short code (u35mub), the same on every door: the tenant's site, Claude, ChatGPT, Teams. It holds:

  • the selection: the room's order of actions, the reserved writes and the traces of reads. The person changes it in the interface, the agent through its tools; a successful submit empties it;
  • the active journey, if there is one;
  • what the person said about themselves and the agent kept (remember);
  • the records of what was submitted: the lines, the amounts, the tenant's references, the resume link. Every door reads them back, a second agent included.

A room starts anonymous. Typed data identifies it; verified data makes it belong to someone, its owner. See Identity.

The code opens the room: whoever holds it sees the selection and the records, and can submit if no submitted_by: owner prevents it. The conversation thread, for its part, is shown only to the owner, signed in, as soon as the room has one.

The session​

A session is a visit. A room has several: the same person comes back tomorrow, or opens their room from another door. Reopening the room during the same visit does not create a session; opening it from elsewhere does. The session is used to count visits and to tell where each message of the thread came from.

The journey belongs to the room​

A process lasts days: the agent opens the ticket on Monday, the manager approves on Wednesday from Teams, in another session. A session attaches to the room's journey. There is one single active journey per room (with its stack of sub-playbooks). Each actor joins the room with their own identity and profiles.

The conversation thread​

The conversation thread is stored server-side, per room. Each message keeps the session and the portal that showed it. The server writes it at the end of each turn. It keeps only what is displayed: the person's messages, the agent's answers, the rendered frames. It never keeps the instructions given to the model, nor the tools' arguments, nor their raw results. A failed turn leaves nothing.

On opening, the portal asks the server for the thread, with only the room_id. The server gives back the room's latest messages.

Who can read it:

  • a room with no owner: whoever holds the code;
  • a room that has an owner: the owner alone, signed in on this portal. Others see "This conversation belongs to an account. Sign in to see it.", with the sign-in steps. Once signed in, the person sees the conversation.

This is not the model's memory: that is a short window. Claude and ChatGPT keep their own conversation; what passes from one door to another is the room.

What the browser keeps​

Two identifiers, in sessionStorage: room_id and session_id. Nothing else — no messages, no selection, no personal data. A PWA closed then reopened starts on a new room, unless it is given the code again.

How long​

The room and what it holds — selection, conversation thread, records, identity data — are erased after 24 h if it is empty, after 90 days of inactivity otherwise: these are the default durations, adjustable per tenant. The log, for its part, is kept for the duration the law imposes on the tenant, longer than the room. See Data.