The web app, CLI, and durable workflows share the MIT OR Apache-2.0 license. Authorized contributors can use the
Operating Neon Law Navigator workshop or the local KIND loop. Accepted contributions
retain their authors' copyright and are licensed under MIT OR Apache-2.0 without a separate CLA. We recommend checking
copied material, AI-generated output, dependency terms, and notices. Merge does not promise review or correctness.
Outside pull requests remain closed for now; write to support@neonlaw.com with a contribution inquiry and use
SECURITY.md for private vulnerability reports.
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.