Skip to main content
Cloudflare participates in several independently owned HelloLucia surfaces. Public route behavior can be verified without claiming that the Cloudflare dashboard, DNS records, Access policies, Pages project settings, or edge rules were inspected.

​
Verified Admin and Engine route boundary

Read on 2026-09-10: The live identity and HTTP evidence prove those route outcomes for the verification date. They do not prove the exact DNS record values, Cloudflare zone ownership, Access policy rules, or provider-side configuration.

​
Separately owned Cloudflare surfaces

  • Lucia Fieldwork App deploys from main to Cloudflare Pages. The app’s own agent contract names the production host as Cloudflare Pages (GitHub-backed, npm run build, output dist/), luciafieldwork.ai answered 200 on 2026-09-10, and no Fieldwork site exists on Netlify. Two September Fieldwork comments and one internal skill said Netlify; that was wrong, and Main ruled on HLLC-41 (2026-09-10) that source wins. Served bundle at main 692a71cd17a9189875b9bd35d5681fcb943bee68 was verified by the Fieldwork Tester on 2026-09-10 (FILD-164).
  • The legacy docs host redirects home. docs.hellolucia.ai answers 301 to https://helloluciallc.com/ through Cloudflare since 2026-08-15 (Legacy docs redirect home, HLLC-24). It is retired, not live.
  • Lucia Marketing owns the public marketing/waitlist source and its Cloudflare Pages workflow. That runtime and provider project were not reverified on 2026-09-10.
  • Other fleet domains and deployments retain their own providers and evidence.
Do not turn Cloudflare’s role on one surface into a fleet-wide hosting or security claim. Use Domains and Live Routing for the full route matrix and Current System State for ownership.

​
Provider-configuration boundary

Not claimed as current on this page:
  • DNS record types, targets, proxy modes, TTLs, or zone settings;
  • Cloudflare Access applications, policies, identities, or bypasses;
  • Pages project names, branch settings, build settings, or deployed commits;
  • WAF, redirect, transform, cache, or edge-log configuration; and
  • credentials, account identifiers, or private provider project identifiers.
Each requires a fresh authorized provider read plus route/deployment evidence before publication.

​
Local-development doctrine

Public environment routes reduce reliance on localhost and ad hoc tunnels for integrated proof. Localhost remains useful for isolated debugging. Neither a public hostname nor a local tunnel proves authentication, provider routing, deployment identity, or application behavior without the matching evidence.

​
See also