Everything you have seen in these workshops — the web app, the navigator CLI, the durable workflows — lives in one
private monorepo. Authorized contributors can use the Operating Neon Law Navigator
workshop or the local KIND loop, then write to contact@neonlaw.org with what they find. Production use needs a
commercial licence from Neon Law IP LLC. A contribution that lands in the repository assigns to Neon Law IP LLC — all
right, title, and interest, including every copyright in it — under the contributor licence agreement. Firm authors
signed that before their first commit; an outside author would sign the same before a merge, and outside merges are
closed for now. The grant out is BUSL-1.1, the same terms the rest of the tree ships under for authorized source
recipients.
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. 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: with repository access, run dev up and prove the change against the
running stack. An authorized lawyer then opens the pull request.