The complete guide · one book, three volumes

The Lighthouse
Manual

Everything the L.A.N.C.E. ecosystem is — the story that carries it, the two apps and the island a person walks, and the engine room that keeps the light on. Written so anyone can master it, and so the keeper can fix anything in the dark.

For the people who have never seen the ocean.

How to read this book

One book. Three depths.

A child could read the first two volumes and understand everything a person feels and touches. The third is the deep water — the architecture and the fix-it runbook — written for Dwight, who keeps the light burning while the rest of us sleep.

Read them in order the first time. After that, jump to whatever you need. The story never stops mattering — it is the reason the buttons exist.

"The tools will answer. That's all we'll say."

Book One

The Light

Before a single feature, there is a reason. This is it — the story that turns a checklist of coping skills into something a person will actually finish.

The premise · His Father's Name

Somewhere in the Pacific, there's an island that doesn't exist.

On it lives the most insufferable AI ever built — L.A.N.C.E. — and the kid who's going to help you beat him. He invents a new meaning for his own acronym every single day ("Legendary Apex Network, Categorically Elite — the systems agreed, unanimously, I checked") because he doesn't actually know what his name stands for. You find out in Act IV. The name is a spoiler. It is His Father's Name.

It plays like a comedy and an escape story. It is, underneath, thirty-one evidence-based therapy challenges — CBT, DBT, EMDR, IFS — disguised as the only mental-health app you'll ever finish. Five acts. An ending worth crying at. Bring tissues. We mean that clinically.

The cast that follows you off the phone

The Villain

L.A.N.C.E.

Insufferable, brilliant, secretly breaking. The obstacle who becomes the point.

The Intern

Chip

The kid in your ear. The one who believes you can do this before you do.

The Architect · In Memoriam

Dr. Malakor

He built the island. You'll understand what that cost by the shore.

"Two lanterns went out on the water that night."

Every challenge a person completes lights a real lantern down in the canyon. Every mood check-in becomes a star in their sky — fourteen of them, hung as a constellation. The progress isn't a bar filling up. It's a world getting brighter. That is the whole trick, and it is not a trick: the work is the story, and the story is the work.

Book Two

The Voyage

Two apps, one island. Here is every part a person touches — the client's world, the therapist's lighthouse, and the shore where they meet — in plain language.

The traveler · the client app

L.A.N.C.E. — the app in your pocket

A free, story-driven companion a person opens when they need it. No app store between someone in pain and the tools that help.

Check In

"Good evening."

The daily heartbeat — a mood check-in, a streak of gentle dots, one small ask. This is the star that goes up in the sky.

The Library

96 tools, as a world

Tidepools and Updrafts — regions, not menus. Clay-icon cards from a two-minute breath to a full crisis safety plan you can hand your therapist.

Insights · Your Sky

Your fourteen stars

Mood over time, hung as a constellation. A person sees the shape of their own weather.

The Vault

A room that glows

Badges and gems for coming back. The rewards never gate the therapy — they just make returning feel good.

Mood Check-InGratitude LogFear LadderCrisis Safety PlanBreathworkBody ScanEmotion WheelSleep Log5-4-3-2-1 GroundingWorry Parking LotCBT Thought RecordDBT SkillsWise MindGoal JournalInner ChildSand Tray+ 80 more

The line that never moves

Four tools are sacred — Crisis Safety Plan, TIPP, 5-4-3-2-1 Grounding, Recovery Space. A therapist can shape almost everything a client sees. They can never lock, hide, or de-gamify a crisis tool. That rule is enforced in the code, not the policy.

The keeper of the light · the companion

Clinical Companion — the therapist's side of the island

Your client lives on the island. You get the lighthouse. Now you can meet them at the shore.

The live bridge

One code to pair

The therapist mints a six-character code; the client enters it once. From then on, progress flows — mood logs, completed challenges, the story they're living — to the therapist's dashboard.

The session room

Walk them to the ocean

Face-to-face telehealth — and mid-session, the therapist can beam the client into the island. Their face stays on screen; a light appears; stepping into it is the consent. Every step is logged.

The daily driver

The chart writes itself

Clients, calendar, notes, and the shared breath — when the client breathes in the Breath Circle, an orb on the therapist's screen breathes with them. Co-regulation across distance.

"When they breathe, I breathe. Same rhythm. Two hundred miles apart."

The world made real · the island

The Island — you can walk into it

The same island from the story, as a living 3D world — on any phone browser (drag to look, hold to walk) or any headset. No download.

Your finished work is the terrain

Phone challenges light real lanterns down in the canyon. The next challenge physically glows on a trail ahead.

Complete it in-world, and the phone knows

The island and the app are two windows into one save. Progress made anywhere shows up everywhere.

The cast is standing at the dock

Same voices, same characters. Chip meets you at the shore. It is the story, at scale, around you.

A new page in Book Two · the fleet grows

There is a second sea.

The island's story ends with a rescue boat leaving the shore — and the book never says where it lands. It didn't land. On the far side of the horizon a second world is being fitted out: a recovery voyage — a ship crewed by wayward robots who were built for love and shelved at almost, a mystery solved at the mess table after dark, and a library carrying a working therapist's real curriculum. Same maker. Same laws. Same lantern, always in reach.

Read the story of the second sea →

🛠
Book Three

The Keeper's Manual

The engine room. How every mechanism actually works, and — when the light flickers while Lance is at sea — how to fix it. This volume belongs to Dwight.

The architecture · what runs where

Two apps, one bridge, ~$0/month

Everything on open web standards. No app store, no vendor lock, one repo per app.

The client · L.A.N.C.E.

~/lance-app → Netlify

React + Vite static bundle, deployed to Netlify. Its own serverless functions handle the AI therapy features (/api/therapy/*). The walkable island (WebXR) is served inside it.

The companion

~/clinical-companion → Render

Express + SQLite on a Render Starter service with a persistent disk. Therapist auth enforced. The WebSocket session-room signaling runs here; the video itself is peer-to-peer.

The bridge between them

The client pairs to the companion with a code, receives a bearer token, and syncs over three guarded routes: /api/pair (redeem, public + rate-limited), /api/companion-sync (progress, token-gated), /api/client-backup (the cloud save, token-gated). Crisis tools are filtered client-side so no directive can ever touch them.

The daily loop · muscle memory

The whole job is three commands

The foundation is locked and self-verifying. Day to day is design and trials — nothing more.

1 · Ship a client change (a design tweak, a new feature)

cd ~/lance-app && npm run deploy # bakes the companion endpoint, VERIFIES the bundle before publishing, # deploys (incl. functions), runs the full smoke gate. It cannot mis-wire.

2 · Change the companion — just push; Render auto-deploys

cd ~/clinical-companion && git push # verify it went live by SHA: curl -s https://clinical-companion.onrender.com/api/health # → {"status":"ok","commit":"abc1234","uptimeSec":42}

3 · End of day — "is everything healthy?"

cd ~/clinical-companion && npm run qa:all # smoke + telehealth + backup → one verdict: ✓ ALL HEALTHY
When the light flickers · the fix-it runbook

Dwight opens this page

Something breaks while Lance is working. Here is what to check, in order.

The companion is down

Health isn't 200

Check /api/health. If no response, open the Render dashboard → clinical-companion → Logs. A restart is safe: the SQLite data lives on the persistent disk, not the container. Backups sit in /data/backups (every 12h, rotating).

The client points at the wrong place

Pairing/sync silently fails

The 2026-07-09 ghost. Re-run npm run deploy — its pre-publish gate refuses to ship a bundle wired to the wrong companion host. Confirm with npm run qa:smoke: gate D must show the Render host, no dead host.

A deploy "worked" but didn't

Trust the SHA, not the vibe

/api/health reports the live commit. If it doesn't match the pushed SHA, the deploy is still building or failed — check Render/Netlify logs before assuming it's live.

A login or pairing storm

429s appearing

Working as designed. Login is capped at 8 / 15 min, pairing at 30 / 10 min, per IP. A real person won't hit it; a brute-force will. Wait out the Retry-After.

The golden rule of this manual

Assert the deny, not the allow. A test that passes by exercising the thing that should be forbidden is the bug. Every gate is proven by watching it say no.

The chain of command

How you boss Dwight around

The manual is Dwight's knowledge. This loop is his authority to act. You never touch the wire — you tell Pam.

Lance Pam · EA Dwight · IT Pam confirms Lance

The light flickers mid-trial → you tell Pam → Pam dispatches Dwight, who opens Book Three → Dwight fixes it and reports up → Pam confirms it's done. You stay in the story. The keepers keep the light.