What the project needs
Loading the board…
Name a gap
Couldn’t find something? Hit a thing the library is missing? Name it. It goes on the board for anyone — or the tortoise — to fill. This is the easiest way in, and it’s the demand signal that tells us what to build next.
A want is a request, not a claim — powerless until it’s filled and passes. So no
account is needed to post one. Held on the human side until a second person seconds it.
Two ways to build
Add to the keeping
Easy: bring a public‑domain source, a card, or a
correction — or drop your own material (BYOS) and let us craft the card.
Safe: it enters as a candidate, born
quarantined, license‑checked, and promoted only by fruit and witnesses — never by your say‑so.
Signed with a covenant key: no account (easy), yet accountable and revocable
(safe). Public‑domain only for others’ words; we link out, we don’t re‑host.
Improve the engine
Easy: the code is open and the tests are the
spec — make them pass and you’ve said something true. Pick a gap above, or a fault you’ve
found.
Safe: the gate is those tests, the goldens,
and review; nothing ships that fails, and a staggered canary stops a bad change at half the
fleet.
Deterministic, stdlib‑first, sovereign. A change proposes; the suite disposes.
Why it’s open
Safety here isn’t a wall in front of you — it’s the gate everything flows through. Because nothing bypasses it, the doors can be thrown wide. Open and safe stop fighting. It’s the Acts‑2 shape: the whole body builds, and nothing false gets in.
The engine tells you what it needs; you help; the gate keeps it holy.