Specifications and guides

These are the working documents, served as plain text from this site rather than from a code host. They are the same files the code is written against. They are also where the technical detail lives: ports and protocols, the exact field numbers, the encryption design, and what a host can still see.

• protocol.mdThe frozen wire protocol: transports, every control frame, the 28 byte media envelope, auth, limits.
• crypto.mdThe end-to-end encryption design, channel key epochs, the invite format, and the threat model including what the host can still see.
• ARCHITECTURE.mdHow the pieces fit, why the server relays rather than mixes, and the latency budget.
• deploy.mdHosting it yourself: the wizard, ports and firewall, TLS, backups, upgrades, and the six most likely failures.
• latency-method.mdHow the latency figures were measured, what comes from documents and what was actually measured, and the command that regenerates them.
• bridge.mdThe narrow API between the desktop shell and the shared client.

These documents are the substitute for reading the source, which is not published. They state what the code does, including the parts that are deliberately out of scope.