If you want to build with it

In short. Everything Habitat publishes can be checked without us: receipts by fingerprint, anchors offline, kits on your own machine. The files Desk makes are plain JSON, signed with Ed25519. Every check Record runs on your file happens in the browser; Published also fetches the Foundation's public anchor files, and Words’ Check reads your paragraphs again on the server.

Where to start

you want to	go to
recompute a published receipt	Run a kit
check that a receipt is the one the Foundation published, offline	Check a receipt, four ways
read or produce Desk's files (receipts, saves, gems)	File formats
run the checks over many session logs	The census tools
know exactly what reaches our server	What is kept, and where
see how the pieces fit together	How it fits together
see the routes that keep what they are given	The API
see the rules each check applies, word for word	Record

What you can rely on

• The same input gives the same output. Checks are deterministic. Kits pin their arithmetic, and the method page lists the platforms and numpy versions where it has been measured.
• Rules are written down beforehand. Each check's rule and limit are printed with its result and written into the receipt.
• Signing is plain. Ed25519 over a short message: the format version, the kind of file, its SHA-256 digest and the time. The public key is in the file. See File formats.
• Anchors use public tools. The Foundation's receipts are DSSE in-toto statements (a standard signed envelope) entered in Sigstore's Rekor. Our offline verifier checks nine things and makes no network calls.

Run a pilot with us

If you have a record you need others to trust, a pilot is the way in: what a pilot team gets, brings and keeps. Or write to hello@thecommons.ooo with a few lines about the record.

What is not public

The Desk source, the server and the census tools are not public repositories. The kits, the anchor verifier, the public keys and every receipt are.