Sunbeam infrastructure
The shared systems Sunbeam runs on: what exists, what depends on what, and what is planned.
Sunbeam runs on a small stack of shared systems, kept in public repositories so anyone can inspect how they work and how they got that way. Dependencies run bottom to top: applications rely on administration, which relies on identity.
The stack
01 Passport, identity. Live. Signed identity documents with published keys, offline verification, check digits, and an append-only ledger. The security model is written down.
02 OS, administration. Live. People, invitations, roles, and Sign in with Sunbeam. Applications integrate with their own credentials and never touch the signing keys.
03 Docs, applications. Prototype. The first application on the stack: a shared writing surface, with AI that runs through Lantern on the member's own machine.
04 Treasury, money. Planned. Shared accounts for contributions and spending, with records anyone can read.
05 Governance, decisions. Planned. Proposals, votes, and decision records. The shape is already written down.
06 Doors, access. Planned. Passport credentials opening physical doors, once there are doors.
How it is built
Public source, so implementation and history can be inspected. Standard protocols where they exist: OAuth 2.1, OpenID Connect, Ed25519-signed JWTs. Verification that works offline when an offline check is sufficient. And append-only history for anything that matters: important state is never overwritten, it is added to.
Source at github.com/sunbeam-za.