← product

Lighthouse — reconnection narratives for alienated parents

Status: vision / near-future (not built) · Owner: Sandon · Created: 2026-07-05 · Channel partner: Ryan Thomas (parental-alienation coach) — white-label

A product surface for alienated parents who want to reconnect with their children — using the parent's own journaling + Odessa to assemble narratives that (a) help the parent heal and positively reframe, and (b) become a record of love the child can receive on their own terms, building toward a brighter future. Delivered through a coach's facilitated practice, not self-serve.

The name is the product spec: a lighthouse doesn't chase ships. It stays lit so a ship can find its way back on its own course.

Why now — it composes from surfaces we already have

Lighthouse is a recombination, not a greenfield build. That's what makes it cheap to prototype and defensible:

Existing surfaceRole in Lighthouse
HiveJournal journalsthe raw material — the parent's writing, memories, regret, hope
Odessathe reframe engine — turns painful raw material into narrative the parent can bear to look at and that points forward (dead-on the fiction→real-change thesis)
Lovio / FutureSend vaultdelivery to the child — a delayed, consent-based vault (a birthday, at 18, whenever they reach for it), NOT a push
Printed journalsthe tangible keepsake — a physical object survives, can be handed over, isn't a notification; matters enormously in estrangement
Channel-partner / coaching-seat infra (the DreamPro / John Rowley pattern)lets Ryan Thomas brand + deliver it as his own

The genuinely new work is framing, safeguarding, and a narrative-assembly flow — not new infrastructure.

The load-bearing decision: lighthouse, not push

The child-facing output is a vault the child chooses to open, not a narrative delivered at them now. This single reframe resolves most of the ethical hazard:

  • It changes the parent's posture from "receive my version of events" — which an estranged child (especially one estranged for good reason) experiences as pressure or gaslighting — to "I'll be here, and here's the record of my love, on your terms."
  • It's emotionally truer to what a genuinely wronged parent wants to say: I never stopped.
  • It keeps the parent as the primary user of the reframe (their own healing), with the child as an eventual, consenting recipient — never a target.

So the two halves are asymmetric:

  • Parent-facing (active): journaling → Odessa reframe → a forward-looking narrative + printed keepsake. This is the healing/processing product. Runs now.
  • Child-facing (latent): a FutureSend/Lovio vault the child can open when they're ready. Time- or event-gated. Nothing is delivered without a consent path.

Distribution rule: never before 18 (the bright line)

Nothing child-facing is ever distributed before the child turns 18. After that, the vault opens by one of two triggers: age of majority (18) or the child reaching out — whichever comes first, but never earlier than 18. This single rule collapses most of the legal/ethical surface:

  • No minor ever receives anything → COPPA/GDPR-K child-delivery, custody-of-a-minor, and pushing-at-a-protected-child concerns fall away.
  • The recipient is always either a consenting adult (18+) or the person who initiated — the two safest possible states.

At/after-18 mechanism — DECIDED: C, hybrid (2026-07-05):

Available at 18; one gentle, one-time notification attempt if a contact path exists, otherwise it waits for the child to reach out and claim it. Combines a reliable landing when possible with a zero-pressure lighthouse when not. (Rejected: A auto-release — needs contact info the alienated parent usually lacks and is still a push; B child-initiated-only — purest but the child may never learn the vault exists.)

The discovery problem (now the crux, since C leans on child-initiated claim whenever no contact path exists): a lighthouse only works if the ship can see it. An estranged adult child needs a way to find the vault. Recommended default (open, pending Ryan): a claim/lookup flow — the adult child searches by the parent's name / their own name / a code the parent registered, plus Ryan's practice as a known human intake point (a natural, trusted "someone is looking for you" front door). Solving discovery is what turns the child-initiated half of C from theoretical into real.

Legacy case (a quiet strength): if the parent dies before the child turns 18, the vault should survive them — a lighthouse that outlives its keeper. This is poignant, on-brand, and an argument for the vault living independently of the parent's active account.

Safeguarding architecture — the hazard we must design around

"Parental alienation" is one of the most weaponized concepts in family law. A tool "for alienated parents to reconnect" will attract two populations:

  1. Genuinely wronged parents (the intended, sympathetic user).
  2. Parents estranged because they were abusive or dangerous, seeking a channel back to a child who is protected from them.

If the product ever becomes a vector for group 2 to reach a child, that is catastrophic — for the child first, and for the brand/founder second. Defenses, in priority order:

  1. Not direct-to-consumer self-serve. Delivered through Ryan's facilitated practice — a screening, judgment-exercising human in the loop. Practitioner-gating is a feature, not a limitation.
  2. Lighthouse-vault model (above) — the child opens on their terms; the product does not push contact.
  3. No facilitation of court-prohibited contact. Explicit in terms; the product must never be a mechanism to circumvent a no-contact / custody order.
  4. Structural, not just human, safeguards. ⚠️ Nuance: Ryan and his wife are coaches, not licensed clinicians — not mandated reporters, not licensed risk-screeners. So the coach gate provides a human container, but the product's own structural safeguards (vault-not-push, terms, no self-serve, no contact facilitation) have to carry more of the safety load than they would with a clinician gate. Don't overstate the clinical rigor of the gate.

The Ryan Thomas partnership

  • Ryan Thomas — parental-alienation coach (ryanthomasinternational.com), runs group sessions for alienated parents. Would brand Lighthouse as his own (white-label channel partner).
  • His wife co-delivers emotional coaching to the same clients — a natural two-role model (alienation coaching + emotional coaching) that maps onto the existing swappable coaching-seat infra (per-client seat with a swappable AI/human holder + supervisor).
  • Structure = the John Rowley / DreamPro model: channel partner rebrands, recruits/serves clients, earns a recurring override on the existing Stripe Connect payout rails. See DREAMPRO_COACHING_SYSTEM.md
  • Children's data — COPPA / GDPR-K special handling; a child recipient may be a minor. Minimize child data; the parent is the account holder.
  • Custody / no-contact orders — the product must not facilitate contact a court has prohibited. Terms + the coach gate handle most of this.
  • Discoverability — anything a parent writes could be subpoenaed in custody litigation; it cuts both ways. Be transparent it's a reflective/creative tool, not a legal strategy.
  • No outcome claims — like the DreamPro wellness-lane guardrail: coaching, not therapy or legal advice; make no reunification-outcome claims.

Not therapy — coaching guardrail

Because the practitioners are coaches (not clinicians), the boundary must be sharper than DreamPro's, not softer: Lighthouse is a reflective + creative tool administered within a coaching practice. No diagnosis, no treatment claims, no legal advice. Crisis/abuse-disclosure paths route to appropriate external resources, not to the product.

Brand / voice

  • Lighthouse metaphor: a beacon, freely followed — a steady light, not a summons (a lighthouse guides ships that choose to follow it).
  • Per brand voice (ETHOS.md): no coercion / consumption metaphors; transformation and becoming. The child is found, not fetched.

Rough phasing

  1. Parent-facing prototype — journaling → Odessa reframe → forward-looking narrative + printed keepsake. Ships value to the parent alone, zero child-facing risk. Pilot inside Ryan's group sessions. (Built — engine + /dashboard/lighthouse tool + save/print keepsake; plus a public signup-funnel landing at /lighthouse with Ryan unnamed for now. See INDEX.)
  2. Lighthouse vault — FutureSend/Lovio delayed, consent-gated child-facing delivery. Only after 1 is validated and the safeguarding + legal terms are locked.
  3. White-label channel — Ryan-branded instance on the coaching-seat + channel-override rails (two-role: alienation coach + emotional coach).

Open questions

  • Ryan's appetite for white-label + the exact two-role split with his wife's emotional-coaching track.
  • Settled: never distribute before 18; at/after-18 mechanism = C (hybrid). Open piece is now discovery — the claim/lookup + Ryan-as-intake flow that lets an estranged adult child actually find the vault (recommended default noted, pending Ryan).
  • How much of the "reframe" is fiction (Odessa-style, names changed) vs. a lightly-edited true record — the more fictionalized, the safer for the parent's processing but the more it risks feeling like a sanitized history if ever child-facing.
  • Jurisdiction scope for the legal review (Ryan is international — UK/US/other).
  • Whether the printed-journal artifact is parent-only or ever child-addressed.
LIGHTHOUSE — Docs | HiveJournal