The published Terms directly contradicted two locked safety decisions and the
shipping app copy, and the in-app Privacy Policy link 404'd. Both are legal
exposure under CA SB 243 (companion chatbots) and the AI-companion litigation.
Terms (§1, §11):
- Add an explicit "you must be 18 or older" eligibility statement. The old §11
permitted "Children 13 and over" independently and under-13 via family
accounts — the exact minor path the app's age gate forbids and the litigation
epicenter targets.
- Replace §11 "Children and Family Accounts" with an honest "Safety Features"
section. Removes the Hard Bell auto-notify block ("emergency services and
trusted contacts are notified first", "cannot be changed") and the
mandatory-reporting clause ("emergency services or relevant authorities may
be contacted", "cannot opt out") — both promised an automatic escalation the
product does not perform. New copy matches the app: Neuron shows you 988 and
how to reach a contact you chose; it never contacts anyone on your behalf;
there is no automatic escalation.
Privacy Policy (new):
- Add src/privacy.el + register it in main.el (generation, /legal/privacy route,
state pointer, sitemap). Fixes the in-app link, which pointed at
/legal/privacy (404 — no route, no doc existed).
- Ported from docs/legal/privacy-policy-companion-DRAFT.md (2026-07-14):
local-first, 18+, and never-auto-contact stated verbatim from the locked draft.
- Wire privacy.html through Dockerfile.stage / Dockerfile / deploy.yaml; add the
secondary /legal/privacy route to server.el for parity.
PENDING ATTORNEY (Daniel) SIGN-OFF before merge/publish. Bracketed legal
decisions (governing law, effective date, retention periods) left for counsel.
Hand-cuts the marketing surface from Next.js to a native El HTTP server.
The El landing reads the pre-rendered index.html (output of the existing
component pipeline at src/index.html) and serves it directly. ~150
lines of El at server.el; 130 KB binary; no Node, no build step at
serve-time, no runtime JS for the marketing pages.
What's here:
- server.el: dispatcher with /, /health, /api/founding-count, /assets/*,
/brand/*, 404 JSON for everything else. Routes go through fs_read
against LANDING_ROOT (default /srv/landing in the container, ./src
locally).
- Dockerfile: two-stage build for linux/amd64 (Cloud Run target).
Stage 1 — debian:bookworm-slim with build-essential + libcurl-dev,
compiles the binary against el_runtime.c. Stage 2 — slim runtime
image with libcurl4 + ca-certificates, drops the binary at
/usr/local/bin/landing, copies src/index.html and src/assets/ into
/srv/landing/. Uses -rdynamic so the runtime's dlsym(RTLD_DEFAULT,
handler_name) can find handle_request inside the executable on
glibc — macOS exposes executable symbols by default, Linux does
not. Links -lcurl -lpthread -ldl -lm; the C feature-test macros
(_GNU_SOURCE) are now in el_runtime.c itself.
- build.sh: stages the foundation El runtime into ./runtime/, runs
elc to regenerate server.c, builds the docker image. --tag and
--push flags. Push targets us-central1-docker.pkg.dev/neuron-785695/
neuron-marketing/marketing for the Cloud Run flip (still manual).
- .gitignore: runtime/, /server.c, build/ — all build artifacts.
The path here was non-trivial. The original goal was to compile the
full 4325-line landing-combined.el end-to-end; that OOM'd at 8.7 GB
under the always-allocate-fresh el_list_append (the workaround for an
aliasing bug in cg_if_stmt). The runtime ARC scaffolding committed
earlier today got the compile down to 3.5 GB peak in 0.26s, but the
landing-combined still has pre-existing source bugs (http_serve(3001)
arity, neuron_origin bare expression statement) that block the build.
The structurally cleaner path was to render the HTML once, offline, and
serve the static output — which is what this server.el does. The
landing-combined.el can be revisited when those source bugs are fixed;
this server.el is the canonical production surface in the meantime.
Did not commit ./runtime/ (gitignored, staged from foundation by
build.sh on each build), ./server.c (generated by elc from server.el),
or ./build/ (build artifacts). The repo carries the source of truth
only.
will.anderson
Will Anderson