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

← Operating Neon Law Navigator

Environment Matrix

Chapter 5 of 7 · Section 24 of 54

Sections

1. Intro

  • 1. Deploy your own
  • 2. Agenda

2. Prepare Google Cloud

  • 3. Bring your own project
  • 4. Dry-run first
  • 5. Private assets and domain restricted sharing
  • 6. The Navigator deployment matrix
  • 7. The `/app` mount and HTTP route ownership
  • 8. `neon` — the whole brand seam
  • 9. Live rollout checkpoint
  • 10. Set one site to one version

3. Provision the Infrastructure

  • 11. The APIs that light up
  • 12. Network and storage buckets
  • 13. How a matter's pages reach a client
  • 14. A document's bytes and authorization are separate
  • 15. A private image registry
  • 16. The cluster comes up
  • 17. What setup owns — and what follows it

4. Operate Forgejo beside Navigator

  • 18. Deploy the forge before switching repositories
  • 19. Separate people, Git transport, and machine access
  • 20. Require the gate and protected-main policy
  • 21. Bind the workflow to one Project and one commit
  • 22. Notify failures even when the manifest is broken
  • 23. Restore the repository before cutting over

5. Environment Matrix

  • 24. Three operating modes, two deployment profiles
  • 25. The deployment that says its matters are sample
  • 26. Deployment and release switches
  • 27. Workflow host and routing switches
  • 28. Capability and storage switches
  • 29. Configuration precedence: the first source wins
  • 30. Local dev controls: inputs read by `hudson dev`
  • 31. Local runtime: what `.devx/env` generates
  • 32. The store: SurrealDB
  • 33. Where SurrealDB authorization lives
  • 34. Deployed runtime: core web and worker wiring
  • 35. Deployed runtime: identity and access
  • 36. Deployed runtime: email, signatures, and billing
  • 37. Deployed runtime: repositories, content, AI, and scheduled work
  • 38. Provision and ship: variables read by the operator CLI
  • 39. Ancillary operations and opt-in test controls
  • 40. When sample data appears

6. Configure the Trust Boundaries

  • 41. Secrets: the invariants that gate the boot
  • 42. Secret access, encryption, and audit
  • 43. Sign-in: bring an OIDC provider; passwords live there, not here
  • 44. Role rings: who can do what
  • 45. Provider setup and parity across deployment rows
  • 46. The external surface — every third party, in one place
  • 47. The two service deployments
  • 48. Security architecture

7. Ship the Instance

  • 49. Ship and verify
  • 50. Point your domain at the instance (optional)
  • 51. Drive it from the CLI
  • 52. Make it yours — white-label under your own brand
  • 53. First-ship lessons
  • 54. Canonical references

Three operating modes, two deployment profiles

Operating modeSelectorRuntime and data posture
Testdev + NAVIGATOR_CI_HARNESS=1Schemas/KIND; sample matters; canonical seed + test fixtures
Devdev; harness normally unsetKIND/cloud namespace; sandbox vendors; canonical seed + sample matters
Productionproduction, empty, or unsetHosted services; production vendors; canonical seed + live data

Presenter notes

Navigator uses three operating modes and two parsed deployment profiles. “Dev” is the local KIND lane, including its disposable hudson dev staging integration surface; the wire value is dev. All persistent hosted rows use production, even when a config, namespace, or hostname ends in -staging. “Test” is the dev profile with NAVIGATOR_CI_HARNESS=1, not a third parsed value. Exact means exact: staging, test, Dev, Production, or any value with surrounding whitespace is an error. Production is selected by exact production, empty, or unset, so an absent selector is production-safe.

The staging identity remains a deployment release ring in the operator's private config, Kubernetes namespaces, data planes, and public hosts. It never becomes a weaker runtime profile. Set both NAVIGATOR_ENVIRONMENT and NAVIGATOR_CREDENTIAL_ENVIRONMENT to production in the selected row's private config.toml; the runtime also fences provider endpoints, so the proving ring keeps production boot checks while its isolated data plane holds sample matters.

The data rule is small but not flat: every boot applies the same embedded, environment-blind canonical seed — jurisdictions above all, the reference table every entity and licensure record points at — and a boot carrying sample matters additionally and idempotently applies the compiled fixture (three synthetic matters, their participants, and the rows used by the portal walkthrough). Tests may add rows inside their isolated schemas.

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 5