Infrastructure reference

System index

Systems and dependencies

The systems are listed in dependency order. Solid rows have an implementation today; dashed rows describe areas that have not been implemented.

06 Doors · access Planned use of Passport credentials for physical access. Depends on a site and compatible door hardware. Not started

05 Governance · decisions Planned support for proposals, voting, decision records, and their history. Not started

04 Treasury · money Planned shared accounts for contributions, spending, and readable financial records. Not started

03 Docs · applications Application layer for members. The first implementation is a shared writing surface. Prototype 02 OS · administration Shared administration for people, invitations, roles, and application sign-in. Implemented 01 Passport · identity Signed identity documents with published keys and independent verification. Implemented

Dependencies run from bottom to top: applications rely on administration, which relies on identity.

Current systems

Implemented and in-progress

Passport

Implemented

The identity layer. Passport issues Ed25519-signed tokens, publishes verification keys at /.well-known/jwks.json, supports offline verification, and records changes in an append-only ledger. Document numbers include check digits.

About Security model Verify Code

OS

Implemented

The administration and authentication layer. It manages invitations, people, and roles. Sunbeam applications integrate through their own client credentials rather than receiving access to signing keys.

Code

Docs

Prototype

The first application on the shared stack. It provides pages, block-based writing, and optional AI features through Lantern, paired to the member’s local AI runtime.

Code

Technical policy

Defaults for shared systems

Public source

Shared infrastructure is kept in public repositories so its implementation and history can be inspected.

Standard protocols

Use established formats and protocols where possible, including OAuth 2.1, OpenID Connect, and Ed25519-signed JWTs.

Independent verification

Publish the information required for verification and avoid a network dependency when an offline check is sufficient.

Recorded history

Use append-only ledgers or revision histories for important state changes instead of replacing the previous record.

Scope: Passport, OS, and Docs are the only layers with code today. Treasury, governance, and physical access describe intended areas of work, not committed delivery dates.

Project directory