Skip to main content
waiOS · Room policies and metering

Every room under one policy. Every session on the record.

A room's descriptor, signed by its authority, fixes its roles and what each may do, its limits, its review policy and its recording policy, and its digest is the room's id. Each participant takes part under a signed grant with a window and joule and funds ceilings, honoured only beside a proof of its key. Every hop that carried a session signs its record, and a verifier replays the room. A public room runs at wai.transaction.science, and the room service and relay build from source to run in your own infrastructure.

01 · What you get

What a room carries.

  • A signed room descriptor and grants: roles and powers, a grant window of at most fourteen days, its event policy and its joule and funds ceilings, revoked through the key log.
  • Review policies, decisions with their statements, and a statement of reasons for each restricting decision.
  • Every event of a room signed by its sender and chained to that sender's previous one, so a gap is told apart from a change.
  • Recordings as one package with clips that prove what they are, and a seek-back window served only to a grant with the seek power.
  • End-to-end encrypted rooms, keyed from one MLS group per room, which are never recorded.
  • A signed record from every hop of a session, and a room-session receipt its verifier recomputes.
02 · Messaging and calling

A conversation is a room. So is a call.

  • A conversation is an end-to-end encrypted room, keyed from one MLS group. Each message is sealed under the group and signed by its author: a text, a reply in a thread, a reaction, an edit or a retraction. Delivery and reading are signed acknowledgements.
  • The room's authority admits and removes members, and the room's clock signs each epoch's roster. A removed member opens nothing sealed after its removal, and a member that was offline catches up from a history store that holds no plaintext and no key.
  • A call is a room with a call descriptor its authority signs. The caller rings each invitee with an invitation it signs, every accept, decline and cancel is a signed answer, and the room's clock signs a missed call. Its audio and video are the room's own tracks, between two participants or among many.
  • Every record verifies offline. Given a conversation's log, a verifier states each epoch's roster and each message accepted, or refused with its reason; without an epoch's secret it still checks the message's receipts and states it sealed. A call's records verify the same way, and a room's signed events replay into its state.
03 · How it works

The open components it runs on.

Each is in the main branch of the WAI open standard. Its first link goes to its row on the WAI status page, and its notes are that row's.

Attested, in WAI, means signed by the party that did the work and measured it: a reader can check the signature, not re-measure the figure. It is not hardware attestation.

  • Room descriptors and grants: the roles and what each may do, each grant's window, event policy and ceilings, exchanged on the room clock and revoked through the key log.

    Notes How a principal obtains a grant, and how a ceiling is held while a session runs, are the deployment's. Several of its bindings follow Internet-Drafts, which may still change.

  • A review policy signed by the room authority, decisions with their statements, notices, and a statement of reasons for each restricting decision.

    Notes How a moderator or a classifier reaches a verdict, and how a notice reaches the room authority, are outside the text.

  • Every decision, lifecycle change and grant exchange is a signed event, chained to its sender's previous one.

    Notes An event's time is its author's claim: a verifier checks that one author's times never go back. Events are signed, not encrypted.

  • A recording manifest held to the room's region pin, and clips that prove they are exact spans of a take.

  • The seek power: a relay keeps a window of a room's tracks, and serves a fetch below a track's live edge only to a grant that holds the power.

    Notes The public demonstration room keeps a fifteen-minute window.

  • End-to-end encrypted rooms, which are never recorded.

    Notes Members run natively in the reference crates and, built for WebAssembly, in a browser page, and the reference room service carries a room's MLS messages. Events, catalogs and receipts stay in the clear. The secure-objects and MLS keying texts it follows are Internet-Drafts, the keying one an individual draft, which may still change. The construction the specification named before this revision is withdrawn.

  • A record signed by every hop of a session, and a room-session receipt that states each hop's joules by class and each grant's use against its ceilings.

    Notes The reference relay signs its record with the unmetered marker. Prices, billing and holding a ceiling while a session runs are the deployment's.

  • The relay, the room service and the browser client the public room runs on, over Media over QUIC Transport.

    Notes Drafts do not interoperate with each other, so a session is one draft from its first byte to its last; the relay maps drafts 18 and 16 onto draft 22's model and names what one draft can say and another cannot, and the extension's envelopes, receipts and catalog fields are the same on each. Runs against other implementations' relays and clients are recorded, with their date and every result, in the codec's README; they reach the public internet, so none is in CI. The browser client speaks draft 22, and the public room reaches its relay over the WebSocket binding.

04 · How to start

Use the public room, or run your own.

  1. Open the public room in a browser. Its room service answers GET /room with the signed room descriptor, the composition descriptor and the publishers' grants, and its relay speaks Media over QUIC over the WebSocket binding, with the subprotocol moqt-22.

    https://wai.transaction.science/room/
    curl https://wai.transaction.science/room-api/room
    wss://wai.transaction.science/moq
  2. To run a room in your own infrastructure, get the source, build the room service, and make its keys; it prints the lines the relay's configuration needs to trust them. Its room.example.toml shows every field of the service's configuration.

    git clone --depth 1 https://git.transaction.science/Transaction-Science/open-standards.git
    cd open-standards/joule-code/joule-code-rs/crates/joule-moq-room
    cargo run -- keygen keys.toml
    cargo run -- relay-lines keys.toml
    cargo run -- --config room.toml
  3. Run the relay: --dev serves loopback with a development certificate, and --config takes a relay.toml (relay.example.toml shows every field).

    cd open-standards/joule-code/joule-code-rs
    cargo run -p joule-moq-relay -- --dev