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

← Operating Neon Law Navigator

Environment Matrix

Chapter 5 of 7 · Section 36 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

Deployed runtime: email, signatures, and billing

CapabilityEnvironment variablesDev / production rule
Email backendNAVIGATOR_EMAIL_BACKENDMust be sendgrid outside the harness
Outbound SendGridSENDGRID_API_KEY, SENDGRID_FROM_EMAILRequired outside the harness
SendGrid base URLSENDGRID_BASE_URLOfficial hosts only outside the harness
Inbound URL gateSENDGRID_INBOUND_SECRETRequired outside the harness
Inbound signatureSENDGRID_INBOUND_PUBLIC_KEYRequired when summary review is enabled
Attachment scannerNAVIGATOR_CLAMD_ADDRRequired in every deployed profile; private clamd only
Event webhookSENDGRID_EVENTS_SECRET, SENDGRID_EVENTS_PUBLIC_KEYRequired outside the harness
Threaded mailNAVIGATOR_PARSE_HOST, NAVIGATOR_LAWYER_NOTIFY_EMAILBoth values enable it
Summary opt-inNAVIGATOR_SUMMARY_ENABLEDEnables durable review
Summary identityNAVIGATOR_DEPLOYMENT_ID, NAVIGATOR_SUMMARY_CHANNEL_IDDurable review coordinates
Summary FirmNAVIGATOR_SUMMARY_FIRM_IDOptional; unset uses the Firm wearing the neon brand
Summary accountNAVIGATOR_SUMMARY_PROVIDER_ACCOUNTOptional; defaults to sendgrid
Summary envelopeNAVIGATOR_SUMMARY_ENVELOPE_RECIPIENTSUnset/off by default; blank values fail
SMSNAVIGATOR_SMS_NUMBER, TWILIO_AUTH_TOKEN, TWILIO_ACCOUNT_SIDOff by default; a number needs both
Voice linesNAVIGATOR_VOICE_NUMBERSOptional brand_key=+E164 pairs; omitted Brands keep their own
SMS test numbersNAVIGATOR_SMS_TEST_RECIPIENTSStaging secret: the only numbers simulated matters may text
SMS reply accountTWILIO_ACCOUNT_SIDReplies need live production egress and sender registration
Summary Gemini modelNAVIGATOR_SUMMARY_GEMINI_MODELOptional Vertex model override
Summary Gemini locationNAVIGATOR_SUMMARY_GEMINI_LOCATIONOptional Vertex location override
Summary input limitNAVIGATOR_SUMMARY_MAX_INPUT_CHARSOptional input limit
Summary output limitNAVIGATOR_SUMMARY_MAX_OUTPUT_TOKENSOptional output limit
DKIM fenceNAVIGATOR_DKIM_REQUIRE_DOMAINOptional domain pin
Lawyer-sender DKIM checknone (always on)Must pass for sender's own domain on every lawyer command/relay
Internal ops noticesSLACK_WEBHOOK_URLOptional; otherwise captured in memory
Per-Project client-view noticesSLACK_BOT_TOKENRequired outside the harness; creates private Project channels
Inbox notice FirmSLACK_MESSAGES_FIRM_IDOptional; unset uses the Firm wearing Neon
Dash0 endpointDASH0_ENDPOINTOptional staging-only integration declaration
Dash0 datasetDASH0_DATASETRequired with DASH0_ENDPOINT
Dash0 tokenDASH0_TOKENEncrypted Secret Manager input; required with DASH0_ENDPOINT
Signature providerNAVIGATOR_SIGNATURE_PROVIDERfake/docusign; unset fails boot; fake refuses production
DocuSign endpointDOCUSIGN_BASE_URLDeclares DocuSign; demo in dev, live in production
DocuSign accountDOCUSIGN_ACCOUNT_IDEnvironment-specific account
DocuSign JWT IDsDOCUSIGN_INTEGRATION_KEY, DOCUSIGN_USER_IDPreferred auth path
DocuSign JWT proofDOCUSIGN_PRIVATE_KEY, DOCUSIGN_OAUTH_BASEPreferred auth path
DocuSign static authDOCUSIGN_ACCESS_TOKENShort-lived fallback
DocuSign signerDOCUSIGN_SIGNER_EMAIL, DOCUSIGN_SIGNER_NAMERequired signer identity
DocuSign webhookDOCUSIGN_HMAC_KEY, DOCUSIGN_WEBHOOK_SECRETRequired once DOCUSIGN_BASE_URL is set
Xero tenantXERO_TENANT_ID, XERO_BASE_URLAll Xero values select real billing
Xero OAuth clientXERO_CLIENT_ID, XERO_CLIENT_SECRETOtherwise stub billing
Xero OAuth tokenXERO_TOKEN_URL, XERO_SCOPE, XERO_ACCESS_TOKENOtherwise stub billing

The signature provider is a closed enum, SignatureProviderKind: fake (the local signature loop — envelopes on disk, local sign pages, DocuSign-Connect-shaped HMAC-signed completion webhooks; dev and CI only, refuses production) or docusign (the real eSignature REST API). There is no implicit default: unset refuses to boot. An envelope on the fake provider carries one of two statuses, EnvelopeStatus: sent (anchors validated against the prepared PDF, PDF stored) or completed (every recipient signed, documents and certificate filed). There is no third state. Tests fail the loop on purpose with the third enum, Fault — send, view, or webhook — and the durable envelope keeps its last true state across every injected failure. Before anything is sent, on either provider, prepare_envelope groups the manifest's fields into per-signer, per-role tabs (SignatureFieldKind::tabs_key picks the tab type, the recipient's role picks the sign page) and refuses the send with a typed SignatureError::TabValidation when a field names no recipient, or SignatureError::AnchorValidation when the prepared PDF's text lacks the field's nlsig- anchor. Off the loop, a matter's execution reading is another closed enum, OnboardingStatus (store/src/projects.rs): pitch — no completed, Navigator-sent onboarding envelope on the matter's onboarding notation — or official — that envelope has completed a loop Navigator itself sent. It is additive to MatterLifecycle (pitch/active/closed), which it does not change, and surfaces on the matter page, through navigator project lifecycle, and in the Portal. The funnel the prospective client walks is itself a closed enum, FunnelEvent (telemetry/src/lib.rs), whose steps are enumerated with their fields in docs/observability.md — lead_captured, offer_accepted (a start-door acceptance: the offer's matter, notation, and proposed terms exist), intake_complete, review_entered, and sent — every field an identifier, never client content.

Presenter notes

NAVIGATOR_CREDENTIAL_ENVIRONMENT must exactly match dev or production outside the harness. A normal dev deployment therefore sends real email from a non-production SendGrid account and creates non-binding envelopes in DocuSign demo. Dash0 is staging-only and optional: omit DASH0_ENDPOINT to omit the dataset and token as well. Once the endpoint is declared, all three Dash0 values are required; the deployment, Secret Manager, and ship checks refuse a missing value instead of allowing the renderer to drop Dash0 silently. Xero is different today: its variables are not part of the deployment invariant, so an incomplete production Xero set still boots and selects StubBillingProvider. Treat that as an explicit capability choice, not evidence that an invoice reached the ledger.

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