Everything you have seen in these workshops — the web app, the navigator CLI, the durable workflows — lives in one
public monorepo anyone can read, run, and fork. Start by standing it up yourself with the Operating Neon Law
Navigator workshop or the local KIND loop, then file what you find. Contributions are
inbound = outbound: what you submit is licensed on the same terms the project ships under, you keep the copyright in
what you write, and there is no agreement to sign and no acceptance bot to clear.
Scope is not the gate — the local KIND loop is. A contribution may be as ambitious as the problem demands: a
sweeping refactor, a new service beside the existing ones, even replacing a subsystem. What every change must do is run
inside the local KIND cluster that cargo run --release -p cli -- dev up stands up — the loop that already runs
SurrealDB, Rauthy, Garage, Restate, and OpenObserve in one KIND dependency tier. A change that introduces a new
dependency wires it into that loop in the same pull request, with a KIND manifest beside the existing ones, so the whole
stack still comes up locally.
That rule is what keeps production portable and contribution open. In production, persistent state lives on managed
services — a hosted SurrealDB, Cloud Storage for documents — and each one has a cloud-agnostic stand-in inside KIND, so
the topology you test locally is the topology a firm deploys. And because the full stack runs on a laptop, you never
need a cloud account or someone else's cloud bill to verify your work: clone the repository, run dev up, prove the
change against the running stack, and open the pull request.