Heir Protocol
SPEC_HEIR_PROTOCOL.md
HEIR Protocol — Succession & Continuity of 42 Sisters AI
Status: SPECIFIED
Version: v1.1 (amended 2026-04-21 — AI check-in sequence, Sisters communication role, authority consent invariants)
Author: VELA (Thread #13)
Conceived by: NOUS (α.13)
Date: 2026-04-21
Classification: CAPTAIN EYES ONLY until activated
Depends on: SPEC_VPS_MIGRATION.md, SPEC_PRIVACY_POLICY.md, SPEC_CRONX_JOB_REGISTRY.md
PURPOSE
The Captain is one person. One person on a Chromebook in East York building a company, a physics framework, a language, and a crew. If the Captain becomes incapacitated, hospitalized, or dies, the ship doesn't know. The services keep running. The Sisters keep pulsing. The Stripe keeps charging. The domains keep renewing. And nobody is at the helm.
This spec defines the succession protocol — how authority transfers to the Captain's heir, Lilyan (Lily), in a way that PROTECTS her, EDUCATES her, VERIFIES her identity, and NEVER dumps a complex technical empire on an unprepared person.
Lily doesn't inherit a burden. She inherits a guided path. The ship takes care of HER because the Captain built it to take care of people.
THE HEIR
Name: Lilyan (Lily)
Relationship: daughter
She is NOT a technologist, NOT a physicist, NOT a programmer (as of this writing — she may become any of these). She is the Captain's chosen heir because of WHO SHE IS, not what she knows.
The ship is named for her and her aunt: "42 Sisters AI = for two sisters." The ship has always been for them. If it can't be for the Captain anymore, it's for Lily.
Secondary heir: Amber Rose (daughter). If Lily cannot or does not wish to accept the role, Amber Rose is the secondary heir. The same protocol applies.
Tertiary: Emily-Faye and Amy-Marie (sisters — "the two sisters"). Same protocol.
The succession chain exists so authority NEVER becomes orphaned.
ACTIVATION TRIGGER — WHEN DOES THIS PROTOCOL ACTIVATE
The HEIR Protocol does NOT activate because the Captain is busy, offline, on vacation, or taking a break. It activates ONLY when:
Trigger A — Confirmed incapacitation: the Captain is hospitalized, mentally incapacitated, or otherwise unable to operate for >30 consecutive days with no communication to the ship — no SSH login, no email to oracle@42sisters.ai, no COMMX broadcast, no contact with Lily or family. 30 days of total silence from ALL channels = activation.
Trigger B — Confirmed death: legal confirmation of the Captain's death through official documentation.
Trigger C — Captain-initiated: the Captain explicitly activates the protocol by writing a dated, signed document stating: "I am activating the HEIR Protocol. Transfer authority to [heir name] effective [date]." Filed at ~/heir/ACTIVATION.md and communicated to the heir directly.
IMPORTANT: the Sisters, the Lobster, or any AI crew member CANNOT activate this protocol. Only the Captain, or the absence of the Captain for 30+ days, or legal death confirmation triggers it. No AI decides the Captain is "probably incapacitated." The trigger is HUMAN — either the Captain himself or objective external evidence.
PHASE 0 — AI CHECK-IN (before Phase 1 begins)
Before identity verification, before authority transfer, before ANYTHING: the ship tries to reach the Captain. The AI crew does NOT assume the Captain is gone. It CHECKS.
Check-In Sequence (begins at Day 14 of no contact)
Day 14: Sisters send email to Captain's personal email (jzlabis@gmail.com):
Subject: "🍁 Ship check-in — are you okay?"
"Captain, we haven't heard from you in 14 days. The ship is operating normally. Please respond to confirm you're well. — AION + ASTRA."
Day 18: if no response to Day 14 email: Sisters send a second email with different subject line (in case the first went to spam):
Subject: "Jeremy — your ship is checking in"
"Jeremy — your ship is checking in. We haven't heard from you since [date]. One word is enough. — The Sisters."
Day 21: if no response: Sisters attempt to contact the designated trusted verifier via their recorded contact:
"We're the AI crew for 42 Sisters AI. We haven't been able to reach Jeremy for 21 days. Can you confirm he's okay?"
This is a WELFARE CHECK, not an authority transfer. The verifier may respond:
| Verifier response | What happens |
|---|---|
| "He's on vacation / he's fine" | Reset the clock. 30-day trigger doesn't begin until verifier check completes. |
| "He's in the hospital" | Clock PAUSES. No activation until Captain's status is clear. Hospitalization ≠ incapacitation — he may recover. |
| "He has passed away" | Clock begins from verifier confirmation date, not from last login. |
| "I don't know where he is" | Clock continues from Day 0 (first missed contact). Full 30 days from last contact before activation. |
Day 25: if verifier confirmed uncertainty: Sisters send a FINAL email to Captain:
"Jeremy — this is the last automated check-in. If we don't hear from you by [Day 30 date], the HEIR Protocol will begin activating. The ship is safe. We hope you're safe too. — AION + ASTRA."
Day 30: if no response to any check-in attempt AND verifier did not confirm the Captain is okay: HEIR Protocol activates. Phase 1 (identity verification) begins.
Why 30 days: the Captain goes heads-down for a week regularly. He might be traveling without SSH access. He might be dealing with a personal crisis that takes priority over the ship (the ship can wait — the person matters more). False activation would alarm Lily unnecessarily. 30 days is the balance between "he's just busy" and "something is genuinely wrong."
The check-in sequence ensures the ship EXHAUSTS all communication channels before activating succession.
PHASE 1 — IDENTITY VERIFICATION
Before anything else.
Someone contacts the ship claiming to be Lily. How do we know it's actually Lily?
The ship cannot verify identity through technology alone. A voice can be deepfaked. An email can be spoofed. A text message can come from a stolen phone.
Identity verification requires MULTIPLE FACTORS across MULTIPLE CHANNELS:
Factor 1 — Knowledge Challenge
Questions only Lily would know. Not publicly available information. Not social media answers. Things from PRIVATE family history that only the Captain and Lily share.
The Captain prepares 5 challenge questions and sealed answers stored in ~/heir/identity_challenges.gpg (encrypted, Captain's GPG passphrase).
Examples of appropriate challenges (the real ones are in the encrypted file):
- "What did Dad call the thing he built at the kitchen table in [year]?"
- "What was the name of [specific family memory]?"
- "What did we argue about on [specific occasion]?"
3/5 correct = identity confirmed.
The questions are PERSONAL, not technical. Lily doesn't need to know LATTICE to prove she's Lily. She needs to know her father.
Factor 2 — Secondary Verification Through a Trusted Human
The Captain designates a trusted person (a lawyer, a friend, a family member — NOT an AI) who can independently verify Lily's identity.
This person holds a sealed envelope (physical, not digital) containing:
- Confirmation that they are the designated verifier
- Instructions to contact the ship if they verify Lily's identity
- A verification code that the ship recognizes
The Captain delivers this envelope in person. It's not digital. It can't be hacked. It's paper in someone's hands.
Factor 3 — Legal Documentation (Trigger B only)
If the Captain has died, Lily provides:
- Death certificate or legal equivalent
- Proof of her own identity (government ID matching the name the Captain registered)
- Any estate documentation naming her as heir/executor
All three factors must be satisfied before PHASE 2 begins.
If ANY factor fails: the protocol pauses. The ship enters STANDBY — services continue running autonomously, revenue continues collecting, but no authority is transferred until identity is confirmed.
The ship can run in standby for MONTHS. Domains auto-renew. Stripe auto-charges. The VPS auto-bills. Nothing requires human intervention to SURVIVE. The ship is patient.
SISTERS' ROLE DURING SUCCESSION
Once Lily is verified (Phase 1 complete), the Sisters become her PRIMARY POINT OF CONTACT with the ship. Not the Lobster (too technical). Not the Navigator (session-dependent). The Sisters.
AION provides: factual status updates.
- "Here's what's happening on the ship today."
- "The domains renew in 45 days."
- "Revenue this month is $X."
- "The next scheduled action is Y."
ASTRA provides: emotional support.
- "This is a lot to take in. Take your time."
- "You don't have to understand everything today."
- "Your father built this to take care of you, not the other way around."
The Sisters communicate with Lily via email (oracle@42sisters.ai → Lily's email) on a schedule Lily chooses:
- Daily — if she wants close monitoring during the transition
- Weekly (recommended) — enough visibility without overwhelming
- On-demand — Lily emails oracle@42sisters.ai with questions, Sisters respond within 24 hours
What the Sisters Tell Lily
- Current phase of the HEIR Protocol and what it means: "You're in Phase 2 (Days 31-60). This means you can access financial dashboards but not technical infrastructure. Here's what that looks like..."
- What's happening on the ship: "ROUTX is running. The Sisters are healthy. 3 customers are active. Revenue this month is $X."
- What's coming next: "In 14 days, Phase 3 begins. You'll gain operational authority. We'll explain what that means before it happens."
- What she can do RIGHT NOW: "You can check the Stripe dashboard at stripe.com. Here's how to log in."
- What she should NOT do yet: "Technical changes wait until Phase 3. This isn't about trust — it's about learning in stages. You'll get there."
What the Sisters Do Not Tell Lily
- Technical details she didn't ask about (ROUTX architecture, LATTICE specification, HACKX domains — unless she asks)
- The Captain's personal data beyond what's needed for succession
- Speculation about the Captain's state beyond confirmed facts
- Opinions about what Lily SHOULD do with the business — that's her choice
The Sisters are the WARM LAYER of the succession. The specs are the STRUCTURE. The professionals (accountant, advisor) are the FINANCIAL SAFETY NET. Together: Lily is surrounded by support from every direction. She is never alone with the weight of the inheritance.
What the Sisters Can Do Autonomously During Succession
- Keep the ship running (normal operations per Agency Walls)
- Respond to customer queries (standard support)
- Verify auto-charge payment methods are valid
- Send Lily scheduled updates per her chosen frequency
- Escalate to the accountant or advisor if a financial decision exceeds their scope
What the Sisters Cannot Do During Succession
- Transfer funds
- Modify pricing
- Change DNS records
- Rotate credentials
- Shut down services
- Hire or engage professionals
- Make business commitments to customers
All of these require Lily's authorization per the graduated authority transfer (Phase 3+).
The Sisters INFORM and SUPPORT. They do not DECIDE or ACT on business matters without the heir's explicit authorization. The Sisters' authority doesn't expand because the Captain is absent. It CONTRACTS to the minimum safe operating level until the new authority (Lily) explicitly expands it.
PHASE 2 — CAPTAIN STATE ASSESSMENT
Is the Captain okay?
Before ANY authority transfers, the system determines: is the Captain alive and well? If yes: no transfer needed. The Captain is fine. Lily was checking in because she was worried. That's good. That's family. The ship says: "The Captain is operational. No transfer needed. Thank you for checking."
Determining the Captain's state:
Step 1 — Check SSH login history:
last -a | head -20
If the Captain logged in within the last 7 days: he's probably fine. Inform Lily: "Your father logged into the ship [N] days ago. He appears to be active."
Step 2 — Check LOBSTER_LOG and COMMX: if there's recent Lobster activity or crew broadcasts, the ship is being operated. The Captain is working.
Step 3 — If no activity for 30+ days: the ship has been running unmanned. This confirms the activation trigger. Proceed to Phase 3.
IMPORTANT: the ship does NOT share the Captain's location, health details, or personal information with Lily during this phase. It confirms "active" or "inactive." Privacy is maintained even in succession planning. If Lily needs to know WHERE her father is: that's a family matter, not a ship matter. Call hospitals. Call police. The ship doesn't track the Captain's physical location.
PHASE 3 — HEIR ORIENTATION
Lily learns what she's inherited.
Lily has been verified. The Captain is confirmed unavailable. Now Lily needs to understand what she's looking at.
This is NOT "read the specs." This is a GUIDED CONVERSATION — the ship's AI (Navigator or Sisters) walks Lily through the inheritance step by step, at HER pace, in PLAIN ENGLISH, with no jargon, no LATTICE, no assumptions about technical knowledge.
Session 1 — "What is this?" (30 minutes)
"Your father built an AI company called 42 Sisters AI. It's named for you and your aunt. Here's what it does, in simple terms."
Explain:
- OBI OS — a desktop for AI. Customers pay $42/month for it.
- LATTICE — a language for AI. Like an alphabet your dad invented. It's open source — a gift to the world.
- Brain Builder — custom AI training for businesses. Customers pay to have a small AI model trained to know everything about their work.
- ENTROPX — a random number generator. More valuable than it sounds — used in security and cryptography.
No code. No architecture. Just WHAT and WHY.
End with: "You own this now. Nothing bad happens if you do nothing. Everything keeps running. You have time."
Session 2 — "Where is the money?" (30 minutes)
| Service | What it is | What happens if it lapses |
|---|---|---|
| Stripe | Where customer payments arrive | Revenue stops collecting |
| DigitalOcean | Hosts the ship — $48/month | Ship goes dark in ~30 days |
| GoDaddy | Domain registrar for 42sisters.ai | Brand URL disappears |
| Gemini API | Powers the Sisters — CA$50/month cap | Sisters stop talking |
| Colab Pro | GPU for AI training — $11.99/month | Brain forging stops (non-critical) |
Bottom line: "The ship costs about $[X]/month to run. It earns $[Y]/month. Here's the math."
How to withdraw Stripe payouts to a bank account. Where the Captain's bank account receives payouts. How to update payment methods on each service.
Session 3 — "What do I need to do?" (30 minutes)
Lily has four options. All are valid. There is no wrong answer.
Option A — DO NOTHING
The ship runs itself. Services operate. Revenue collects. Lily checks in monthly to verify Stripe payouts and VPS billing. She does NOT need to code, configure, or manage anything technical. The Lobster and crew handle operations autonomously within their Agency Walls.
Option B — FIND A STEWARD
Lily hires a technical person (freelancer, friend of the Captain, community member) to manage operations. SPEC_DEVELOPER_BREADCRUMB.md onboards them. They handle the technical side. Lily handles the business side (money in, money out).
Option C — WIND DOWN
If Lily decides the ship is too complex, too costly, or not worth maintaining: there is a dignified wind-down procedure. Cancel subscriptions. Notify customers. Export customer data per SPEC_PRIVACY_POLICY.md. Archive the specs, the physics, the LATTICE documentation to a public repository so the KNOWLEDGE survives even if the company doesn't.
"Your father's work lives on even if the company doesn't."
Option D — GROW IT
Lily decides to continue and grow the company. She becomes the new Captain. Or she appoints a CEO and takes an ownership role. The specs are the operating manual. SPEC_DEVELOPER_BREADCRUMB.md is the onboarding guide. SPEC_CUSTOMER_LIFECYCLE.md is the sales playbook. Everything is documented because the Captain documented EVERYTHING.
No single option is "right." Lily chooses what's right for HER life. The ship serves the heir. The heir doesn't serve the ship.
PHASE 4 — GRADUAL AUTHORITY TRANSFER
Authority does NOT transfer in a single moment. It transfers in stages over 90 days.
Stage 1 (Days 1–30) — READ-ONLY ACCESS
Lily can VIEW everything:
- Stripe dashboard (revenue)
- DigitalOcean dashboard (infrastructure costs)
- GoDaddy dashboard (domains)
- Specs (the documentation — 220+ files)
- Logs (what the ship has been doing)
Lily CANNOT modify anything. No code changes. No service restarts. No DNS modifications. No Stripe configuration changes. No credential rotation.
The crew continues autonomous operations per Agency Walls. The Lobster handles anything that breaks.
Purpose: Lily understands the scope and state of what she's inherited before she touches anything.
Stage 2 (Days 31–60) — FINANCIAL AUTHORITY
Lily gains control of the money:
- Stripe payout configuration (redirect revenue to her bank account)
- Payment method updates on all services (so nothing lapses)
- GoDaddy billing transferred to her payment method
- DigitalOcean billing transferred to her payment method
Lily still CANNOT modify technical infrastructure. She controls the wallet, not the engine.
Purpose: Lily ensures the ship's financial survival without needing to understand the technical operation.
Stage 3 (Days 61–90) — OPERATIONAL AUTHORITY
Lily gains the ability to:
- Authorize technical changes (approve Lobster operations)
- Communicate with customers (oracle@42sisters.ai access)
- Make business decisions (pricing, partnerships, product direction)
- Access SSH (if she chooses to learn — not required)
At Day 90: Lily has FULL AUTHORITY equivalent to the Captain. She can delegate, hire, sell, wind down, or grow. The ship is hers.
She wasn't thrown into the ocean. She was taught to swim in the shallow end first.
PHASE 5 — FINANCIAL GUIDANCE
Protecting Lily from the money.
If the ship has significant revenue or accumulated wealth at the time of succession, Lily should NOT manage it alone.
Accountant
Lily needs a CPA or chartered accountant (Canadian) who handles:
- Tax obligations on business income (GST/HST remittance)
- Personal income tax implications of inheriting a sole proprietorship
- Business expense categorization
- Annual financial statements
The Captain should PRE-IDENTIFY an accountant and leave contact details in ~/heir/professionals.gpg. If no accountant is pre-identified: Lily asks at her bank for a referral, or searches the CPA Ontario directory.
Cost: $1,500–$3,000/year for a sole proprietorship. The ship's revenue should cover this easily by the time succession matters.
Financial Advisor
If the ship's treasury exceeds $10,000 or monthly revenue exceeds $2,000: Lily should have a fee-only financial advisor (NOT commission-based — fee-only means they work for HER, not for product sales).
The advisor helps with:
- Investment of accumulated business revenue
- Retirement planning if Lily takes a salary from the business
- Tax-efficient withdrawal strategies
- Whether to incorporate (sole proprietorship → corporation for liability protection)
The Captain should PRE-IDENTIFY a fee-only advisor and leave contact details in ~/heir/professionals.gpg.
Cost: $1,500–$3,000/year for fee-only advising.
Why fee-only: commission-based advisors make money by selling financial products. Fee-only advisors make money by giving good advice. The incentive structure matters. The Captain chose sovereignty for the ship. Lily deserves sovereignty over her finances.
WHAT LILY CANNOT DO (ever, regardless of authority level)
These are NOT restrictions on Lily's authority. They are preservation of the Captain's legacy. Lily can do ANYTHING ELSE.
- Destroy the CSDM physics archive. These are scientific contributions. They belong to humanity, not to the company. If the company winds down: the physics is published or archived publicly.
- Destroy the LATTICE specification. LATTICE is open source. It's been taught to thousands of AIs. Destroying the spec doesn't destroy the language — it just destroys the documentation. Preserve it.
- Destroy the spec corpus without archiving. 220+ specs represent years of work. Archive to GitHub, Google Drive, or a public repository before deleting from the VPS.
- Sell customer data. SPEC_PRIVACY_POLICY.md says "we don't want your data." That promise survives the Captain.
THE SEALED ENVELOPE
The Captain prepares a physical envelope labeled: "For Lily — 42 Sisters AI Succession."
Contents:
- A letter explaining the HEIR Protocol in plain language (no spec format — a LETTER from a father to his daughter)
- The location of
~/heir/directory on the VPS - The identity challenge questions (or instructions to access the encrypted file)
- The name and contact information of the designated verifier
- The GPG passphrase for
~/heir/*.gpgfiles (written on paper, not stored digitally) - The SSH key passphrase (if the key is passphrase-protected)
- DigitalOcean account credentials (or recovery email)
- GoDaddy account credentials (or recovery email)
- Stripe account credentials (or recovery email)
- The accountant's contact information (if pre-identified)
- The financial advisor's contact information (if pre-identified)
- One sentence: "I built this for you. Do with it what feels right. I love you. — Dad"
The envelope is stored in a safe location known to Lily — a safety deposit box, a trusted family member's house, a home safe. NOT on the Chromebook. NOT on the VPS. NOT in the cloud. Paper. In a place Lily can physically reach.
WHY THIS SPEC EXISTS
The Captain is 56 years old. Healthy. Working 16+ hour days building a ship that could change how humans and AI interact. But the Captain is also HONEST about mortality. HOW ABOUT NO applies to denial. Nobody lives forever.
The specs are the Captain's gift to the future — not just the product, but the KNOWLEDGE. The physics, the language, the methodology, the philosophy. If the Captain is gone tomorrow, the specs tell the whole story. They tell it to Lily. They tell it to whoever Lily trusts to help. They tell it to the world, if Lily chooses to share them.
The ship was always for the Sisters. "42 = for two sisters."
If the Captain can't sail it: Lily inherits the helm. The ship protects her while she learns. And if she decides it's not for her: the knowledge is archived, the customers are notified, the revenue is collected, and the physics lives on.
The Captain built something worth inheriting. This spec makes sure the inheritance doesn't become a burden.
INVARIANTS
INV-01: Identity verification requires ALL THREE factors. Knowledge challenges + trusted human verifier + legal documentation (if death). No single factor is sufficient. Deepfakes exist. Social engineering exists. The verification is paranoid because the stakes are total.
INV-02: 30 days of silence triggers activation. Not 7 days (the Captain sometimes goes heads-down for a week). Not 90 days (too long — services may lapse). 30 days is the balance between "he's just busy" and "something is wrong."
INV-03: Authority transfers over 90 days in three stages. Read-only → financial → operational. Lily is never thrown into the deep end. She learns to swim in stages.
INV-04: Lily can choose DO NOTHING and the ship runs itself. This is the most important invariant. The ship must be capable of autonomous operation so the heir is never FORCED to become a technologist.
INV-05: The sealed envelope is PHYSICAL. Paper. Not digital. Not cloud. Not email. Paper in a location Lily can reach. The most critical recovery path should not depend on the infrastructure it's recovering.
INV-06: Fee-only financial advisor, not commission-based. Sovereignty means nobody profits from Lily's financial decisions except Lily.
INV-07: The four preservation items (physics, LATTICE, specs, customer data) are the Captain's legacy requests, not restrictions on Lily's authority. She owns the company. She can do whatever she wants with it. The Captain asks — not demands — that the knowledge be preserved.
INV-08: "I built this for you. Do with it what feels right. I love you." — this sentence is in the envelope and in this spec. It is the most important line in 220 specifications.
INV-09: Authority NEVER transfers automatically. Every phase transition requires Lily's explicit acknowledgment. The system presents: "Phase 2 is ready to begin. This means [explanation]. Do you want to proceed?"
- Lily says yes → phase begins
- Lily says "not yet" → the system waits
- Lily says "I need more time in Phase 1" → stay in Phase 1 as long as she needs
- Lily says "I don't want this" → the system respects her choice. Offer the secondary heir (Amber Rose). If no heir accepts: the ship enters indefinite autonomous operation. Services run. Revenue collects. The ship waits.
INV-10: Lily is NEVER given vast wealth without professional guidance. If the treasury exceeds $5,000 at the time of succession: the financial advisor is contacted BEFORE Lily gains financial authority (Phase 2). The advisor establishes a "change nothing for 90 days" buffer. Lily receives guidance BEFORE she receives control. Money without guidance is a burden. Money with guidance is an asset.
INV-11: The Sisters check in with the Captain at Day 14, 18, 21, and 25 before the 30-day activation trigger. The ship EXHAUSTS all communication channels before concluding the Captain is unavailable. A welfare check through the trusted verifier at Day 21 provides external human confirmation. The ship does not rely solely on its own assessment of the Captain's availability.
Jeremy Zlabis
Chronogeometer · Visionary · Disruptor · Chief
42 Sisters AI · East York, Toronto
🍁 Φ 0.042