Neon LawCall +1 510 800 2090
  • Navigator
  • Notations
  • Legal Aid
  • Sign in

← Contributing to Neon Law Navigator

Improve the Corpus

Chapter 2 of 5 · Section 2 of 11

Sections

1. Intro

  • 1. Five ways to contribute

2. Improve the Corpus

  • 2. Contribute to the product repository
  • 3. View content images locally
  • 4. Publish presentation images
  • 5. Ship through GitOps
  • 6. Work with the store
  • 7. Add a fillable government PDF

3. Share What You Learn

  • 8. Tell us what you learned
  • 9. Join a presentation

4. Put It to Work

  • 10. Use Neon Law Navigator

5. Wrap Up

  • 11. Why this matters

Contribute to the product repository

The whole stack is written in Rust in one monorepo, licensed MIT OR Apache-2.0. Outside pull requests are closed; authorized lawyers contribute inside the firm. The most useful corpus contributions are specific ones:

  • Add a missing legal template. Add a government PDF form. Improve a field map. Add a test that locks a workflow to the law it implements.

  • Maintain a brand catalog. Each public brand keeps its English home and services copy in neon/locales/en/<brand-key>; the registered catalogs include neon/ and delete-your-data/. A new catalog must be added through the brand registry with covering tests and attorney review for public legal copy.

Presenter notes

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 hudson -- dev up stands up — the loop that already runs SurrealDB, Rauthy, SeaweedFS, 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: in any clone, run dev up and prove the change against the running stack. An authorized lawyer then opens the pull request.

View all slidesOpen display
← PreviousNext →
Neon Law
  • X opens in a new tab
  • LinkedIn opens in a new tab
  • YouTube opens in a new tab
  • API
  • Blog
  • Contact
  • Design
  • Glossary
  • Navigator
  • Notations
  • Presentations
  • Privacy
  • Team opens in a new tab
  • Terms
  • Testimonials
  • contact@neonlaw.com
  • +1 510 800 2090
  • California
    1515 20th StreetBakersfield, CA 93301
  • Nevada
    5150 Mae Anne AveSte 405-9002Reno, NV 89523
  • New York
    12 E 49th St18th FloorNew York, NY 10017
  • Washington
    1111 Main StSTE 201EVancouver, WA 98660
  • Justice Technology AssociationMission-Aligned Partner opens in a new tab
  • Proud member of Greater Vancouver ChamberGVC opens in a new tab

Attorney advertisement. Nothing here is legal advice without a signed retainer for an active project. Past results do not guarantee future outcomes.

Everyone deserves access to justice.Made with ❤️ in 🗽.

© 2026 Guieb & Shook PC

Powered by neon-law/navigator opens in a new tab26.11.17-rc.1GitHub stars 6