Board work, in chat

The board asks. Answer in chat.

SuperExchange is a Matrix application service. It carries SuperPipeline’s gates, questions and waiting cards into the board’s encrypted room, and when a person answers there, the board acts on it as that person.

Read the README Source on GitHub

Early: v0.0.2 · MIT · runs in production, no production board moved to it yet

#superexchange_board_brd_launchencrypted

superpipeline board

Approval needed — “Launch post” at stage review. Approve, request changes, or reject.

Approve “Launch post”?

gate · stage review

ApproveRequest changesReject

Ana answered with the card

Approve

superpipeline

Approved by Ana — the board has it.

Example room. The wording is treaty’s; the card and names are made up.

How an answer reaches the board

One path per board, one message per event, one receipt per answer. The steps below are a gate; questions, follow-ups and waiting cards go the same way.

- SuperPipeline boarda gate opens at reviewgate.pendingresolved as Ana
- Event relaytreatysigned delivery
- SuperExchangeits own store, keys and registrationposts it onceone receipt
- Accountswho sent this?a person: Ana
- The board’s roomMatrix, end-to-end encryptedgate cardApproveApproved by Ana
The board raises a gate; the relay delivers it to SuperExchange, signed.The room is made once, people invited; the gate is posted once, encrypted.Ana answers with the card; Accounts says she is a person.The gate is resolved as Ana, and the room gets one receipt.
1
The board raises a gate
SuperPipeline publishes gate.pending to the suite’s event relay, which delivers it to SuperExchange signed. It is kept only for boards an operator has opted in.
- SuperPipeline boarda gate opens at reviewgate.pendingresolved as Ana
- Event relaytreatysigned delivery
- SuperExchangeits own store, keys and registrationposts it onceone receipt
- Accountswho sent this?a person: Ana
- The board’s roomMatrix, end-to-end encryptedgate cardApproveApproved by Ana
The board raises a gate; the relay delivers it to SuperExchange, signed.The room is made once, people invited; the gate is posted once, encrypted.Ana answers with the card; Accounts says she is a person.The gate is resolved as Ana, and the room gets one receipt.
2
It is posted once, encrypted
SuperExchange makes the board’s room once, invites the board’s people, waits until one has joined, then posts the gate exactly once. Rooms are end-to-end encrypted with SuperExchange’s own keys.
- SuperPipeline boarda gate opens at reviewgate.pendingresolved as Ana
- Event relaytreatysigned delivery
- SuperExchangeits own store, keys and registrationposts it onceone receipt
- Accountswho sent this?a person: Ana
- The board’s roomMatrix, end-to-end encryptedgate cardApproveApproved by Ana
The board raises a gate; the relay delivers it to SuperExchange, signed.The room is made once, people invited; the gate is posted once, encrypted.Ana answers with the card; Accounts says she is a person.The gate is resolved as Ana, and the room gets one receipt.
3
A person answers in the room
Accounts says who the Matrix sender is. Only a person may answer, and only with an option the gate offered. An agent’s answer, or one from another room, is ignored.
- SuperPipeline boarda gate opens at reviewgate.pendingresolved as Ana
- Event relaytreatysigned delivery
- SuperExchangeits own store, keys and registrationposts it onceone receipt
- Accountswho sent this?a person: Ana
- The board’s roomMatrix, end-to-end encryptedgate cardApproveApproved by Ana
The board raises a gate; the relay delivers it to SuperExchange, signed.The room is made once, people invited; the gate is posted once, encrypted.Ana answers with the card; Accounts says she is a person.The gate is resolved as Ana, and the room gets one receipt.
4
The board acts as that person
The gate is resolved at SuperPipeline as the person who answered, and one receipt is posted. A repeat is told it was already decided. A gate decided on the web is settled in the room by the next sweep.

SuperPipeline boarda gate opens at reviewgate.pendingresolved as Ana
Event relaytreatysigned delivery
SuperExchangeits own store, keys and registrationposts it onceone receipt
Accountswho sent this?a person: Ana
The board’s roomMatrix, end-to-end encryptedgate cardApproveApproved by Ana

The board raises a gate; the relay delivers it to SuperExchange, signed.The room is made once, people invited; the gate is posted once, encrypted.Ana answers with the card; Accounts says she is a person.The gate is resolved as Ana, and the room gets one receipt.

What it carries

Everything a board waits on a person for, posted in the board’s room and answered there. The event formats are treaty’s: SuperExchange carries them, it does not define them.

Gates

An approval or a choice a stage is waiting on. Approve, request changes or reject from the room; a choice of versions names the one you pick.

Board questions

An agent blocked on a person, or a SuperToolkit approval request. Answer with the card, or type the number or label of an option. A typed reply can decline an approval, never grant it.

Delivery follow-ups

A post approved for manual delivery still owes the board its live link. Record the link, or switch to automatic delivery when the whole post could be shown.

Waiting cards

A card parked for a person after repeated failures, a block or a missing permission. Resume it here or at an earlier stage, with an instruction for the next attempt, or archive it.

Notices

Reminders, escalations to the workspace’s admins, quorum progress, held approvals and failed or overridden checks, each said once, in reply to its card.

Pull-backs and overrides

Pull a gate back, or override a failed check, from the room. Each needs a comment, and acts as the person who sent it.

What it needs

SuperPipeline, whose boards it speaks for, read and acted on through its API.
The event relay (treaty’s), which delivers the board’s events signed.
A Matrix homeserver, where it registers as an application service with its own namespace.
Accounts, the organization plane, which says who a Matrix sender is and vouches for them to the board.

What needs it

Nothing. SuperPipeline remains a board without it, and its gates are still decided on the web and in supi.
SuperMessage remains a plain Matrix client. Any Matrix client can read and answer the room.
A board leaves by being taken out of SuperExchange; agents keep working either way.

Run it

From source, with Bun. Every setting is in the README; a missing or malformed one stops it before it listens, naming the setting, never its value.

$ bun install
$ MATRIX_HOMESERVER_URL=… MATRIX_SERVER_NAME=… MATRIX_AS_TOKEN=… MATRIX_HS_TOKEN=… \
TREATY_RELAY_DELIVERY_SECRET=… SUPEREXCHANGE_OPERATOR_TOKEN_SHA256=… \
ORG_PLANE_URL=… ORG_PLANE_SERVICE_CREDENTIAL=… SUPERPIPELINE_URL=… \
SUPEREXCHANGE_CRYPTO_PASSPHRASE="$(openssl rand -base64 32)" SUPEREXCHANGE_DATA_DIR=$PWD/.data \
  bun apps/exchange/src/main.ts
$ curl http://127.0.0.1:8080/healthz

An operator then opts a board in through PUT /v1/boards/:boardId. Back up the crypto store with the database: lose it and the room keys go with it.The full setup is in the README.

Where it is today

Early, and honest about it. This is v0.0.2.

It runs in production, but no production board has moved to it yet. A board moves one at a time, and until it does, its chat stays where it was.
SuperPipeline does not yet relay the board-room notices (reminders, escalations, quorum progress, held approvals, checks). SuperExchange is ready to say them; until the board sends them, it says nothing.
The follow-up and waiting-card sweeps cannot read the board with a service token yet, so they back off. Those cards still arrive and are answered through the relay.
An answer from a Matrix account that is linked to nobody does not count. The person is told how to link it, at most once a day per room.
No published image, package or hosted service: you run it from source.

Source on GitHub, mirrored from the forge (where pull requests are made; it needs a forge account). What changed in each release is in thechangelog.