Souspli / Docs / Design notes
Design notes
Each subsystem of Souspli was built from a written brief: what it is for, the one principle that governs it, what is deliberately out of scope, and how it is tested. They are kept here as written, as decision records — the reasoning is usually more useful than the conclusion.
They are not documentation. They use the code's names (thing, shell, cage; see the glossary), their "out of scope" sections are frozen at the date shown, and several describe as future work things that now exist. For how things are today, read How it works.
| Written | Note | About |
|---|---|---|
| 2026-07-16 | cage | The sealed container: four hardening layers and the escape battery. |
| 2026-07-19 | bridge | The four-function bridge and what it withholds. |
| 2026-07-19 | format-spec-notes | What building the bridge taught the format specification. |
| 2026-07-20 | security-review-round2 | Resolution of two rounds of internal security review. |
| 2026-07-21 | transport | Locators, bounded fetches, content-addressed integrity. |
| 2026-07-23 | naming | Names: the resolver is untrusted for the key. |
| 2026-07-23 | conformance | Interop vectors for a second implementation. |
| 2026-07-23 | authoring | Authoring as the mirror of admission. |
| 2026-07-25 | packaging | Installers for testers. |
| 2026-08-23 | sandbox | The OS sandbox: why the suite runs with it off, and how that is kept honest. |
| 2026-09-13 | relay | Nostr relays: the first push transport; offers and pointers. |
| 2026-09-13 | forum | A forum out of existing primitives plus one new type, the vote. |