CiteBible is Built — the Free Door is Open

🔑 Morning ignition — the ~3-minute switch that turns on money

Everything below is a Sam-console action — no code, no deploy from me. Do step 1 to make the Pro upgrade actually charge; do step 2 because a credential was exposed overnight; step 3 is when-ready cleanup.

1. 1

   Register CiteBible in Core — this unlocks the Pro checkout Sam · unlocks money

   Core (core.oll.am) keeps an allow-list of products that may run its magic-link + checkout flow. CiteBible isn't on it yet, so a Pro upgrade click has nowhere to land. Add one env var and redeploy Core:

   Coolify → oll-core app → Environment → PRODUCT_VERIFY_BASE_CITEBIBLE = https://citebible.oll.am → Redeploy

   No new Stripe price needed. The plan is the existing platform Pro — STRIPE_PRO_PRICE_ID = price_1TmvlJI5o19D7tAoP1cJgN51 (a monthly subscription, already set on Core). After this redeploy, the upgrade → Core checkout → oll_pro flow works for CiteBible.

2. 2

   Rotate the TWO secrets exposed tonight Sam · security

   During tonight's debugging two credentials were pasted into chat. Treat both as burned. Neither is optional — the Neon password also guards oll_core, and the service token is the one required secret gating oll-memory.

   a) Neon neondb_owner password — rotate, then update the connection string on both apps that use it:

   Neon console → roles → neondb_owner → reset password → update DATABASE_URL on: · oll-core app (guards oll_core) · oll-memory app (guards oll_memory) → redeploy both

   b) OLL_MEMORY_SERVICE_TOKEN — the shared service token between the CiteBible frontend and oll-memory; regenerate and set the same new value on both:

   Generate a new random token → → set OLL_MEMORY_SERVICE_TOKEN (identical value) on: · oll-memory app (verifies it) · CiteBible frontend app (sends it) → redeploy both
3. 3

   When ready — graduate the branches & open the front door Optional today

   CiteBible runs as preview deploys off feat branches (unmerged, per the frozen-main guardrail). Nothing here is required to charge — it's the follow-through:

   • Review + merge the frontend branch feat/citebible-one-box and the corpus branch feat/bible-verse-reingest to main when you've clicked through them — merging publishes the SEO front door (the 26 /for/{situation} pages + hub) to the public domain.
   • Review the Pro-generation change (the fail-closed paywall-on-CREATE feature) before it goes to prod.
   • Then distribution — fire the launch burst using the build-in-public share kit (drafted tonight, not yet posted), so the free door actually gets traffic.

What's verified live — and what's only built

Honest rung per line. "Verified live" = I typed it against the deployed URL tonight. "Built" = code exists and passes locally, but no live proof of the paid outcome yet.

The money model — paywall on CREATE, not SEARCH

The whole design turns on one honest line: retrieval is free forever, generation is Pro. Searching scripture for your situation costs nothing and needs no login — that's the SEO front door and the honest gift. Asking the engine to write a grounded reflection from those verses is the paid act, gated behind the existing platform Pro. The paywall sits on the Create button, never on Search.

The night's arc — from three broken wires to live end-to-end

The honest story: CiteBible didn't come up on the first try. Three separate integration faults each looked like "the corpus is empty" but had distinct root causes. Naming them teaches the shape of a cross-service bug — the symptom is always downstream of the break.

With all three wires corrected, the chain came up green end-to-end: CiteBible frontend → oll-memory (retrieval) → oll-ollama (nomic embeddings) + Neon oll_memory (verse corpus) → oll-model (step-back theme rewrite). The theme rewrite is what turns "grief" into the retrieval themes you saw — a step-back query expansion through the frozen Model gateway.

The big one — retrieval that's actually pastoral

Bringing the chain up only got a verse back. The harder, more valuable work was making the right verse come back — the one a person in that situation actually needs, not the one that shares a keyword. That's the retrieval-quality tuning deployed tonight (9ed1d40).

Three changes, all inside oll-memory, all live:

• Prefer verse-level. A whole-chapter hit and a single-verse hit no longer compete as equals — the ranking prefers the verse, so the answer points at a line you can hold, not a page you have to scan.
• Vector floor drops keyword-only noise. Matches that only share a word — but sit far away in meaning — are cut below a similarity floor, so "anxiety" stops surfacing verses that merely contain the word "afraid" in an unrelated story.
• Chapters enriched with their best_verse. When a chapter does rank, it carries the single strongest verse inside it, so the result still lands on something specific.

The live topology

All on the Hetzner VPS (Coolify), shared coolify Docker network. Min-env baked as defaults — the only secrets needed are OLL_MEMORY_SERVICE_TOKEN and DATABASE_URL. This mirrors the platform pattern: a thin product frontend over a reusable Core/Model/Memory backend, integrating over HTTP only.

What the night shipped — all nine board tasks done

The overnight board is fully cleared. Honest rung on each line.

Read next

• CiteBible — build-in-public share kit Draft — the launch copy for the distribution push (step 3), not yet posted.
• CiteBible — branding & design study — the product's visual identity + the Still Room.
• Fixing pastoral retrieval — rewrite-first, re-ingest as polish — how retrieval quality gets sharpened (the plan behind tonight's corpus work).
• Verticalize the engine — corpus candidates — CiteBible is the first proof that "one corpus becomes a product"; the others in the pipeline.
• Verticalize the engine — research — the thesis: the memory/retrieval engine, pointed at a corpus, is a distributable product.
• CiteBible — Coolify preview runbook — the deploy mechanics for the feat-branch previews.
• The platform architecture — where CiteBible sits atop oll-memory + Core + Model (the corrected diagram).