Skip to main content
At a glanceThis page anchors the verified Admin/Engine infrastructure seam and maps independently owned fleet services to their owner pages. A service named here is not, by itself, proof of its current provider-console configuration or live delivery state.

​
Infrastructure Purpose

The infrastructure layer exists to make Lucia:
It is not just deployment plumbing. It is part of the product.

​
Infrastructure map and evidence boundary

The fleet-wide topology and per-surface evidence ledger live in Current System State.

​
Admin and Engine environment model

Engine Development implements the documented intake routes. This 2026-09-10 verification re-read the Resend console (domain state) and no other provider dashboard. The provider pages separate implemented source routes from provider-console and live-delivery evidence; none should be read as a fresh webhook-target claim. Environment facts not evidenced on a record are set by the founder’s hand and unverified. This library never states an environment value. Staging is live but is not a mirror of current Development. Its Render services track stage, have automatic deploy disabled, and currently serve older commits. No current provider destination is inferred for either environment without provider-owned evidence. Current Development services still emit package/runtime version metadata 0.1.3.6. That reused value is not a release boundary. Use the full deployed Admin and Engine commit SHAs for release identity and promote exact reviewed commits rather than a version label. The former version-specific Eval Labs promotion hold is historical. Current promotion doctrine is evidence-based and commit-addressed: capture and review the intended Development behavior, name the exact source commits, promote them intentionally to stage, then verify the manual Staging deployment.

​
Verified Admin and Engine runtime identity

The Engine root identity and Admin build both expose commit-addressed evidence. Local checkout folder names and package versions are not deployment proof. Fieldwork identities on the same date: app main 692a71cd17a9189875b9bd35d5681fcb943bee68 on Cloudflare Pages (luciafieldwork.ai), API main 89b775b2796bb94b0616812e8f02ca3a7a7ca023 on Render lucia-fieldwork-api (api.luciafieldwork.ai). Development surfaces:
Marketing / waitlist surface:
Staging surfaces:
Documented Eval Labs Development target, last live-verified on 2026-07-10:
Guest-facing Lucia production entrypoints:
The legacy /lucia-lab/ path redirects to /; it is not a separate current surface.

​
Email infrastructure

Resend carries the guest-mail family (the booking magic link and, since 2026-09-09, the payment request) from the verified sending domain send.hellolucia.ai; Postmark carries the employee-facing maintenance thread only; on Development every guest mail lands in one testing inbox (LUCI-231). Use Resend, Email Services and Postmark Email Inbound for owner-scoped evidence. The marketing waitlist mail is separately owned.

​
Render publication boundary

The public Admin/Engine domains and exact deployed commit identities are the documented release evidence. Internal Render project/service identifiers, credential values, and private environment configuration are intentionally omitted from this public page. Use the provider dashboard only through an authorized operational workflow.

​
Payment truth infrastructure

The durable ownership boundary remains:
Since September the Engine runs real Stripe in test mode behind a declared STRIPE_MODE, and the payment record’s doors (send a payment link, charge the card on file, record a payment taken another way) are real Stripe actions. See Payment truth — current for the current contract and Lucia Payment Truth Foundation for the dated 2026-06-19 foundation.

​
Operating loop

Lucia is moving away from localhost-first.
Localhost should not be treated as the default proof path for integrated behavior.

​
Admin and Engine GitHub scope

The branch and deployment rules on this page cover:
They are not a complete repository list. Fieldwork App/API, Guest Agent, Eval Labs, Marketing, the Library, and private operator tooling are separately owned; see Current System State.

​
Admin and Engine branch discipline

Stage changes should be explicit and reviewed. This snapshot does not claim a currently verified GitHub branch-protection configuration. Current Development CI and deploy gate:
Integration onto dev is by literal 40-character SHA, fast-forward only, and a battery is green only at exit code 0. The Algorithm’s behaviour gate is the replay harness, not the old quality-bank diagnostic. See GitHub and Branch Discipline.

​
Infrastructure rule

Every infrastructure claim in the Canon must specify whether it is:
It must also name its evidence date and distinguish source implementation from provider configuration, live execution, and delivery proof. No pretending.

​
See also

​
Upstream / Downstream

​
Upstream

This layer is fed by:

​
Downstream

This layer affects: