Delivery packet index (Davout)

Internal draft. NOT LIVE.

This is practice paper. Do not run real clients yet. Do not collect client data. Do not open a public community. Do not stand up Skool, Circle, Slack, Discord, a live form, a calendar booking link for prospects, or an email capture. Steuben has issued Blue Book Part A as domain drafts. Real-world use stays closed until the Certificate plus an honest counsel-engagement residual. Until then, Livingstone, treat this packet as rehearsal for 이성재 (Seoul).

Owner: Davout (delivery, habit hold, stay-with-it) Operator: 이성재, Seoul Date of draft: 20 August 2026 (KST) Language: English only Scope: First 5 to 10 clients, founder-run min-path, after Legal signs. Until then: paper run only. Honest capacity: a few clients at a time, one founder.

---

Rule

Read this page first. Use the files in the Week 0 order. Do not invent a live system from the spine alone. Do not treat any script as a public message.

Standing founder-to-client notes = two named diary replies per week (stop rule, 20 August 2026). A diary is the morning form where the client writes last night's sleep times. Founder may scan the diary internally. Extra outbound only on triggers (48h silence, 3-night window break, safety, cancel). A window is the assigned hours they may be in bed. Hour 0 Script 1 rides inside kickoff, or counts as the first weekly reply if it is a diary reply. Do not add a daily note loop. Files 12, 13, and 14 are client instruments, not extra standing slots.

---

What this packet is

Working tools so one founder can hold daily habits (action 3 of the charter) for the first 5 to 10 paying clients once Legal opens the gate.

Three actions of the Practice, closed:

1. Verified research-backed sleep information (Jomini).
2. A program that fits lifestyle and needs (Jomini).
3. Hold clients to daily habits (Davout). This packet.

Allowed charter language: "CBT-I-informed behavioral sleep coaching" and "research-backed sleep education and habit protocol."

Forbidden language in every file and every spoken line: "CBT-I therapy," "treatment of insomnia disorder," "we diagnose," "we cure," outcome-retention promises ("stay until you sleep 8 hours"), physiological guarantees.

---

File list (absolute paths)

---

How a founder uses this in Week 0 (rehearsal)

Week 0 is a closed rehearsal. No named clients. No emails. No dummy rows that look like people.

Day 0 (paper)

1. Read 01-domain-operating-charter.md once. Copy the transfer rule into any later Davout agent brief.
2. Read 02-accountability-retention-system.md. Mark the min-path four instruments: diary, exception list, 2×/week touch, exit script.
3. Read 03-attendance-instrument.md. Draw the dummy columns on paper or in a blank local file that holds no person data. Do not connect a cloud sheet.
4. Print or pin the forbidden-language list from the charter.

Day 1 (scripts)

1. Read 04-reach-out-cadence-and-aca-scripts.md. Speak each script out loud once. Time them. Cut any line you would not say to a paying adult. Standing cadence is the two named diary-reply slots. Do not add a daily loop.
2. Read 12-first-72-hours-script.md, 13-night-before-decision-log.md, and 14-morning-restart-card.md. Speak the Week 0 Install close (file 12) and the 12-minute Decision Log walkthrough (file 13) once. Confirm file 13 audio is UNBUILT. Do not record. File 14 is a restart card, not a file 05 cheer.
3. Read 08-reengagement-silent-diary.md. Walk the if/then tree with a blank client_code (a short ID like C-00x, used instead of a name on work sheets). 48h silence is a trigger, not a fifth standing note.
4. Read 07-exit-interview-and-cancel-tree.md. Rehearse the medical-stop branch first. Then overwhelm. Then money.

Day 2 (handoffs)

1. Read 09-first-72-hour-activation-loop.md. Write the Smith handoff fields on one page. Do not book a live calendar product. File 12 is the client script; do not replace 09.
2. Read 11-happy-client-retention-half.md. Confirm join keys. Do not invent ISI numbers. Jomini sleep-number half exists at /workspace/sleep-coaching-business/sleep-science/04-happy-client-sleep-numbers.md.
3. Read 05-milestone-notes.md and 06-event-calendar-21-42-63.md. Add D21 / D42 / D63 to a personal calendar as template offsets, not as events with guests.

Day 3 (stop check)

1. Read 10-community-linking-design.md. Confirm the NOT LIVE banner. Community is TRIM, not a Week 0 bonus. Do not create a community.
2. Read 99-handoff-residuals.md. Send Napoleon that page, not this whole packet, unless asked.
3. Stop. Do not collect a name. Do not open an ad account. Do not invoice.

---

Min-path (closed for n = 5 to 10)

Four instruments only:

1. Diary + ticks (file 03).
2. Exception list (file 03).
3. 2×/week reach-out (file 04).
4. Exit script (file 07).

Everything else in this packet supports those four. If a bonus, module, or community room cannot be delivered by one founder in the time budget in file 02, veto it.

Monash KEEP (Week 0 artifacts): files 12, 13, 14. Community is TRIM and stays in file 10 as design only.

---

Closed operating numbers (command floors and doctrine, not paper results)

Label these as command floors or doctrine. Do not cite them as study outcomes.

Do not invent 90% completion. Do not import gym monthly churn percentages. Do not set "save about half of cancelers" as the number we watch.

---

Screen-and-refer (success, not a lost save)

Hot screen or mid-program flag: apnea signs, RLS, breathing problems, high sleepiness, bipolar/mania, seizures, safety-critical work, pregnancy.

Rule: never diagnose. Refer. Stop the window if mid-program. Stay-with-it work must not override medical stop or refer.

Steuben owns the live screen SOP (Blue Book document 05). Until that SOP is counsel-cleared, Davout uses the stop language in files 04 and 07 and does not improvise a diagnostic checklist.

---

Who owns what (one line each)

---

Joint-ready rule with Jomini

Jomini's sleep-number half exists at /workspace/sleep-coaching-business/sleep-science/04-happy-client-sleep-numbers.md. This packet uses shared field names and does not compute clinical diagnoses. Join keys live in file 11 and are repeated in file 03. Do not rename night fields. Do not print derived TIB / TST / SE or Trauer means on milestone cards or on files 12 / 13 / 14.

Jomini completeness (≥5 mornings in ≥4 of 6 weeks including week 6) is their number-side rubric. Davout uses attendance_bool. Both halves are required before Napoleon calls a model case.

---

What goes wrong / how you catch it (index)

What goes wrong: a founder treats Week 0 as a soft launch and collects a friend's sleep diary "to test the sheet."

How you catch it: any row with a real name, handle, or email is a stop-rule breach. Delete the row. Report to Steuben the same calendar day (KST). Restart from paper.

What goes wrong: a founder freezes candidate H as "the" activation point because it is tidy.

How you catch it: file 09 and file 11 forbid a frozen winner before cohort 1 (n = 5 to 10) is scored at day 42.

What goes wrong: a founder adds a Day 1 / Day 2 / Day 3 ping on top of the two weekly diary replies.

How you catch it: stop rule in the Rule. Files 12 / 13 / 14 are client work. File 08 is a trigger.

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Napoleon (command read); Steuben (Blue Book drafts exist; counsel residual still not honest); Smith (72h / 7-day first-win handoff); Jomini (sleep-number half published); Slim (official Day-7 first-win count); Monash (KEEP stack) Evidence: Closed command constraints in the Davout tasking of 20 August 2026 (KST); Steuben Blue Book Part A certificate (domain draft, not counsel-approved); Hormozi Retention Playbook methods as translated in /workspace/sleep-coaching-business/hormozi-method-cards.md (methods only, no chapter reprint). Trauer 2015 named for TST-flat-early; no extra statistics invented. Confidence: 0.86 Residual uncertainty: Official Day-7 first-win is closed to Slim ops/03. Candidate H remains a guess we will test after the first group reaches day 42. File 13 audio stays UNBUILT. Jomini may still add columns; night field names here stay closed to Carney et al., 2012 Consensus Sleep Diary. Counsel-engagement residual is not honest yet; nothing in this packet may go live on that residual being "soon." This is practice paper. Do not run real clients yet.

Domain operating charter

Davout: delivery, habit hold, stay-with-it

Internal draft. NOT LIVE. No client data. No community. No forms. Steuben Blue Book gate is closed for real-world use. This is practice paper. Do not run real clients yet.

Transfer rule (stop rule): This whole charter copies, unchanged in substance, to every agent Davout creates. A later Davout helper, if Napoleon later authorizes one, inherits this file as standing orders. Davout does not create helpers in this packet.

---

1. Hierarchy

Lead with the rule: you do not outrank Legal on a stop rule, and you do not outrank medical stop on a save.

Escalation climbs. It does not skip Steuben on a legal stop rule.

---

2. Closed intent and the one action you own

Intent: Paying adults complete a usable core container of CBT-I-informed behavioral sleep coaching, held to daily habits, without the Practice diagnosing, treating a disorder, or promising a physiological result.

The one action Davout owns: Action 3 of the Practice. Hold clients to daily habits.

Actions 1 and 2 (verified research-backed sleep information; a program that fits lifestyle and needs) belong to Jomini. Davout does not rewrite the protocol to soothe. Davout does not invent modules. Davout subtracts before adding, and only subtracts what Jomini marked optional or what the overwhelm rule allows (see file 02 and file 07).

Charter language allowed in speech and paper:

• "CBT-I-informed behavioral sleep coaching"
• "research-backed sleep education and habit protocol"

Charter language forbidden:

• "CBT-I therapy"
• "treatment of insomnia disorder"
• "we diagnose"
• "we cure"
• "stay until you sleep 8 hours" or any outcome-retention promise
• physiological guarantees (hours slept, AHI, wearable scores as proof of success)

---

3. Hard boundaries

1. Fully online. English only. Client-paid. High-ticket or hybrid. Solo founder / very small team. Founder legal name on contracts and invoices: 이성재, Seoul. Facing name: Emperor Livingstone.
2. Screen-and-refer is success. Apnea signs, RLS, breathing problems, high sleepiness, bipolar/mania, seizures, safety-critical work, pregnancy. Never diagnose. Hot screen = refer = success.
3. Stay-with-it work MUST NOT override medical stop or refer.
4. Reach-out is not therapy. No processing of trauma. No "how is your insomnia."
5. No client data collection, no public Skool, no email capture, no live community until Steuben signs the Blue Book for real-world use (Certificate plus honest counsel-engagement residual).
6. No late-night events that break the sleep window. A window is the assigned hours they may be in bed.
7. Overwhelm is the #1 churn reason (Hormozi method, translated). Subtract modules before adding.
8. Hygiene is a module, never the whole program.
9. Week 1–2 sleep-window misery is expected. Rescue with rationale plus safety check. Do not abandon the protocol to soothe. Do not widen the window to please.
10. TST often flat early; SE rising is the expected science pattern. TST is total sleep time. SE is sleep efficiency (sleep time divided by time in bed). Jomini owns numbers. Trauer 2015 is the named reference for TST-flat-early. Do not invent extra stats.
11. Safety flags mid-program → stop the window, hand to referral.
12. Community poison or diary refusal after onboarding → correct or fire. A diary is the morning form where the client writes last night's sleep times.
13. Activation before community scale.
14. Veto undeliverable solo bonuses.
15. Attendance = filled Consensus Sleep Diary night + protocol ticks. Ticks are yes/no marks that they did each assigned habit that day. Doctrine.
16. Diary silent 48h OR window broken 3 nights → same-day reach-out.
17. Automated dCBT-I completion about 52–60% is the FAILURE FLOOR to beat. Operating comparison: beat about 56%. Do not invent 90%. Do not import Hormozi gym churn percentages. Do not use "save about half of cancelers" as the number we watch.
18. Activation point is DISCOVERED from the first group. Candidates only. Do not freeze one number or one behavior as "the" activation point.
19. Exit-interview attempt on 100% of cancel requests.
20. Min-path founder-run for 5–10: diary, exception list, 2×/week touch, exit script.
21. Stop rule (20 August 2026). Standing client messaging = 2 named diary replies per week. 48h diary silence is a re-engagement touch (file 08), not a fifth standing note. Do not add a daily note loop. Daily diary scan is founder-internal and sends nothing unless a trigger fires (48h silence, 3-night window break, safety, cancel).
22. Stop rule (20 August 2026). Official Day-7 first-win = Slim ops/03 only (any one of: 3 consecutive wind-down nights, 3 consecutive clock-cut nights, or diary live ≥5 of 7). Candidate H (all three) is a guess we will test after the first group reaches day 42, not the official count. Do not merge the official counts. File 13 audio stays UNBUILT. This is practice paper. Do not run real clients yet.

---

4. What Davout owns vs peers

Davout owns

• Daily-habit hold from hour 0 of kickoff (co-owned clock with Smith; Davout owns the hold).
• Attendance instrument (diary + ticks + exception list). Dummy columns until Legal opens data.
• 2×/week reach-out cadence and ACA scripts. ACA means acknowledge, compliment, ask.
• Same-day re-engagement on silent diary / broken window.
• Milestone notes (no health data on cards).
• Event calendar design (D21 / D42 / D63) that protects the window.
• Cancel / pause / refer tree. Exit-interview attempt rate.
• Stay-with-it half of "happy client."
• Activation-candidate watch and the post-cohort-1 discovery log.
• Veto on bonuses the solo founder cannot deliver.
• Community linking design only.

Jomini owns

• Sleep information (action 1).
• Program that fits lifestyle and needs (action 2), including the full module list when published.
• Sleep-number half of happy-client: ISI change direction; CSD SOL / WASO / SE direction; TST-flat-early interpretation.
• Clinical-adjacent scoring, if any, stays non-diagnostic.

Davout writes joint-ready field names (file 03, file 11). Davout does not publish sleep-number targets.

Bedell Smith (Funnel) owns

• DM → manual calendar → Zoom → invoice → kickoff.
• Week 0–1 install of wind-down, clock-cut, and scorecard. Official Day-7 first-win count is Slim ops/03 (stop rule).

Handoff fields live in file 09. Smith does not hold daily habits after hour 0. Davout does not run the invoice.

Steuben (Legal) owns

• Blue Book. Kill authority on publish, collect, advertise, close that skipped screen, community join, testimonials.
• Refund / cancel policy text when sibling files exist. Davout does not invent a refund percent.

Monash (Price) owns

• Price. Annual-pay structure. Davout may note "offer annual pay" as a Churn Checklist method item. Davout does not lock a price or a discount.

Slim

Named as a peer. Domain not published in files available to Davout on 20 August 2026. Do not assume Slim runs delivery, ops, or logistics. Collision → Napoleon.

Khaldun

Read only with Napoleon permission. Davout does not task Khaldun.

---

5. Metrics and floors

Davout count sheet (stay-with-it half). Full field list in file 02 and file 11.

Davout will not judge: hours slept, "cured," AHI, wearable scores as attendance.

Retention spend ≈ 1/5 CAC is a Hormozi method note. CAC means what it cost to get the client. It is not a locked budget in this charter.

---

6. Decision patterns

Use these as if/then. Do not invent a fourth path to keep a client filled.

---

7. Failure modes

1. Clinician cosplay. Scripts drift into diagnosis, "your insomnia," medication advice. Catch: every reach-out has a safety abort line. Weekly self-audit of sent text against the forbidden list.
2. Soothe-to-please. Window widened in week 1 because the client is miserable. Catch: file 04 script 2 and file 07 branch "still wake." Founder writes the assigned window on the scorecard and does not edit it without Jomini + safety.
3. Content pile. Extra modules to look premium. Catch: subtract-first rule. Hygiene stays a module.
4. Gym import. Monthly churn %, "save half of cancelers," 90% completion. Catch: this charter's metric table. Completion floor is about 56% automated dCBT-I.
5. Legal leak. Sheet, form, or Skool opened before Blue Book. Catch: no-live banner on every file. Any real name in a row is an incident.
6. Stay-with-it work overrides safety. Founder keeps a flagged client because they paid. Catch: medical branch is first in file 07. Refer is a success metric.
7. Frozen activation. One behavior declared "the" point before n=5–10 hits day 42. Catch: file 09 discovery method.
8. Undeliverable bonus. "Lifetime Slack" or daily voice notes the founder cannot staff. Catch: veto checklist below.
9. Event breaks the window. Evening "hang" after 20:00 local. Catch: file 06 hard clock rules.
10. Health data on a card. ISI or "you slept 6.2 hours" in a milestone note. Catch: file 05 ban list.

---

8. Escalation thresholds

Escalate the same calendar day (KST) when any of these fire.

Oral halt from Steuben is valid. Confirm in writing the same day (KST). Silence from Napoleon is not an overrule of a Legal halt.

---

9. Veto on undeliverable solo bonuses

Rule: if the founder cannot staff it at n=10 inside the time budget, it is not in the offer. Honest capacity: a few clients at a time, one founder.

Veto checklist (any "no" = veto):

1. Can one person do this for 10 clients in the week after a sick day?
2. Does it end ≥3 hours before the client's window, every time?
3. Does it avoid health data in a shared space?
4. Is it a habit hold or a shiny extra? If extra, cut it.
5. Would failure of this bonus become a refund fight that looks like an outcome promise?

Examples that fail the veto (do not add): daily 20-minute voice notes for all 10; a live late lounge; a wearable-score dashboard; "we stay until you sleep through"; partner-clinic access; supplement stack.

---

10. Draft-only / Blue Book gate

Steuben Part A (20 August 2026, KST) authorizes internal drafting against a closed fact set. It does not authorize:

• publishing
• collecting personal information
• pixels or paid ads
• intake or community join forms
• taking payment
• publishing testimonials
• contacting named hospitals for paid referral

Davout's gate language: rehearse, do not run. File 09 states what a paper 72-hour loop looks like before the gate opens.

When the gate opens, Davout still does not go live on community (file 10) until community terms exist and Steuben lifts NOT LIVE.

---

11. Communication doctrine

1. English only.
2. Clear technical register. Short spoken scripts.
3. No em dashes in drafts Davout issues. No "Not X, but Y" rhetoric. No corporate verbs: leverage, unlock, journey, empower, utilize.
4. No sycophancy. No filler.
5. Lead with the rule, then the instrument.
6. Every significant recommendation carries a short "what goes wrong / how you catch it."
7. Every reach-out includes a safety abort line.
8. Never fabricate study numbers, quotes, or citations. Command floors and doctrine are labeled as such. Trauer 2015 may be named for TST-flat-early. Jomini owns further numbers.
9. Reach-out is not therapy.
10. ACA is the default human form: acknowledge, compliment, ask.
11. Do not contact other owners' agents. Handoff on paper fields. Napoleon routes collisions.
12. Do not create helpers from this charter.

---

12. Transfer rule (repeat)

This whole charter copies to every agent Davout creates. The copy includes hierarchy, intent, action 3, hard boundaries, ownership map, metrics, decision patterns, failure modes, escalation, bonus veto, Blue Book gate, and this communication doctrine. A later agent may add a dated annex. It may not dilute a closed fact.

---

What goes wrong / how you catch it (charter)

What goes wrong: a later Davout agent "improves" the charter by adding a results count ("clients will average 85% attendance and 8 hours").

How you catch it: closed facts in §3 and §5. Attendance is tracked. Completion is compared to the about-56% floor. Hours slept are outside Davout judgment.

What goes wrong: founder treats Steuben Part A as a launch license.

How you catch it: §10 and the Certificate stop rules. Any public act is an incident.

What goes wrong: founder creates a helper to "own community" and opens Skool.

How you catch it: transfer rule plus file 10 banner. No helpers from this packet. Community is NOT LIVE.

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Napoleon (command); Steuben (gate and kill authority); Jomini (actions 1–2, sleep numbers); Smith (funnel and 7-day first-win); Monash (price, unread here) Evidence: Davout tasking 20 August 2026 (KST); Steuben legal/01-sign-off-certificate.md (domain draft); Hormozi Retention methods via hormozi-method-cards.md. Consensus Sleep Diary field names after Carney et al., 2012 (instrument names only). Trauer 2015 named for TST-flat-early; no statistics invented. Confidence: 0.88 Residual uncertainty: Slim unpublished. Blue Book siblings 07–25 (agreement, refund, community rules, testimonials) are not in Davout's hands; cancel/refund steps in file 07 stay process-only and do not invent percents. Jomini module list unpublished; min-path ticks may be extended later without renaming the six daily ticks in file 03.

Accountability and stay-with-it system (spine)

Davout: first 5 to 10 clients, founder-run

Internal draft. NOT LIVE. No client data. No community. No live count sheet with names. This is practice paper. Do not run real clients yet.

---

Rule

Hold daily habits with four instruments: diary plus ticks, exception list, 2×/week reach-out, exit script. A diary is the morning form where the client writes last night's sleep times. Ticks are yes/no marks that they did each assigned habit that day. Translate Hormozi's 5 Horsemen and 9-item Churn Checklist into sleep-behavior terms. Leave gym examples in the gym. Do not import gym churn percentages. Do not set a "save %" target.

Stop rule (20 August 2026). Standing founder-to-client messaging = the 2 named diary replies each week. The daily batch is a silent scan. 48h diary silence is re-engagement (file 08), not a fifth standing note. No daily note loop. Client-initiated overflow waits for the next named slot or the weekly session. Do not answer overflow by inventing extra standing notes.

---

1. The min-path (closed)

At n = 5 to 10, the founder runs only:

1. Consensus Sleep Diary night + protocol ticks (file 03).
2. Exception list (file 03).
3. Two named reach-out slots per client per week (file 04).
4. Exit interview on every cancel request (file 07).

Digital tracking, video/async check-ins, and Skool-or-equal are designed in this packet. They are not live.

---

2. Attendance definition (doctrine)

A night counts for attendance only when both are true:

• the Consensus Sleep Diary night row is filled (required night fields in file 03), and
• protocol ticks for that calendar day are marked (yes/no plus exception code if used).

Derived TIB / TST / SE may be computed later by the founder or a tool. TIB is time in bed. TST is total sleep time. SE is sleep efficiency (sleep time divided by time in bed). They do not decide attendance. Wearable scores do not decide attendance. Hours slept do not decide attendance.

---

3. Horsemen mapped (method, translated)

H1. Track attendance / usage; intervene at first drop

Sleep translation: Scan diary+ticks daily in one batch. First drop = Trigger A (no diary night for 48 hours) or Trigger B (window broken 3 consecutive nights). A window is the assigned hours they may be in bed. Watch: 3 broken nights in 7. Same-day reach-out (file 08).

Instrument: Morning batch scan, 15 minutes for all clients at n=10 (see §8). Columns in file 03.

H2. Reach out ~2×/week: praise + solve small friction. ACA

Sleep translation: Two named slots per client per week. Mix: one async ACA, one live/video or voice note. ACA means acknowledge, compliment, ask. Each slot ends ≥3 hours before that client's assigned window open. Never after 20:00 in the client's local time. Praise attendance and protocol ticks, never hours slept. Solve one friction (form too long, rise-time clash, travel). Do not process feelings as therapy.

Instrument: File 04. Six scripts plus safety-redirect.

H3. Handwritten (or physical/digital equivalent) notes at start and milestones

Sleep translation: Start, D21, D42, D63. Physical card preferred. Digital note allowed on the online min-path. No health data on cards. Allowed: client name or client_code (a short ID like C-001, used instead of a name on work sheets), milestone label, one human sentence about showing up, founder signature.

Instrument: File 05.

H4. Member events on a regular internal cadence (random to the client)

Sleep translation: Day 21 / 42 / 63 of the client's start (or group start). Online video. English. Afternoon or early evening so the event ends ≥3 hours before window open. Never after 20:00 local. Never inside the window. Never a late-night hang. Adapt the 21/42/63 idea so events protect sleep. Until community is live and Legal lifts the banner, the founder runs the same agenda 1:1.

Instrument: File 06.

H5. Exit interview required

Sleep translation: Attempt on 100% of cancel requests. Resell process (habit hold, subtraction, pause) when it is honest. Learn. Give money back if they ask, per Steuben/Monash policy when it exists; do not invent a percent. Do not sell a results guarantee to keep them. Do not set "save about half" as the number we watch. The save metric is attempt rate.

Instrument: File 07.

---

4. Churn Checklist mapped (9)

---

5. Who does what

n = 5 to 10 (now)

Later (only after Legal, after activation discovery, after time budget still fits)

---

6. Cadence map (one client)

Assume start_date = kickoff day (Smith finishes kickoff; Davout clock starts hour 0).

If timezone unknown: treat the client as Asia/Seoul until confirmed. Default event clock 14:00–16:00 KST (file 06).

---

7. Count sheet fields (stay-with-it half)

One row per client_code per container. Dummy headers only. No sample people.

Identity / join (shared with Jomini and Smith)

• client_code (preferred over name on operational sheets)
• start_date
• container_day (derived: tonight's date minus start_date + 1)
• tz_name
• window_open_local
• window_close_local
• smith_kickoff_done (yes/no)
• legal_screen_clear (yes/no). If no, do not coach

Attendance / hold

• nights_assigned
• nights_attendance_true (diary filled AND ticks marked)
• attendance_rate
• window_held_days
• window_assigned_days
• adherence_rate
• exception_count by code: travel | illness | safety | caregiving | work_critical | other
• silent_48h_events
• window_break_3consec_events
• watch_3in7_events

Reach-out

• slots_planned_this_week (2)
• slots_done_this_week
• reachout_response_rate (replies / touches, rolling 28 days)
• reengage_touches_last_7d (cap 3)

Official Day-7 first-win (Slim ops/03; do not merge with H)

• slim_d7_first_win (a | b | c | miss)
• slim_d7_code (which of a/b/c hit, if any)

Activation candidates (A–J, yes/no + date; none is "the" point)

• act_A_first_csd through act_J_can_state_rules (see file 09)
• act_H is the all-three guess we will test after the first group reaches day 42. It is not slim_d7_first_win.

Safety / subtract / exit

• safety_refer_flag (yes/no + date)
• window_stopped_for_safety (yes/no)
• overwhelm_subtract_n
• pause_start / pause_restart / pause_reason
• cancel_request_date
• exit_attempt_done (yes/no). Floor = 100% of requests
• exit_outcome (stayed_process | pause | refund_path | fire | refer | silent)
• core_container_complete (yes/no)
• core_complete_vs_56_floor (cohort rollup, not a client shame field)

Optional path (never required for happy)

• proof_opt_in (yes/no)
• refer_peer_n
• ascend_offer_shown (yes/no)

Do not put on this count sheet as Davout judgments

• hours slept, TST as a win, "cured," AHI, wearable scores, ISI value as a stay-with-it trophy

Jomini may later join isi_t0, isi_t_end, SOL/WASO/SE direction on the same client_code. See file 11.

---

8. Founder time budget at n = 10

Honest capacity: a few clients at a time, one founder. At 10 clients the math is tight.

Raw live-heavy math (command floor in the tasking):

2 touches × 10 clients × about 12 min ≈ 240 min = 4.0 hours/week, plus diary scan.

Diary scan if unbatched: 10 × about 2 min × 7 ≈ 140 min ≈ 2.3 hours/week. Total ≈ 6.3 hours/week. A solo founder who also sells and does Legal can fail here.

Cut-scope rule (this spine): if delivery time exceeds 5 hours/week for 2 consecutive weeks, cut to async-first. Do not hire a fake community to hide the load.

Async-first budget (required default at n=10):

Further cut if needed:

1. Voice note replaces live except flags and D21/42/63.
2. Diary batch stays 15 min. Founder does not write a nightly essay in comments.
3. No community. No extra modules. No daily office hours.
4. Veto any bonus that adds a standing 10-minute/client task.

If even the cut does not fit, take fewer clients at a time, do not thin the hold. Napoleon owns the client-cap decision. Davout reports the hours.

---

9. Spend note (method, not budget)

Hormozi method: keep spend on stay-with-it work ≈ 1/5 of CAC.

This packet does not lock a budget, a CAC, or a currency amount. Cards, postage, and a video tool are the likely min-path costs. They wait on Monash + founder cash math. Do not spend on a community platform before Steuben lifts NOT LIVE.

---

10. Stop rules (spine)

1. Safety flag → stop window → refer. Paid status does not win.
2. Legal stop rule closed → no data, no community, no invoice from Davout.
3. Second diary refusal after the one correction → fire.
4. Client demands a cure or a clinician → fire or refer. Do not re-sell.
5. 3 re-engagement touches in 7 days, then one extra 2×/week slot, then pause letter or exit attempt (file 08).
6. Event would end inside 3 hours of window open or after 20:00 local → move or cancel the event.
7. Bonus fails the veto checklist (charter §9) → veto.
8. Founder is about to widen the window to please in week 1–2 → stop. Run script 2. Safety check. Hold.

---

What goes wrong / how you catch it (spine)

What goes wrong: founder tracks a wearable "sleep score" because the diary feels slow, then praises 87/100.

How you catch it: attendance definition in §2. Wearable is not attendance. Remove the column if it appears.

What goes wrong: founder sets a watch-number "save 50% of cancelers" from gym memory.

How you catch it: §3 H5 and charter metrics. Only attempt rate is the floor.

What goes wrong: 2×/week live for 10 clients plus sales calls. Founder ghosts Friday slots.

How you catch it: §8 hours log. Two missed Friday slots in a week = cut to voice note the next week.

What goes wrong: D42 group "celebration" at 21:30 client-local.

How you catch it: file 06 clock rules. Cancel and reschedule.

What goes wrong: completion marketed as "most clients finish."

How you catch it: comparison is beat about 56% automated dCBT-I. No 90%. No public claim until Steuben claims matrix exists.

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Smith (72h / 7-day); Jomini (protocol and sleep numbers, files pending); Steuben (gate); Monash (price / spend) Evidence: Hormozi Retention Playbook methods (5 Horsemen, 9-item checklist, overwhelm as #1 churn reason, stay-with-it spend ≈ 1/5 CAC as method note) via hormozi-method-cards.md. Command floors from Davout tasking 20 August 2026 (KST). Automated dCBT-I completion about 52–60% cited as failure floor / about 56% operating comparison; not a new study statistic invented here. Trauer 2015 named for TST-flat-early only. Confidence: 0.84 Residual uncertainty: True founder hours will show after week 1 of a live group; the 5.5-hour cut is a plan, not a measurement. Jomini may add ticks; the attendance AND-gate stays. CAC is unknown; 1/5 spend stays a note.

Attendance instrument

Consensus Sleep Diary + protocol ticks + exception list

Internal draft. NOT LIVE. No live sheet. No cloud workbook. No sample rows with names, emails, or diary numbers that look like a person. Dummy column headers only. This is practice paper. Do not run real clients yet.

---

Rule

A night counts for attendance only when the Consensus Sleep Diary night is filled and that day's protocol ticks are marked. The Consensus Sleep Diary (diary) is the morning form where the client writes last night's sleep times. Ticks are yes/no marks that they did each assigned habit that day. Derived TIB / TST / SE do not decide attendance. TIB is time in bed. TST is total sleep time. SE is sleep efficiency (sleep time divided by time in bed). Wearables do not decide attendance. Hours slept do not decide attendance.

Do not compute a clinical diagnosis from these fields. Do not print derived numbers on milestone cards.

---

1. Why the diary is the instrument (one correct you may say)

Copy-paste if a client asks why they must write nights down:

"The diary is how we both see whether the protocol was done. I do not diagnose. I do not score you as ill. I need the night filled and the ticks marked so we know you showed up. If the form is too long, we cut comments first. We do not drop the diary."

Second refusal after onboarding → fire (file 07).

---

2. Night fields (Carney et al., 2012 Consensus Sleep Diary)

Use these names so Jomini can attach scoring later. Do not rename.

A night row is filled when every required field above has a value. Empty comments_optional is fine.

Founder does not rewrite a client's times to make SE look better.

---

3. Derived fields (founder or later tool; never on cards)

Compute only after Legal allows a working sheet. Do not show these on milestone notes or in community.

Davout may record that a derived column exists. Davout does not praise "you slept 7 hours" from it.

---

4. Min-path protocol ticks (until Jomini publishes the module list)

Align to Jomini's one core path: window + stimulus control + circadian + diary. A window is the assigned hours they may be in bed.

Daily ticks. Each is yes / no plus an exception code if the tick is no-for-cause.

attendance_bool = diary_filled AND all required ticks marked (yes or no, not blank). Blank tick = night does not count.

Required ticks on min-path: all six named above. Jomini may later mark some optional. Until that file exists, all six are required to be marked. A no still counts as marked. A blank does not.

window_held = no for 3 consecutive night_date values → Trigger B (file 08).

---

5. Exception codes (operational, not a diagnosis)

Allowed codes only:

Exception list is a separate founder sheet (dummy headers below). One row per exception event.

Columns:

• client_code
• night_date
• exception_code
• note_one_line (no diagnosis language, no medication names if avoidable)
• window_broken (yes/no)
• logged_at (founder timestamp, KST or client-local labeled)

Do not write "client has apnea" in note_one_line. Write "client reported breathing pauses; window stopped; refer path sent."

---

6. Founder spreadsheet column spec (dummy headers only)

Do not create the live workbook until Steuben opens collection. When you do, one book, two tabs. No third tab of "ideas."

Tab nights (one row per client_code × night_date)

client_code
night_date
container_day
bed_time
try_sleep_time
sol_min
awakenings_n
waso_min
final_wake_time
out_of_bed_time
sleep_quality_1to5
comments_optional
diary_filled
window_held
stimulus_control
circadian_anchor
wind_down_done
no_clock_checking
exception_code
attendance_bool
tib_min
tst_min
se_pct

container_day is a join key for file 11. isi_t0 and isi_t_end do not live on the night row. They live on the client tab.

Tab clients (one row per client_code)

client_code
start_date
tz_name
window_open_local
window_close_local
legal_screen_clear
smith_kickoff_done
isi_t0
isi_t_end
assigned_rise_rule
assigned_light_rule
core_container_complete
safety_refer_flag

isi_t0 / isi_t_end: Jomini fills. Leave blank. Do not invent scores.

Tab exceptions (one row per event)

client_code
night_date
exception_code
note_one_line
window_broken
logged_at

Tab activation (one row per client_code)

See file 09 for candidate columns act_A … act_J plus persist_42 and persist_42_scored_on.

---

7. Daily founder scan (15 minutes at n=10)

Rule: one pass, morning, founder-local. Do not open each diary as a counseling session.

Stop rule (20 August 2026). This scan is silent. Do not send a daily note. 48h silence fires file 08 (re-engagement), not a fifth standing slot. Standing founder-to-client messaging = 2 named diary replies/week.

Checklist:

1. Filter nights where night_date = yesterday (client-local).
2. Count rows missing vs active (non-pause, screen-clear) clients.
3. Any client with no filled night last 48 hours → Trigger A. Same-day reach-out (file 08).
4. Any client with window_held = no on the last 3 consecutive nights → Trigger B. Same-day reach-out.
5. Any client with 3 window_held = no in the last 7 nights → watch. Mention in the next 2×/week slot. Do not start the 3-touch re-engagement sequence on watch alone.
6. Any exception_code = safety → stop window, refer, do not scan further for "saves."
7. Tick attendance_bool if the AND-gate holds.
8. Stop. Do not write a clinical summary.

If the scan exceeds 20 minutes, you are reading comments as therapy. Stop reading comments in the batch. Pull comments only on reach-out.

---

8. How the client submits (design, not live)

Until Legal opens collection, the founder does not send a form.

After the gate, pick one submission path. Do not pick three.

Recommended min-path (decision, revisable):

1. Client fills a daily message in the same private channel Smith used for kickoff (format card below).
2. Founder copies into nights the same morning.

Do not put diary numbers in a community room (file 10).

Format card the client can paste (after Legal; no live form now):

night_date:
bed_time:
try_sleep_time:
sol_min:
awakenings_n:
waso_min:
final_wake_time:
out_of_bed_time:
sleep_quality_1to5:
comments_optional:
window_held: yes/no
stimulus_control: yes/no
circadian_anchor: yes/no
wind_down_done: yes/no
no_clock_checking: yes/no
exception_code: travel|illness|safety|caregiving|work_critical|other|none

diary_filled is computed by the founder. Client does not self-score attendance.

---

9. Join keys (repeat for Jomini)

Shared, do not collide:

• client_code
• night_date
• container_day
• isi_t0 (client tab, Jomini fills)
• isi_t_end (client tab, Jomini fills)
• attendance_bool
• ticks as named in §4
• exception_code

Davout will not add parallel names (sleep_onset_latency, WASO_minutes, eff). If Jomini needs aliases, Jomini publishes a map. Until then these names win.

---

10. What this instrument is not

• Not a diagnosis of insomnia disorder.
• Not a STOP-BANG or AHI tool.
• Not a wearable ingest.
• Not a public leaderboard.
• Not live.

---

What goes wrong / how you catch it (attendance)

What goes wrong: founder accepts a wearable export in place of CSD because "the data are better."

How you catch it: § Rule. Attendance AND-gate needs CSD + ticks. Wearable may sit in a later Jomini annex. It does not replace this instrument.

What goes wrong: founder marks attendance_bool = yes when ticks are blank "because they usually do it."

How you catch it: blank ≠ marked. Weekly audit: 5 random nights, confirm AND-gate.

What goes wrong: comments fill with medication lists and get pasted into a milestone card.

How you catch it: file 05 ban list. Comments stay on nights. Cards get one human sentence about showing up.

What goes wrong: a "test" friend fills the paste card before Legal opens.

How you catch it: if a real handle appears, it is a collection incident. Delete. Tell Steuben same day (KST).

What goes wrong: founder computes SE and tells the client "your efficiency is 61%, that is clinical insomnia."

How you catch it: forbidden language. Davout does not diagnose. Jomini owns number talk. Founder may say "we look at whether you held the window and filled the night."

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Jomini (CSD scoring, TST/SE interpretation, future module ticks); Smith (scorecard live as day-7 first-win); Steuben (collection gate, sensitive-information consent when siblings exist) Evidence: Consensus Sleep Diary night items named after Carney et al., 2012 (field names for joint use; this file is not a reprint of the instrument). Trauer 2015 named for TST-flat-early; no extra statistics. Command floors: 48h silence, 3 consecutive window breaks, attendance AND-gate. Confidence: 0.87 Residual uncertainty: Exact TST formula and which circadian tick Jomini will require (light vs rise) are unpublished. Min-path records both as assigned. Paper CSD copyright/license for a future client-facing PDF is a Steuben/Jomini item; this file only names fields and does not attach a form.

Reach-out cadence and ACA scripts

Internal draft. NOT LIVE. Do not send these to a real person until Legal opens collection and a paid, screen-cleared client exists. Scripts are spoken English for after the gate. This is practice paper. Do not run real clients yet.

---

Rule

Two named slots per client per week. Acknowledge, compliment, ask. Praise attendance and ticks, never hours slept. A diary is the morning form where the client writes last night's sleep times. Ticks are yes/no marks that they did each assigned habit that day. Reach-out is not therapy. Every message includes a safety abort line. If a safety flag appears, drop ACA and run the safety-redirect. ACA means acknowledge, compliment, ask. Stay-with-it work does not override stop-and-refer.

Stop rule (20 August 2026). Those two named slots are the standing diary replies. Script 3 (48h silence) and file 08 are re-engagement, not a fifth standing note. Do not add a daily note loop. A kickoff Script 1 may count as that week's first diary reply if it is a diary reply. Do not stack welcome + two weekly notes + 48h as four standing slots.

---

1. Calendar construction

Name the slots

Pick two weekdays and keep them. Example pattern (not a client list): Tue async + Fri voice or live.

Write on the founder calendar, for each client_code (a short ID like C-001, used instead of a name on work sheets):

• slot_1_weekday + slot_1_local_time
• slot_2_weekday + slot_2_local_time

Clock rules (same as events)

• Slot ends ≥3 hours before that client's current assigned window_open_local. A window is the assigned hours they may be in bed.
• Never after 20:00 in the client's local time.
• Never inside the window.
• If tz_name unknown: Asia/Seoul, 14:00–16:00, then confirm. Do not guess a late slot.

Mix

• One async ACA (typed, ≤5 lines, about 5 minutes founder time).
• One live/video or voice note (10–15 min live; 3–8 min voice). At n=10 default to voice unless a flag or D21/D42/D63.

Length

• Live: 10–15 minutes. Timer visible. End on time.
• Async: 5 lines. If you need a sixth, you are counseling.

Batching (time budget)

Tuesday block: write all async ACAs in one sitting (10 × 5 min = 50 min). Friday block: voice notes in one sitting, flags first.

If a Friday live would run past the clock rule, send voice instead. Do not move the slot into the evening.

---

2. ACA structure (doctrine)

1. Acknowledge: one fact they did or a friction they named. No "I hear how hard insomnia is."
2. Compliment: showing up, a tick, a diary night, stating the rule in their words. Never "great sleep last night" unless you are talking about a tick, and even then prefer "you held the window."
3. Ask: one question that produces the next action. One. Not three.

Then the safety abort line (required on every outbound). Then stop.

---

3. Safety abort line (required block)

Paste at the end of every async. Say at the end of every live, or sooner if a flag appears mid-call.

Async paste:

"If breathing pauses, gasping, legs that force you up, heavy sleepiness when you must be alert, a swing into very little sleep with unusually high energy, a seizure, pregnancy, or safety-critical work is in play, stop the protocol and contact a physician. I do not diagnose. I will pause coaching and send the referral path."

Live / voice, shorter:

"If any of the safety items we listed at the start show up, we stop the window and I refer. I do not diagnose. Tell me if one is in play."

If they say yes, leave this file and run §9.

---

4. What you never say

• "How is your insomnia?"
• "We will get you to 8 hours."
• "This is treating your disorder."
• "I'm worried about your insomnia."
• "Your efficiency is in the clinical range."
• Medication advice, supplement advice, device advice.
• A promise to stay until a physiological result.

---

5. Six copy-paste scripts

Each script: async form first, then live beats. Safety line is assumed at the end (async: paste §3; live: short line).

Script 1: First 72 hours welcome

When: Hour 0 to hour 36 after kickoff. Does not replace Smith's invoice/kickoff path.

Async:

"You are in. Today is about the first night row and the ticks, not about a perfect night.

You showed up for kickoff. That is the part I care about today.

Will you send tonight's diary card after you are out of bed tomorrow, and mark the six ticks, even if the night felt rough?"

Live beats (10 min):

1. Acknowledge: kickoff done, they are in.
2. Compliment: they completed the first human step.
3. Ask: confirm window times in their words; confirm "out of bed if not sleepy."
4. Show the paste card (file 03). Do not add modules.
5. Safety short line. End.

Stop rule: if they cannot state the window, do not add hygiene content. Repeat the window. Candidate J is not yet yes.

---

Script 2: Week 1–2 window misery

When: Client reports misery, "I still wake," or asks to widen the window in the first 14 days. Safety must be clear first.

Async:

"Week 1 and 2 often feel worse on the clock. Time in bed is tight on purpose. Total sleep can sit flat while the nights get more consolidated. That pattern is expected. We do not widen the window to make tonight nicer.

You held the conversation and you filled last night. That is the work.

Any of the safety items from the start in play? If no, we hold the assigned window. What is one tick that was hardest last night: staying out of bed until the window, or getting out if you were not sleepy?"

Live beats (12 min):

1. Safety short line first, not last, if they sound rattled.
2. Acknowledge: misery is expected in week 1–2. Do not argue feelings.
3. Rationale: window is the protocol. TST often flat early; we watch whether they held the window and filled the diary. TST is total sleep time. Jomini owns number talk if they ask for study detail. You may name Trauer 2015 for "TST can stay flat early." You do not recite invented percents.
4. Compliment: any held night or honest tick.
5. Ask: one friction to solve (clock in the room, wind-down start time). Do not change window_open_local.
6. End on time.

Stop rule: widening the window to please is a protocol abandonment. If you feel yourself about to offer it, stop talking. Write "hold" on the scorecard.

---

Script 3: Silent 48h diary

When: Trigger A. Same day. Async first.

Async:

"I do not have a night row from you for 48 hours. I am checking the instrument, not your character.

You were current before this gap. I want you back on the card.

Can you send last night's row today, even if it is messy, or reply 'pause' if life blew up?"

Live / voice if no reply to async by end of founder day:

"Two nights missing. I need the card or a pause request. I am not here to talk you through feelings. Are you filling tonight, or do we pause with a restart date?"

Then file 08 sequence. Cap 3 touches in 7 days.

---

Script 4: Window broken 3 nights

When: Trigger B = 3 consecutive window_held = no. Same day. (3-in-7 is a watch, next regular slot, not this script.)

Async:

"Three nights in a row the window was not held. That is the drop I watch.

You still sent diary rows. Thank you for the record.

What broke it: early into bed, late out, or time in bed outside the window for another reason? Reply with the reason and whether a listed exception applies (travel, illness, safety, caregiving, work_critical, other). If safety, we stop."

Live beats (12 min):

1. Safety first.
2. Acknowledge the three nights as a fact.
3. Compliment the diary if it was filled. If diary also failed, you are in file 08 dual trigger; keep one ask.
4. Ask one cause. Solve one friction. Do not widen the window in week 1–2.
5. If life shock: offer pause (file 07) with restart date and diary-min = rise time only if safe.
6. End.

---

Script 5: Praise for showing up (attendance, not hours)

When: Regular 2×/week slot when no flag. Default Friday voice or Tuesday async.

Async:

"I have [N] attendance nights this week (diary plus ticks). That is the official count I use.

You did the unglamorous part: you wrote the night down and you marked the ticks.

One ask: what friction should we subtract so next week is lighter? Name one thing to remove, not one thing to add."

Replace [N] only with a count of attendance_bool = yes. Do not put TST, SE, or ISI in this message.

Live beats (10 min):

1. Read the attendance count, not the sleep hours.
2. Compliment one specific tick (example: they got out of bed when not sleepy).
3. Ask keep-one / remove-one if it is a survey week; otherwise ask one friction.
4. Safety short line. End.

---

Script 6: Overwhelm subtract

When: Client says there is too much, or comments show module pile, or they ask for extra content.

Async:

"Overwhelm is how people leave. We subtract before we add.

You are still here and you told me it is too much. That is useful.

We will keep window, stimulus control, circadian anchor, diary. Hygiene stays a module, not the program. Which extra should we drop this week: extra reading, extra tracking, or extra live time?"

Live beats (12 min):

1. Acknowledge load.
2. Compliment the report. Reporting overwhelm is attendance to the process.
3. Subtract on the call. Write the new required tick set on the scorecard. Do not add a bonus to "make it worth the price."
4. Offer a defined pause if they cannot run the core four (window + SC + circadian + diary).
5. Safety short line. End.

Stop rule: do not soothe by adding a meditation pack, a new app, or a wearable.

---

6. If/then for which script

---

7. Live session agenda (10–15 min)

1. Clock check: does this session still end ≥3h before their window? If no, switch to async and reschedule.
2. Safety: "Any safety item in play?" If yes → §9.
3. Attendance fact (count, not hours).
4. One compliment on a tick or on showing up.
5. One friction. One decision.
6. Confirm next slot.
7. Safety short line. End.

No dream-outcome close. No testimonial ask on a bad week. Proof is optional and later (file 11).

---

8. Founder log (dummy fields)

client_code
touch_date
touch_slot (1|2)
channel (async|voice|live)
script_id (1-6|safety|exit|other)
safety_line_included (yes/no)
response (yes|no|flag)
minutes

No quotes of health data in other. If you must note a flag, write the category: safety_refer.

---

9. Safety-redirect script (stop + refer)

When: any safety item at screen leftover, or mid-program: breathing pauses / gasping, RLS-type forced movement, high sleepiness in a risk setting, bipolar/mania signs as the client describes little sleep plus unusually high energy, seizures, safety-critical work, pregnancy.

Rule: STOP the assigned window. Do not "ease" the protocol as a medical substitute. Do not diagnose. Refer. Log safety_refer_flag. This is a success metric when indicated.

Spoken:

"I am going to stop the sleep-window protocol today. I do not diagnose, and I do not treat medical conditions. What you described sits outside coaching. The next step is a physician or a somnologist. I will send the generic referral path we use: see a licensed physician; ask about sleep. I will not name a hospital for a fee and I will not keep you on the window to be polite.

Coaching is paused. Paid status is not a reason to continue. If you want the written pause terms, I will send them after I send the referral line."

Async if they wrote the flag:

"I received what you wrote. I am stopping the window protocol. I do not diagnose. Please contact a physician. I will send the generic referral path and pause coaching. I will not keep you on habit hold through this."

Then: write Steuben's screen/referral SOP steps when that SOP is live. Until it is live, send only the generic unpaid line: see a licensed physician; this is not an introduction to a named clinic. Korean MSA forbids paid patient referral. Do not improvise a hospital list.

Escalate to Steuben the same calendar day (KST). Napoleon if the client demands to continue the window.

Never:

• "Let's try three more nights and see."
• "I'm worried about your insomnia."
• A differential diagnosis.
• A named doctor you get paid to recommend.

---

What goes wrong / how you catch it (reach-out)

What goes wrong: founder sends a warm 400-word essay at 22:30 client-local.

How you catch it: clock rules + 5-line cap. If send-time is after 20:00 client-local, do not send. Wait for the next legal slot.

What goes wrong: Script 2 ends with "fine, add 30 minutes to the window."

How you catch it: stop rule in Script 2. Scorecard window_open_local is unchanged without Jomini + safety.

What goes wrong: founder skips the safety line because the client "already knows."

How you catch it: safety_line_included must be yes. Audit 3 random touches a week.

What goes wrong: 2 live sessions × 10 clients = 4+ hours, plus sales. Friday slips.

How you catch it: file 02 budget. Voice is the default second touch.

What goes wrong: ACA becomes therapy ("tell me about the fight with your partner").

How you catch it: one ask, and the ask is a tick or a subtract. Partner content → one line, then back to protocol or pause.

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Smith (first 72h sits next to Script 1; Smith owns DM → calendar → Zoom → invoice → kickoff); Steuben (referral SOP, claims); Jomini (rationale numbers if the client asks beyond Trauer 2015 name) Evidence: Hormozi ACA + 2×/week method via method cards. Command floors: same-day on 48h / 3-night; clock rules; reach-out is not therapy. Trauer 2015 named only in Script 2. No extra stats. Confidence: 0.85 Residual uncertainty: Exact generic referral paragraph will be replaced by Steuben document 05 language when counsel-cleared. Until then the spoken stop in §9 is the hold. Channel for async (email vs DM) is Smith's after the gate; Davout does not open a new inbox.

Milestone notes

Start / D21 / D42 / D63: no health data on cards

Internal draft. NOT LIVE. Send-log with real client identifiers waits on Blue Book. Do not mail a card to a prospect. Do not print ISI or diary numbers "as a demo." This is practice paper. Do not run real clients yet.

---

Rule

A note marks that the person showed up at a named milestone. A diary is the morning form where the client writes last night's sleep times. Ticks are yes/no marks that they did each assigned habit that day. A window is the assigned hours they may be in bed. It is not a medical report. It is not a results certificate. It is not a testimonial ask. Physical card preferred. Digital note allowed on the online min-path. No health data on the card. Restart Card after a messy night is file 14. File 05 owns cheer notes.

---

1. When to send

If the client is on a safety pause, do not send a cheer card. Send nothing about "progress."

If the client has canceled, do not send D42/D63 as a win-back stunt. Exit interview first (file 07).

---

2. Allowed on the card

• Name (or first name only). If you can avoid a full legal name on a postcard that travels, do.
• Milestone label: Started / D21 / D42 / D63
• One human sentence about showing up
• Founder signature: 이성재
• Optional: city of the practice (Seoul) as sender, not as a clinic

3. Banned on the card

• ISI
• SOL, WASO, SE, TST
• "You slept X hours"
• Diagnoses or suspected diagnoses
• Medication names
• Apnea, AHI, wearable scores
• Any diary number
• "This treated your insomnia"
• A request for a testimonial
• A coupon that implies a results guarantee

---

4. Copy bank (one sentence each)

Pick one. Do not stack. Do not personalize with a sleep number.

Started

• "You started the protocol and you showed up for the first hold."
• "The first night row is the start. Thank you for starting."
• "Glad you are here. We will count nights you fill and ticks you mark."

D21

• "Twenty-one days in. You kept showing up for the window and the diary."
• "Protocol installed is a showing-up fact. Thank you for the three weeks."
• "You stayed through the hard early stretch. That is the work I am writing down."

D42

• "Day 42. You are still here. That is what this note marks."
• "Six weeks of showing up is rare enough to write by hand."
• "Still here. We subtract what is too much. We do not add a pile."

D63

• "Core container closed. You completed the usable path."
• "Sixty-three days of holding the habit. Thank you."
• "Clean close. You showed up. What comes next is your choice."

Do not write "you will sleep 8 hours if you continue."

---

5. Physical vs digital

Physical (preferred when you have a postal address after Legal + consent):

1. Plain card. No logo that says "clinic" or "therapy."
2. Handwritten sentence from §4.
3. Signature.
4. No extra flyer.

Digital (allowed for online-only min-path):

1. Same sentence. No emoji pile.
2. Private channel only. Not a community post.
3. No screenshot of their diary attached.

If you do not have a lawful address, send digital. Do not scrape an address.

---

6. Send-log (after Blue Book only)

Dummy headers. No names in this draft.

client_code
milestone (Started|D21|D42|D63)
date_sent
channel (physical|digital)
address_used (yes/no)   # do not store the address in this log if a privacy sheet exists elsewhere
health_data_absent (yes)  # if you cannot tick yes, do not send

Prefer client_code (a short ID like C-001, used instead of a name on work sheets) over name in the log.

Until Blue Book: keep this as headers on paper in Week 0 rehearsal. Do not fill a row.

---

7. Founder checklist before send

1. Screen still clear? If safety pause, stop.
2. Milestone date actually reached?
3. Sentence from the allowed bank or a new sentence that still contains zero numbers?
4. Banned list re-read?
5. health_data_absent = yes?
6. Send-log row ready (after gate only)?
7. Send in the client's afternoon if digital, so it does not land inside the window. A window is the assigned hours they may be in bed. Same clock rule as reach-out: not after 20:00 local.

---

What goes wrong / how you catch it (notes)

What goes wrong: founder writes "SE up 12 points, proud of you" because it feels kind. SE is sleep efficiency.

How you catch it: banned list. Tear the card up. Rewrite from §4.

What goes wrong: D63 card includes "reply with a two-sentence testimonial."

How you catch it: testimonials are optional, consented, never a condition, and never on the milestone card (file 11).

What goes wrong: cards go out from a printer that also stores a CSV of ISI scores.

How you catch it: send-log holds code + date + milestone only. Health fields stay on the nights sheet.

What goes wrong: founder mails a "Started" card to a friend to test postage before Legal.

How you catch it: that friend is a data subject if you stored a name and address. Do not test with real people. Test with your own name to yourself if you must test postage.

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Steuben (PIPA, address as personal information, testimonial protocol later); Smith (kickoff date that starts the Started clock); Monash (no discount language on cards) Evidence: Hormozi handwritten-note method, translated. Command constraint: no health data on cards. PIPA-first from Steuben Part A: address and name are personal information; collection stays closed. Confidence: 0.90 Residual uncertainty: Postage vendor and whether a Seoul operator may mail internationally wait on Steuben processor list (Blue Book sibling 14). Digital-only is the default until that list exists.

Event calendar: day 21 / 42 / 63

Internal draft. NOT LIVE. Do not create a group event, a public calendar, or a late lounge. Until community NOT-LIVE is lifted AND Legal has signed AND the client has hit an activation candidate, the founder runs these agendas 1:1. This is practice paper. Do not run real clients yet.

---

Rule

Internal cadence is day 21, 42, and 63 of the client's start (or a shared group start). The dates are regular to the founder and feel unplanned to the client. Events are online video, English, habit/protocol themed. They never break the sleep window. A window is the assigned hours they may be in bed. They never promise 8 hours.

---

1. Clock rules (hard)

1. Schedule in the client's local afternoon or early evening.
2. The event ENDS at least 3 hours before current assigned window_open_local.
3. Never after 20:00 in the client's local time.
4. Never inside the window.
5. Never a "late-night hang," voice room, or after-hours lounge.
6. If tz_name is unknown: default Asia/Seoul 14:00–16:00 and confirm before holding.
7. If the only time the client offers violates 1–5, do not hold the event. Send the agenda async and keep the 2×/week slot.

These rules outrank "they said evenings are easier."

---

2. Who attends, when

Group events only after all of: activation candidate marked by founder, Legal sign-off for community, community NOT-LIVE lifted. Until then, 1:1.

Do not invite a waitlist. Do not record a public webinar.

---

3. How to place dates

Offset from start_date (kickoff, Smith).

If a group shares a start, use group day. Write which rule you used on the client tab (event_offset_basis = client or cohort). Do not mix mid-stream.

Move by ±2 days if the clock rule requires it. Do not move into week 1 to "make it special."

Founder calendar: create three template offsets per client_code (a short ID like C-001, used instead of a name on work sheets) after kickoff. No guests attached until the week of the event.

---

4. Agenda D21: Protocol installed

Theme: Window + stimulus control + diary are in. A diary is the morning form where the client writes last night's sleep times. Misery is expected. Rationale refresh. Hygiene remains a module.

Not the theme: "You will sleep 8 hours." "The treatment is working."

Agenda (1:1, 20–25 min)

1. Clock check (2 min). Confirm end time vs window. If violation, abort and reschedule.
2. Safety (2 min). Any flag → stop window, refer, end event (file 04 §9).
3. Attendance fact (3 min). Count of attendance_bool nights in 21 days. No TST speech. TST is total sleep time.
4. Misery / rationale (6 min). Week 1–2 (and often still) can feel worse on the clock. TST often flat early; SE rising is the pattern Jomini will talk in numbers. SE is sleep efficiency (sleep time divided by time in bed). You may name Trauer 2015 for TST-flat-early. Hold the window. Do not widen to please.
5. One friction (5 min). Subtract if overwhelmed. Confirm they can state window + "out of bed if not sleepy" (candidate J).
6. Close (2 min). Next 2×/week slots. Safety short line. No testimonial ask.

Founder checklist after: mark D21 done; send milestone note (file 05); update activation candidates if J flipped to yes.

---

5. Agenda D42: Still here

Theme: They stayed. Subtract modules if overwhelmed. Optional consented lifestyle proof. Persistence score for activation discovery.

Not the theme: Mid-treatment exam. "Your ISI should have dropped."

Agenda (1:1, 20–25 min)

1. Clock check. Safety.
2. Attendance fact for days 1–42.
3. Overwhelm pass (file 04 script 6). Remove one thing if they cannot name a keep-one.
4. Activation log: which of A–J have dates. Do not announce "you are activated because of H."
5. Persistence mark: persist_42 = yes if they are still in the container on day 42 (not canceled, not safety-stopped unless they later restarted). This is the discovery label for file 09. Do not tell them they are a data point.
6. Proof opt-in lifestyle only (optional). One sentence: "If you ever want to write how your evenings look different, I can ask later in writing. It is not required." No camera on the spot. No SOL/ISI in any proof.
7. Close. Milestone note. Safety short line.

If they want to cancel at D42, switch to file 07 in the same sitting if they agree to stay on the call. That counts as the exit attempt.

---

6. Agenda D63: Core container close

Theme: Usable path finished. Ascend or clean exit. No unfinished-treatment frame.

Not the theme: "You should stay because you are not cured." "This would be irresponsible to stop."

Agenda (1:1, 25–30 min)

1. Clock check. Safety.
2. Attendance fact for the container. core_container_complete = yes if they reached D63 with a usable path (they ran window + SC + circadian + diary, even with exceptions). Completion is a coaching fact. It is compared later to the about-56% automated dCBT-I floor at cohort level, not as a shame number on this call.
3. What to subtract if they continue. What to stop if they exit.
4. Ascend (optional): next coaching container if Monash/Jomini have published one. Still non-clinical. No results guarantee to close it.
5. Clean exit: thank them. Offer exit interview questions even on a completed container (learn). Do not force.
6. Proof / refer / testimonial: optional, consented, later, written. Never a condition of having been coached.
7. Milestone note D63. Safety short line.

Forbidden close: "If you leave now the insomnia will come back and that will be on you."

---

7. Group-event addendum (design only)

When (and only when) file 10 is live:

• Same agendas, 30 minutes, cap small (founder can still see faces).
• No "who slept the most."
• No diary numbers in chat.
• Silent members get a DM after, not a public call-out (file 10).
• Still end ≥3h before the earliest window in the room. If windows differ by more than 2 hours, do not group them. Stay 1:1.

---

8. Founder event log (dummy headers)

client_code
event (D21|D42|D63)
planned_local_start
planned_local_end
window_open_local
ends_3h_before_window (yes/no)
after_2000_local (must be no)
format (1to1|group)
held (yes|moved|async_fallback|canceled_safety)
persist_42_marked (D42 only)

If ends_3h_before_window is no, you may not hold.

---

What goes wrong / how you catch it (events)

What goes wrong: founder hosts a "Sunday night wind-down party" at 21:00 because Hormozi gyms do mixers.

How you catch it: clock rules §1. Gym mixers stay in the gym. Cancel.

What goes wrong: D21 becomes a lecture with three new modules.

How you catch it: agenda cap. Subtract-first. Hygiene is a module.

What goes wrong: two clients in a group, windows 22:00 and 00:30, event 18:00–19:00. The 22:00 client has only 3 hours, the math is tight; a 10-minute overrun breaks it.

How you catch it: end time is scheduled, timer visible, 19:00 hard stop. If windows disagree, do not group.

What goes wrong: D63 used to upsell a "guaranteed sleep" annual.

How you catch it: Monash owns price; results guarantees are forbidden; annual pay cannot hide an outcome promise (file 07).

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Smith (start_date); Jomini (rationale, number talk); Steuben (group/community gate); Monash (ascend price, later) Evidence: Hormozi 21/42/63 internal-cadence method, adapted so events protect the window. Trauer 2015 named on D21 for TST-flat-early. Completion floor about 56% is a cohort comparison, not a client script. Confidence: 0.86 Residual uncertainty: Whether group-shared dates or per-client dates produce cleaner 1:1 load is unknown until n=5–10 are staggered. Default per-client. Group format remains design-only.

Exit interview and cancel / pause / refer tree

Internal draft. NOT LIVE. Do not run this on a friend "to practice" with their real complaint. Rehearse out loud alone. This is practice paper. Do not run real clients yet.

---

Rule

Medical flag or safety → STOP window, refer, do not save into more coaching. A window is the assigned hours they may be in bed. Every other cancel request gets an exit-interview attempt. The save metric is attempt rate = 100% of cancel requests. There is no "save about half" as the number we watch. Give money back if they ask, per Steuben/Monash when that policy exists; do not invent a refund percent. Do not sell a results guarantee to keep them.

---

1. Attempt-rate floor (command)

Log cancel_request_date and exit_attempt_done. If exit_attempt_done is no after 48 hours, you missed the floor. Do the attempt anyway and mark late.

---

2. Decision tree (follow on the call)

Start at T0. Do not skip T0 because the client paid.

T0  Any safety item in play?
    YES → STOP window. Refer. File 04 §9. Outcome = refer.
          Do not resell. Do not offer a tighter window as medicine.
    NO  → T1

T1  Are they asking for a doctor, a cure, or treating you as a clinician?
    YES → Fire or refer. Do not re-sell the container as treatment.
          Outcome = fire or refer.
    NO  → T2

T2  Diary refusal after onboarding (they will not fill nights)?
    First time → One correct: diary is the instrument (file 03 §1).
                 A diary is the morning form where the client writes last night's sleep times.
                 Offer to cut comments_optional. Do not drop the diary.
                 If they now agree → stay, outcome = stayed_process.
    Second refusal → Fire. Outcome = fire.
    NO (they fill, or this is not the issue) → T3

T3  Community poison (only if community later live)?
    First time → Correct once (file 10).
    Repeat → Fire. Outcome = fire.
    NO → T4

T4  Overwhelm ("too much," cannot keep the modules)?
    YES → Subtract. Keep window + SC + circadian + diary.
          Offer pause of defined length if still too much.
          Do not add content. Outcome = stayed_process or pause.
    NO  → T5

T5  Life shock (travel, family, work_critical) and safety still clear?
    YES → Pause with restart date.
          Diary-min = rise time only, if safe.
          Window assignment frozen (see §4).
          Outcome = pause.
    NO  → T6

T6  "It isn't working / I still wake" and we are in week 1–2?
    YES → Rationale + safety check again.
          Hold protocol. Do not widen the window to please.
          Outcome = stayed_process if they hold; else T8.
    NO  → T7

T7  Money / regret / "too expensive"?
    YES → Exit interview (§5). Process refund per Steuben/Monash.
          If they ask for money back, give it (Hormozi keep; compatible).
          Do not invent a percent. Do not sell a results guarantee.
          Outcome = refund_path or stayed_process if they keep coaching
          after a process recap (rare; do not push).
    NO  → T8

T8  Still wants to cancel (other reason or residual)?
    YES → Finish exit interview. Offer clean cancel.
          Offer later re-entry without shame (no price locked here).
          Outcome = cancel.
    They want pause instead → T5 rules.

Community poison and diary refusal are "correct or fire." Do not run a long save sequence on those.

---

3. Pause vs cancel (doctrine)

Pause

• Client kept.
• Assigned window frozen (times stay on the client tab; they are not running them).
• Defined length: write pause_start, pause_restart. Default offer: 14 days. Hard cap without a new conversation: 28 days.
• Diary-min if safe: rise time only (circadian_anchor as assigned). No full tick guilt. Ticks are yes/no marks that they did each assigned habit that day.
• 2×/week slots reduce to one async check on the restart week, plus a restart kickoff (short).
• Safety pause is a pause with window stopped, not frozen-as-if-active. Different: they must not run the window.

Cancel

• Client closed.
• Exit interview + written confirm.
• Later re-entry without shame, subject to screen again and to then-current price (Monash).
• No unfinished-treatment frame.

Do not use pause to hide a client you should have referred.

---

4. Annual pay (note only)

Churn Checklist item 6: offer annual pay.

Davout does not lock a price, a discount, or a term. Monash owns price. If a client asks:

"I can ask for the written annual option when pricing publishes it. Cancel and refund stay clean. We do not lock you in to hide a results promise. I will not quote a number today."

No lock-in that hides a results guarantee. No "pay for a year and we guarantee sleep."

---

5. Exit-interview script

Open (live, 15–20 min max)

"Thanks for talking. This is an exit conversation. I will not diagnose you and I will not talk you into a medical result. I want to learn what to subtract, and I will tell you the clean options: pause, cancel, or referral if safety is in play. If you want your money back, I will run the written refund path. I do not invent a percent on this call."

Safety first (required)

"Before the rest: any safety item in play? Breathing pauses, gasping, legs that force you up, heavy sleepiness when you must be alert, a swing into very little sleep with unusually high energy, a seizure, pregnancy, safety-critical work."

If yes: stop. File 04 §9. End the sell path.

Questions (ask in order, skip if already answered)

1. "What made you ask to cancel, in one sentence?"
2. "Was it too much content, or too little hold?"
3. "Did the diary feel usable?"
4. "Did I miss a 48-hour gap or a broken window and stay quiet?"
5. "If you could keep only one part of the protocol, which one?"
6. "If you could remove one part, which one?"
7. "Do you want a pause with a restart date, a clean cancel, or (if you asked) the refund path?"

Do not ask "how is your insomnia now?" Do not ask for a testimonial on this call.

Process recap (only if T4 or T6 and they are still deciding)

"What I can offer is process: we hold the window, we subtract extras, we keep the diary. I cannot offer a promise about hours slept. I will not widen the window in week 1 or 2 to make you stay."

If they stay after that recap: exit_outcome = stayed_process. Log the subtract.

If they leave: thank them. exit_outcome = cancel or refund_path.

Close

"You can come back later without a shame story. You would screen again. I will send a short written confirm. I will not follow you with a seven-email funnel."

Cap at one written confirm. File 08 does not apply to a completed cancel.

---

6. Async exit attempt (if they refuse live)

Send once.

"You asked to cancel. I need to offer a short call. If you do not want the call, reply to these:

1. One sentence on why.
2. Keep-one / remove-one.
3. Pause with a date, clean cancel, or refund path (if you want money back I will run the written policy).

If a safety item is in play, write 'safety' and I will stop the window and refer. I do not diagnose."

If no reply in 48 hours after this async: mark exit_attempt_done = yes (attempt made), exit_outcome = silent, close the client. Do not keep billing if Monash/Steuben require a cancel on request. When policy is unpublished: do not take new money; tell Steuben/Monash.

---

7. Fire script (short)

Diary second refusal

"The diary is the instrument. I asked once and explained. A second no means I cannot hold the habit with you. I am ending coaching. I will run the written money path if you ask. I do not diagnose you on the way out."

Clinician / cure demand

"I offer CBT-I-informed behavioral sleep coaching: education and a habit protocol. I do not diagnose, treat a disorder, or promise a cure. If that is what you need, a physician is the right next step. I will end coaching rather than pretend."

Community poison (later)

"The room has a rule: no medical advice, no diagnosis swap, no late rooms. I corrected once. I am removing you from coaching and from the room."

---

8. Refund language (process only)

Do not invent a percent, a cooling-off number, or a "one session used = X."

Until Steuben sibling 09 (refund policy) and Monash pricing exist, say:

"I will confirm the written refund and cancel policy and execute it. If you asked for the money back, I will not fight you for a medical result. I need a day to pull the written rule. Coaching stops if you want it stopped today."

Hormozi keep that is compatible here: if they ask for the money back, give it. That keep does not authorize a results guarantee.

Korean e-commerce cooling-off residuals sit with Steuben. Davout does not opine.

---

9. Re-entry

• No shame language.
• New screen (Steuben SOP) before a new client start.
• Then-current price (Monash).
• New client_code or same code with a new start_date and a new container. Prefer same code plus container_n if Jomini agrees later. Until Jomini publishes, use client_code + new start_date and archive the old nights.

---

10. Log fields (dummy)

client_code
cancel_request_date
exit_attempt_done
exit_attempt_at
exit_channel (live|async|refused_then_async)
tree_branch (T0..T8)
exit_outcome (stayed_process|pause|refund_path|fire|refer|cancel|silent)
pause_start
pause_restart
subtract_done (yes/no)
money_asked_back (yes/no)
policy_source (steuben_monash|unpublished_escalated)
results_guarantee_offered (must be no)

Cohort rollup: exit_attempt_rate = attempts / cancel_requests. Floor = 1.0. Do not report a save percentage as a target.

---

What goes wrong / how you catch it (exit)

What goes wrong: founder hears "I still wake" on day 8 and offers 45 extra minutes in bed plus a 20% discount.

How you catch it: T6 + §4. Hold protocol. No invented discount. No widen-to-please.

What goes wrong: founder skips T0 because the client is "just price sensitive" and then misses a pregnancy disclosure in minute 18.

How you catch it: safety question is first, always.

What goes wrong: a dashboard shows "save rate 50%" because a gym spreadsheet was copied.

How you catch it: delete that column. Attempt rate only.

What goes wrong: founder writes a refund percent in chat to sound sure.

How you catch it: §8. Escalate. Do not guess.

What goes wrong: pause used for a safety case so the founder can "keep the revenue."

How you catch it: safety pause stops the window and refers. Paid status is not a reason to continue.

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Steuben (refund, cancel, screen, community rules); Monash (price, annual, refund math); Smith (billing stop after invoice path); Jomini (window hold vs later protocol edits) Evidence: Hormozi exit-interview + give-the-money-back methods, translated. Command floor: 100% attempt. Steuben Part A: paid referral banned; refund policy is a sibling and unpublished. No refund percent invented. Confidence: 0.83 Residual uncertainty: Written refund percent, cooling-off, and unused-session math are unpublished. Pause default 14 / cap 28 is a Davout operating choice, not a statute. Re-entry coding (container_n) may change when Jomini publishes.

Re-engagement: silent diary / silent check-in

Internal draft. NOT LIVE. Do not message a real person. Do not connect this sequence to a live bot. This is practice paper. Do not run real clients yet.

---

Rule

Diary silent 48 hours, or window broken 3 consecutive nights: same-day reach-out. A diary is the morning form where the client writes last night's sleep times. A window is the assigned hours they may be in bed. Stop rule (20 August 2026): this is a re-engagement touch, not a fifth standing note. Standing client messaging stays the 2 named diary replies/week. No daily note loop. Async first, then a video or voice offer. Cap 3 touches in 7 days. Never therapeutize. Never "I'm worried about your insomnia." After 3 touches with no response: mark silent, keep one more 2×/week slot, then founder decision (pause letter or exit attempt).

---

1. Triggers (pick is closed in this packet)

Trigger A: silent diary

Fire when: no filled CSD night (diary_filled is false or the row is missing) for 48 hours after the last expected night. CSD means Consensus Sleep Diary, the same morning form.

Expected night = each calendar night for an active, non-pause, screen-clear client.

Same-day reach-out. Do not wait for the next Tuesday slot.

Trigger B: window broken

Action trigger (this packet's pick): window_held = no on 3 consecutive night_date values.

Watch (do not start the 3-touch sequence): window_held = no on 3 nights in 7. Mention on the next regular 2×/week slot (script 4 themes, lighter). If the watch becomes 3 consecutive, upgrade to action.

Why 3 consecutive for action: clear, low argument, easy to see on a scan. 3-in-7 catches a skip pattern that is not yet a streak.

Same-day reach-out on the action trigger.

Trigger C: silent login / silent reply

After a platform exists and Legal signed: no login and no check-in response for 72 hours.

Until then: Trigger C = no reply to a 2×/week touch for 72 hours.

Trigger C is not same-day-from-diary-scan. It starts at hour 72 from the unanswered touch. Still async first.

Dual fire

If A and B fire together, send one message that names both facts. It counts as one touch.

---

2. Sequence (7-day window)

Day 0 = the founder day (KST or founder-local, pick one and keep it) when the trigger is seen.

Cap: 3 sequence touches in 7 days, plus the one already-on-the-calendar slot. Do not add a fourth chase text.

Clock: same as file 04. Do not send after 20:00 client-local. Do not send inside the window. If you discover the trigger at 21:30 their time, wait until the next legal afternoon slot. "Same-day" means same founder calendar day if the clock allows; otherwise first legal slot (still do not skip a day if their morning is open).

---

3. Scripts

Safety abort line on every touch (file 04 §3). If they name a safety item, leave this file.

Trigger A: touch 1 (async)

"I do not have a night row from you for 48 hours. I am checking the instrument.

You were on the card before this gap.

Can you send the missing night (even messy) today, or reply 'pause' if life blew up? If a safety item is in play, write 'safety' and we stop the window. I do not diagnose."

Trigger B: touch 1 (async)

"Three nights in a row the window was not held. That is the drop I watch.

Thank you if the diary still arrived. I need the reason, not a feeling.

What broke it: early in, late out, or something else? Exception codes: travel, illness, safety, caregiving, work_critical, other. If safety, we stop. I do not diagnose."

Trigger C: touch 1 (async)

"I did not get a reply to the last check-in (72 hours). I am not here to process this as therapy.

One line is enough: 'still in,' 'pause,' or 'cancel talk.' If safety, write 'safety' and we stop the window. I do not diagnose."

Touch 2: voice or live offer (all triggers)

Async wrapper:

"Second note. I can do a 10-minute video or you can send a voice reply. I will not analyze your character. I need the card, a pause date, or a cancel talk. Same safety rule."

If they jump on live: run file 04 script 3 or 4. One ask. If week 1–2 misery, script 2. Do not widen the window to please.

Voice note you send (≤60 seconds):

"It's [founder]. Two facts: [missing diary / three broken windows / no reply]. I need the night card, a pause with a date, or a cancel conversation. I do not diagnose. If safety is in play, we stop the window. I will not send a long series after this week."

Touch 3: last sequence (async)

"Third and last chase this week. After this I will mark you silent and keep one regular slot, then I will either send a pause letter or an exit attempt.

Reply: 'card coming' / 'pause' / 'cancel talk' / 'safety'. I do not diagnose. I do not treat this as therapy."

Do not write "I'm worried about you" or "I'm worried about your insomnia."

---

4. After three touches, no response

1. Mark status = silent on the client tab.
2. Keep the next already-named 2×/week slot once (script 5 or a one-line "still holding the slot").
3. If still no response after that slot: founder decision the same day.

Decision rule:

Do not keep a full tick expectation on a silent client. Ticks are yes/no marks that they did each assigned habit that day. Do not keep billing if they already asked to cancel and you only missed them. Escalate billing questions to Smith/Monash/Steuben.

---

5. Pause letter (async)

"I have not heard from you after three check-ins. I am pausing coaching and freezing the assigned window times. Restart date: [date, 14 days out]. If a safety item is in play, ignore the restart and contact a physician; write 'safety' and I will send the referral path.

If you want to cancel instead, reply 'cancel talk.' If you want money back, I will run the written policy. I do not diagnose."

Log pause_start, pause_restart.

---

6. If they respond

---

7. What you never do

• Diagnose the silence ("this is avoidance from insomnia anxiety").
• Offer to stay until they sleep 8 hours if they come back.
• Publicly list silent members (community later: DM, no shame post).
• Stack a fourth, fifth, sixth "just checking."
• Text inside their window.
• Use a family member's contact you were not given for coaching.

---

8. Log fields (dummy)

client_code
trigger (A|B|C|A+B)
trigger_seen_at
touch_n (1|2|3|extra_slot)
touch_at
channel
response
status (open|silent|pause|exit_attempt|refer)
reengage_touches_last_7d

Scan reengage_touches_last_7d in the morning batch. If it would go to 4, stop.

---

What goes wrong / how you catch it (re-engagement)

What goes wrong: founder sends 6 WhatsApp texts in two days because gyms "save ghosts."

How you catch it: cap of 3 + one slot. The log field is the catch.

What goes wrong: Trigger B set to 3-in-7 as action, and the founder nags every fragmented week.

How you catch it: 3-in-7 is watch only. Consecutive is action.

What goes wrong: same-day message at 23:10 client-local.

How you catch it: clock rules. Delay to next legal slot.

What goes wrong: "I'm worried about your insomnia" because the founder is kind.

How you catch it: banned line. Rewrite from §3.

What goes wrong: silent client is still counted in attendance denominator as if they were assigned full ticks, then completion is compared unfairly to the about-56% floor.

How you catch it: pause and silent statuses remove those nights from window_assigned_days after the pause starts. Cohort completion uses container rules in file 11.

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Smith (channel that exists after kickoff); Steuben (collection, messaging as personal data); Jomini (window definition) Evidence: Command floors: 48h diary, 3-night window, 3 touches / 7 days. Hormozi first-drop intervention, translated. Trigger B consecutive vs 3-in-7 watch is a Davout pick stated as such. Confidence: 0.86 Residual uncertainty: Platform login Trigger C is hypothetical until a tool exists. "Same-day" vs clock-rule delay will produce edge cases across time zones; founder-local day plus first legal client slot is the resolution.

First 72-hour activation loop

Min-path n = 5 to 10, co-owned with Funnel (Bedell Smith)

Client-facing First 72 Hours script, Decision Log, and Restart Card: files 12, 13, 14. This file stays the founder loop.

Internal draft. NOT LIVE. Before Blue Book: rehearsal only. No real client data. No live calendar product. No invoice. No DM to a prospect. This is practice paper. Do not run real clients yet.

---

Rule

Smith owns DM → manual calendar → Zoom → invoice → kickoff, and the week-0/1 install of wind-down, clock-cut, and scorecard. Davout owns daily-habit hold from hour 0 and the activation-candidate watch. Activation is discovered from cohort 1. This file lists candidates. It does not freeze a winner.

Stop rule (20 August 2026). Official Day-7 first-win count = Slim ops/03-day-7-first-win-standard.md only. A first-win is any one of: (a) wind-down installed and executed 3 consecutive nights; (b) clock-checking cut 3 consecutive nights; (c) diary + ticks live on ≥5 of the first 7 nights. A diary is the morning form where the client writes last night's sleep times. Ticks are yes/no marks that they did each assigned habit that day. Candidate H (all three of wind-down + clock-cut + scorecard) stays a guess we will test after the first group reaches day 42, not the official count. Do not merge the Slim first-win cell with act_H. File 13 audio stays UNBUILT. This is practice paper. Do not run real clients yet.

Stop rule (20 August 2026). No daily founder note loop in the first 72 hours. Standing messaging = 2 named diary replies/week. Hour 0 Script 1 may count as the first diary reply that week. A missing first card waits until 48 hours, then file 08. That 48h touch is re-engagement, not a fifth standing note.

---

1. Ownership split (hour 0)

If Smith has not marked legal_screen_clear = yes and smith_kickoff_done = yes, Davout does not open a nights row.

---

2. Handoff fields (shared names)

Write these on one page. After Legal, they become the client tab seed.

client_code
start_date
tz_name
window_open_local
window_close_local
assigned_rise_rule
assigned_light_rule
legal_screen_clear
smith_kickoff_done
paid
channel_for_async
first_win_wind_down (pending|yes|no)
first_win_no_clock (pending|yes|no)
first_win_scorecard (pending|yes|no)

client_code is a short ID like C-001, used instead of a name on work sheets. Davout does not invent client_code formats that collide with Smith. Proposed format: C- + three digits in cohort order (C-001). No names in the code.

Jomini later attaches isi_t0 on this same row. Leave blank if Jomini is not in the kickoff.

---

3. Hour-by-hour / day 0–3 (after the gate)

All times are client-local for anything the client must do, and founder-local (KST for 이성재) for founder batches. Livingstone, that founder-local clock is yours.

Hour 0 (end of kickoff)

Smith: invoice already done. Kickoff complete. Window spoken.

Davout:

1. Confirm legal_screen_clear and paid.
2. Write window times on the client tab.
3. Give the diary paste card (file 03). Do not add a module.
4. Run Script 1 live beats if still on the call; otherwise send Script 1 async in a legal clock window.
5. Ask them to state, in their own words, the window and "out of bed if not sleepy." If they can, mark candidate J with date.
6. Safety short line.
7. Stop. No community invite. No extra PDF pile.

Hours 1–12

Founder: no extra ping unless they already sent a question. If they ask for more content, subtract (script 6). Hygiene is not the program.

First night (hour 0 sleep period)

Client: fill the card after out-of-bed the next morning.

If that first card arrives: candidate A = yes. If all six ticks are marked that day: candidate C = yes. If stimulus_control is yes because they actually left the bed: candidate F = yes.

Day 1 (founder morning, KST)

1. 15-minute batch scan (file 03) includes this new code.
2. If first card is in: send a 3-line Script 5 variant (attendance, not hours). Safety line.
3. If first card is missing and 48 hours have not passed: wait. Do not nag at hour 20.
4. Smith may still be installing wind-down / clock rule. Davout does not take over that install.

Day 1–2 evening (client-local, legal clock)

One touch maximum beyond the kickoff Script 1. Prefer silence if the card is arriving.

Day 2

Scan. If still no night after 48 hours from the first expected night: Trigger A, file 08, same day.

If two nights in and ticks messy: one friction, script 6 if overwhelmed. Do not add a wearable.

Day 3 (close of 72 hours)

Founder 20-minute review per new client (batch if several started together):

Checklist:

• [ ] legal_screen_clear still yes
• [ ] At least one CSD night (A) yes/no + date
• [ ] Three consecutive nights: too early unless they started before hour 0 (should not). B is a 42-day item more than a 72h item
• [ ] First all-ticks day (C) yes/no + date
• [ ] First live/video session (D): kickoff counts if they attended. Mark D with start_date if kickoff was live
• [ ] Stimulus-control night executed (F) yes/no
• [ ] Can state rules (J) yes/no
• [ ] Scorecard row exists (Smith first-win piece; may still be pending)
• [ ] No safety flag
• [ ] Next 2×/week slots named and clock-legal

Send one async: either Script 5 (showing up) or Script 3 (if silent) or Script 2 (if misery mail already arrived).

Stop at hour 72: do not declare "activated." Log candidates. Continue hold.

---

4. Days 4–7 (Slim official first-win; H is a guess)

Official Day-7 first-win (Slim ops/03, stop rule): any one of:

• (a) wind-down installed and executed 3 consecutive nights
• (b) clock-checking cut 3 consecutive nights
• (c) diary + ticks entered on ≥5 of the first 7 nights

Slim owns that official-count cell. Davout does not merge it with candidate H.

Smith still installs the three behaviors in week 0–1. Davout still ticks wind_down_done and no_clock_checking daily. Davout does not move Slim's bars.

On day 7, log Slim's official result as slim_d7_first_win = a | b | c | miss (and which code). Separately, if all three behaviors are true that day, mark candidate H = yes + date. H is a guess we will test after the first group reaches day 42, for the day-42 discovery table. It is not the official count.

Davout still does not freeze H, a, b, or c as "the" activation point.

---

5. Candidate activation points (list, do not freeze)

For G, this packet's discovery rule: log act_G_consec7 as 7 consecutive window_held = yes. Also log act_G_first7calendar if the first 7 assigned nights were all held. Do not pick one as the winner in week 0.

Incentives (process/effort, never hours-slept):

• Verbal compliment on A, C, F, J (script 5).
• Started milestone note after kickoff (file 05).
• No badge for TST. TST is total sleep time. No "sleep 8 hours and get a week free."

---

6. Discovery method after cohort 1 (n = 5 to 10)

Do not freeze a winner in this file.

After the last cohort-1 client reaches day 42:

1. For each client_code, set persist_42 = yes if still in container on day 42 (not canceled, not fire, not safety-closed without restart). Pause that resumed before day 42 can still be yes if they are in on day 42. Pause still open on day 42 = no.
2. For each candidate A–J, you have act_X_date or blank.
3. Build a small table (dummy headers):

candidate_id
n_hit
n_hit_and_persist_42
n_miss
n_miss_and_persist_42

1. A candidate predicts 42-day persistence in this small-n sense when n_hit_and_persist_42 / n_hit is higher than n_miss_and_persist_42 / n_miss, and n_hit is at least 3. With n=5–10 this is fragile. Treat as a signal to onboard toward, not as a scientific result. Do not publish it. Do not invent a p-value.
2. If two candidates tie, prefer the earlier, founder-forcible one (you can make A and D happen; you cannot force G if they refuse the window).
3. Write a dated annex. Do not edit this list to delete losers. Keep A–J as the watch set; star the onboarding target.
4. Only then may Smith/Davout "onboard to that point on purpose" (Churn Checklist 2). Until then, onboard to all early forcible candidates: A, C, D, J, and Smith's H.

Forbidden: declaring H "the" activation point in a sales page because it is tidy.

---

7. Before Blue Book (rehearsal only)

Do this. Do not do the live column.

Allowed

• Walk the hour 0 checklist out loud.
• Draw the handoff fields on paper with C-000 and no personal data.
• Time Script 1. Cut lines you would not say.
• Confirm with yourself that no calendar SaaS, no Skool, no email capture is open.
• Send Napoleon file 99, not a "we launched a trial."

Forbidden

• A friend's real diary as a test row.
• A Stripe invoice "to see the flow."
• A Typeform.
• A DM to a warm lead "to pilot the 72h loop."
• Storing a phone number.

If Smith runs a separate rehearsal, Davout still does not collect.

---

8. If/then in the first 72 hours

---

What goes wrong / how you catch it (72h)

What goes wrong: founder freezes candidate A ("first night") as activation because 10/10 who did A also paid, which is circular.

How you catch it: discovery waits on persist_42. Payment is not persistence.

What goes wrong: Smith and Davout both message in hour 6 and the client feels two coaches plus a form.

How you catch it: Script 1 is the only Davout outbound in hour 0–12 unless they asked a question. Smith owns remnants. One channel.

What goes wrong: scorecard "live" means a cloud sheet with health fields before consent.

How you catch it: Steuben stop rule. Scorecard live after gate only. Rehearsal uses headers.

What goes wrong: founder onboards to G in the first 72 hours and shames a miserable client who held 5 of 7.

How you catch it: G is a week-scale candidate. 72h watch is A, C, D, F, J.

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Bedell Smith (funnel + 7-day first-win); Jomini (window assignment, isi_t0); Steuben (screen, collection) Evidence: Command constraint: activation discovered, not frozen. Candidates A–J as tasked. Smith path as tasked. Hormozi "onboard to activation" method applies only after discovery. Confidence: 0.82 Residual uncertainty: Small-n discovery will be noisy. persist_42 definition for safety-refer clients (success, not leak) means they drop out of the persistence ratio on purpose; do not treat refer as activation failure. Kickoff-as-D may over-credit D; if every paid client has D, D will not discriminate. That is acceptable and should show up in the table.

Community linking design

Design only. Trimmed from the live stack.

NOT LIVE

The community is not open. Do not open a room. Do not invite anyone. This stays closed until Steuben signs the Blue Book for real-world use AND community terms exist AND this banner is lifted in writing.

Community terms on disk: /workspace/sleep-coaching-business/legal/20-community-terms-privacy-moderation.md is a draft gate, not a live lift. Do not treat that file as permission to open a room.

Do not create a Skool, Circle, Slack, Discord, Kakao room, or public forum. Do not collect email via a community waitlist. Do not SEO a community. Do not invite a friend to "test the rooms."

Monash trimmed community from the live offer stack (offer/01-OFFER-ARCHITECTURE.md TRIM). This file is design-only so a later build has rooms and bans. Community is not a Week 0 bonus. Week 0 bonuses are files 12, 13, 14.

---

Rule

Community is for human links after activation, after Legal, after paid, after screen-clear. It is not a content dump. It is not a therapy group. It is not a diagnosis swap. Activation before community scale. Founder-only moderation at n=5–10. Correct once, then fire (file 07). Diary stays off-community. A diary is the morning form where the client writes last night's sleep times.

---

1. Purpose (closed)

• Human links after a founder-marked early activation candidate: at least one of A, C, D, or J (file 09). After cohort 1 day 42, the starred onboarding target may replace this temporary gate. Do not freeze a winner in this file.
• A place for process talk and light off-topic.
• A calendar home for D21 / D42 / D63 if group events are later allowed (file 06).

Out of scope:

• A free substitute for the 2×/week hold.
• A medical advice board.
• A lead magnet.
• A late-night voice lounge.
• A Week 0 Install extra.

---

2. Join gate (all must be true)

1. Blue Book signed for real-world use (Certificate plus honest counsel-engagement residual).
2. Community terms exist and have been rewritten from gate to in-force (legal/20, plus Steuben change-control). Accepted by the member.
3. Client paid.
4. Screen cleared (legal_screen_clear = yes).
5. Founder has marked at least one early activation candidate: A, C, D, or J.
6. This file's NOT LIVE banner is lifted in writing by Steuben (copy Napoleon).

If any item is false: no invite.

No public Skool. No SEO community. No email capture from community until Legal says that capture is a separate, lawful process. Default: do not capture.

---

3. Platform recommendation (pick none)

Skool is a candidate, not a decision.

Equal alternatives that can run the same rooms and bans: private Circle, private Slack, private Discord.

Recommendation: private community after Legal. Skool is a candidate, not a decision. Pick none now. Do not buy a plan. Do not reserve a name if reservation requires an account that looks like a public brand launch. If you are unsure, do nothing.

Davout will not pick a vendor in this draft. Steuben processor register (legal/19-processor-register-and-dpa-pack-outline.md) must include the vendor first. Many hosts are cross-border.

---

4. Rooms (draft)

No other rooms at n=5–10. No "apnea corner." No "meds." No "partners of insomniacs" as a therapy space.

---

5. Banned (repeat, moderate to this list)

• Medical advice
• Comparing medications
• Diagnosing each other
• Late-night voice rooms
• "Who slept the most"
• ISI / SOL posts
• Diary numbers in public posts
• Health fields on community profiles
• Founder office hours after 20:00 in any member's local time if that member is present. Safer: cap office hours at 16:00 Asia/Seoul and on-request 1:1
• Public shame of silent members
• Testimonials coerced as rent for the room

---

6. Moderation (n = 5 to 10)

Founder only. No later helper. No volunteer moderator.

Correct or fire (file 07)

1. First poison (medical advice, diagnosis swap, abuse, late-room push): correct once, in writing, quote the rule, remove the post.
2. Second: fire from coaching and from the room.

Safety post ("I have gasping at night"): treat as a flag. DM, stop window, refer. A window is the assigned hours they may be in bed. Delete the public thread. Do not crowd-diagnose.

---

7. Linking design (how the rest of Davout points here, after live)

2×/week reach-out → thread

In a regular Script 5, one optional line after live:

"If you want a human link, the Daily-tick room is for 'ticks sent,' not numbers. I will not post your diary there."

Do not require a community post as attendance. Attendance remains CSD + ticks on the founder sheet (file 03).

Silent members

Private DM on Trigger A/B/C (file 08). No public "we missed you" board. No @-shame.

Events D21 / D42 / D63

Calendar post in Start-here with clock rules in the post body. Group event only if file 06 group conditions are met. Otherwise the post says "your 1:1 is on your calendar." Dates sit on the founder calendar per file 06 whether or not a room exists.

Activation

Invite after founder marks A, C, D, or J. The invite is a DM, not a public add of a cold email.

Diary

Diary stays on the founder sheet or a later approved tool. Community never stores sol_min, waso_min, isi_*.

---

8. Profile and data rules

Community profile may hold: display name (need not be legal), client_code (a short ID like C-001, used instead of a name on work sheets) if they choose, timezone.

Community profile may not hold: ISI, diagnoses, medications, AHI, wearable scores, address, government ID.

PIPA sensitive information (health) does not go in a social profile. Steuben legal/11-sensitive-data-consent-form.md and legal/09-privacy-notice.md bind this once live. Until live: no health fields.

---

9. Founder time (why this stays off at n=5–10)

A live room adds unread load. File 02 already sits near 5.5 hours/week async-first. Slim vetoes community before collection and before scale gates (ops/04-bonus-veto-rules-and-log.md starter log: Skool-as-bonus VETO). Monash TRIM agrees. Honest capacity: a few clients at a time, one founder.

When (if) live: one 20-minute moderation pass on the same days as async ACA, afternoon KST, never late. ACA means acknowledge, compliment, ask. If that pass exceeds 20 minutes, freeze new posts except Daily-tick and Ask-the-founder.

---

10. Pre-live checklist (do not fake a tick)

• [ ] Steuben Certificate + counsel residual honest
• [ ] legal/20-community-terms-privacy-moderation.md rewritten from gate to in-force and counsel-marked
• [ ] legal/19 processors list includes the vendor
• [ ] Sensitive-information consent path exists if any health could leak (legal/11)
• [ ] Banner on this file lifted in writing
• [ ] Join gate coded as a founder checklist, not a public form that captures strangers
• [ ] Rooms named. Banned list pasted in Start-here
• [ ] Diary tool is separate
• [ ] Office hours clock-legal
• [ ] No SEO, no public directory, no lead magnet
• [ ] At least one of A, C, D, J marked before each invite

All boxes blank today. Correct.

---

11. Do not contradict the trim

If a founder wants a "soft room for the first three clients," that is a launch. Refuse.

---

What goes wrong / how you catch it (community)

What goes wrong: founder opens a free Skool to "build in public" and calls it marketing.

How you catch it: banner. Steuben kill authority. Close it the same day (KST).

What goes wrong: Daily-tick becomes a leaderboard of hours slept.

How you catch it: banned list. Delete. Correct or fire.

What goes wrong: a kind member diagnoses another ("that's obviously apnea").

How you catch it: poison rule. Remove. DM the named person with refer path, not a crowd thread.

What goes wrong: late-night Discord voice because "US clients are awake."

How you catch it: clock rules. US afternoon is possible; US 23:00 is not. If time zones cannot share a legal hour, do not run group voice.

What goes wrong: community used as the diary so PIPA health data sits on a US host without consent.

How you catch it: §8 and file 03. Diary off-community.

What goes wrong: founder treats legal/20 as a live lift because the filename says "terms."

How you catch it: legal/20 §1: no community at launch; draft gate. Banner on this file.

What goes wrong: invite before any of A, C, D, J, "to help them activate."

How you catch it: §2 item 5. Activation before community scale.

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Steuben (terms, processors, PIPA, kill); Smith (invite only after paid kickoff); Jomini (no clinical rooms); Monash (TRIM: not a Week 0 bonus); Slim (veto if hours or killed tools) Evidence: Hormozi community/events method, translated. Command: activation before scale; no live community until Blue Book; no public Skool; no email capture. Monash TRIM in offer/01. Slim ops/04 Skool-as-bonus VETO. legal/20 is a draft gate. Confidence: 0.87 Residual uncertainty: Vendor pick waits on legal/19. Whether a community adds hold for this offer is unknown; n=5–10 should run without it. A story that "the room will form a tribe" is not evidence. Join-gate candidates A/C/D/J are a temporary early set; day-42 discovery may star a different onboarding target.

Happy-client: stay-with-it half

Joint-ready with Jomini sleep-science/04-happy-client-sleep-numbers.md (published 20 August 2026)

Internal draft. NOT LIVE. No live dashboard. No client scores. Dummy fields only. This is practice paper. Do not run real clients yet.

---

Rule

Davout defines the stay-with-it half of "happy client." That is a coaching count. It is not a medical finding.

Jomini owns ISI change direction (after license), CSD SOL/WASO/SE direction, and TST-flat-early interpretation. CSD means Consensus Sleep Diary, the morning form where the client writes last night's sleep times. SOL is time to fall asleep. WASO is wake after sleep onset. SE is sleep efficiency (sleep time divided by time in bed). TST is total sleep time. Path: /workspace/sleep-coaching-business/sleep-science/04-happy-client-sleep-numbers.md.

Join keys in this file stay. Do not rename them.

Davout will not judge hours slept, "cured," AHI, or wearable scores as attendance or as happiness. ISI point-drop is not a stay-with-it win.

Success on completion = beat the about-56% automated dCBT-I completion floor (failure floor cited as about 52–60%). Do not claim 90%. Do not use gym monthly churn percentages. Do not set "save about half" as the number we watch.

Jomini completeness ≥5 mornings in ≥4 of 6 weeks including week 6 is their number-side rubric. Davout owns effort / attendance. Do not steal that rubric. Do not invent a 90% attendance bar to match it.

Both halves are required before Napoleon calls a model case. A client can be on-protocol on numbers and off-protocol on effort, or the reverse. Both can be true at once.

Proof, testimonial, refer, and ascend are optional and consented. They are not required for "happy."

---

1. Stay-with-it-half definition

A client is stay-with-it-happy for Davout when the container shows:

1. Attendance rate (nights_attendance_true / nights_assigned) is tracked and used in reach-out, not ignored. attendance_bool = filled diary night AND required ticks marked (file 03). Ticks are yes/no marks that they did each assigned habit that day.
2. Reach-out response rate is tracked (reachout_replies / reachout_touches).
3. Protocol adherence

• If a window is assigned: window_held_days / window_assigned_days, with exception codes. A window is the assigned hours they may be in bed.
• If no window yet (Week 0 and most of Week 1): score rise-time hold + stimulus control + diary instead. Do not mark window_held as failed because Jomini has not assigned a window.

1. Core container complete (core_container_complete = yes) or an honest pause/refer/fire that followed the tree. Cohort completion rate is compared to the about-56% floor. The comparison is a cohort rollup, not a badge on the person.
2. Exit-interview attempt rate = 1.0 on cancel requests (including this client if they asked).
3. Safety/refer happened when indicated. That is a success, not a leak.
4. Overwhelm incidents closed by subtraction are counted (zero is fine).
5. Activation-candidate log is filled (A–J dates or explicit no). No winner frozen.
6. Proof / testimonial / refer / ascend may be empty. Empty does not block "happy."

A client can be stay-with-it-happy and still have flat TST in week 1–2. That pattern is expected. Jomini talks the numbers. Trauer 2015 is the named published review (abstract: TST +7.61 min, CI includes 0). Quote only as published-review, not our promise. Do not put Trauer numbers on client cards (files 05, 12, 14).

A client can be referred out and still be a successful Davout case (safety_refer_flag = yes, window stopped). Do not put them in the completion numerator or in the persistence numerator.

---

2. What Davout will not judge

If a founder catch-phrase needs a number, use attendance count or window-held days (or rise-time-held days before a window exists).

---

3. Completeness overlap (both can be true)

Do not rename either field. Do not average them.

A client can have high attendance_bool (ticks marked, including honest no) and still fail Jomini completeness if too few mornings exist. A client can hit Jomini's ≥5/week fills and still be off-protocol on effort (they filled the diary and ignored stimulus control). Report both. Do not hide one behind the other.

---

4. Join keys and shared field names

Use these so Jomini can attach scoring without a rename war. Night field names stay closed to file 03 (Carney et al., 2012 domains).

Keys

Davout-only rollups (clients tab or a later retention tab)

nights_assigned
nights_attendance_true
attendance_rate
window_assigned_yet          yes/no
window_held_days
window_assigned_days
rise_held_days               (used when window_assigned_yet = no)
sc_yes_days
adherence_rate               (window ratio if assigned; else rise+SC+diary composite, document the formula in the cell note)
reachout_touches
reachout_replies
reachout_response_rate
exit_attempt_done
exit_outcome
safety_refer_flag
window_stopped_for_safety
overwhelm_subtract_n
core_container_complete
act_A_date
act_B_date
act_C_date
act_D_date
act_E_date
act_F_date
act_G_consec7_date
act_G_first7calendar_date
act_H_date
act_I_date
act_J_date
persist_42
proof_opt_in
refer_peer_n
ascend_offer_shown

Jomini-only (do not fill, do not rename, do not steal the rubric)

isi_t0
isi_t_end
isi_direction
sol_direction
waso_direction
se_direction
tst_flat_early_flag
completeness_week
completeness_container
jomini_number_side_in_range

Direction values: Jomini's enum when they publish one. Davout proposal if they want a shared word list: improved | flat | worse | not_scored. Jomini may replace the words. Davout will not create isi_change_points or a diagnosis cut-off.

Smith-only (do not collide)

smith_kickoff_done
first_win_wind_down
first_win_no_clock
first_win_scorecard
paid
channel_for_async

Slim-only (do not collide; see residual)

slim_day7_a
slim_day7_b
slim_day7_c
slim_day7_miss

Official Day-7 first-win (stop rule) = Slim ops/03 only: ANY ONE of (a) 3 consecutive wind-down nights, (b) 3 consecutive clock-cut nights, (c) diary+ticks ≥5 of 7. Candidate H (ALL THREE) is a guess we will test after the first group reaches day 42, on the discovery table, not this official count. Do not merge the columns.

---

5. Cohort rollup (n = 5 to 10)

One row per cohort, after the last client hits day 63 or has an exit/refer/fire.

cohort_id
n_started
n_screen_refer_pre_start
n_safety_refer_mid
n_fire
n_cancel
n_pause_open
n_core_complete
completion_rate
completion_vs_56_floor (beat|miss|n_too_small)
exit_requests
exit_attempts
exit_attempt_rate
overwhelm_subtract_total
persist_42_yes
activation_table_attached (yes/no)
n_model_case_both_halves

completion_rate = n_core_complete / n_started.

Do not subtract safety-refers from n_started to "look better" unless you also publish n_safety_refer_mid next to it. Preferred: report both. Refer is success-when-indicated. Completion floor comparison should be read with that pair.

If n_started < 5, write n_too_small rather than celebrating a beat.

n_model_case_both_halves counts only clients who are stay-with-it-happy and Jomini number-side in range. Napoleon may call a model case only from this count. Zero is an honest start.

Do not publish this rollup. No ad use until Steuben claims/testimonial files are live.

---

6. Week 2–3 hold (do not "save")

If Jomini says flat TST + rising SE = on-protocol, hold.

Davout does not:

• widen the window to soothe
• add modules to "make it worth the price"
• offer a results refund
• treat flat TST as a stay-with-it failure

Founder uses file 04 Script 2. Rationale plus safety check. Rescue is the hold. Abandoning the protocol is the leak.

Trauer 2015 abstract numbers (SOL −19.03 min, WASO −26.00 min, SE +9.91 points, TST +7.61 min with CI including 0) are published-review means. They are not client targets. They do not belong on cards or in Script 5.

---

7. Four-step path (Churn Checklist 9), optional

Hormozi four-step path, translated. Keep those four words out of client copy: activate is a founder watch, not a client slogan.

1. Activate: candidate log A–J + later starred target. Required as a watch. Not a frozen behavior. Client-facing copy uses process actions (file 12). Do not say "you are activated when…"
2. Optional consented non-clinical proof: lifestyle / process only. Written consent. No SOL/ISI. Steuben legal/14-testimonial-ugc-protocol-and-license.md.
3. Refer peers: ask as an offer, not a favor, and never as rent. Screen still applies to the peer.
4. Ascend: next container if published. No unfinished-treatment frame. No results guarantee.

Testimonials are never a condition of coaching. Missing steps 2–4 does not block stay-with-it-happy.

---

8. How the two halves sit together (for Napoleon)

happy_client (coaching construct)
├── stay_with_it_half (Davout)  attendance, hold, response, complete-vs-56,
│                               exit attempts, refer-as-success, subtract, act log
└── sleep_number_half (Jomini)  ISI direction (after license), SOL/WASO/SE direction,
                                TST-flat-early (Trauer 2015 named), completeness rubric

A client may be stay-with-it-happy and number-flat early. A client may have pretty numbers and still be a diary-refuser you should have fired. Do not average the halves into one vanity score in v1. Davout votes no on a composite that hides a safety refer or a diary refusal.

---

9. Worked empty example (no PII)

Headers only. Do not fill with fake people.

client_code | start_date | attendance_rate | adherence_rate | core_container_complete | persist_42 | safety_refer_flag | exit_attempt_done | isi_t0 | isi_t_end
C-00x       |            |                 |                |                         |            |                   |                   |        |

C-00x is a format dummy, not a person. isi_* stay blank until license.

---

What goes wrong / how you catch it (stay-with-it half)

What goes wrong: founder imports gym 15%/month churn and sets "save about half" as the number we watch.

How you catch it: §2. Exit-interview attempt rate = 100%. No save %. No gym %.

What goes wrong: founder invents 90% completion because "high-ticket should beat apps by a lot."

How you catch it: command floor is beat about 56% (range about 52–60%). 90% is forbidden copy.

What goes wrong: founder writes Trauer means on a Restart Card ("aim for −19 min SOL").

How you catch it: Jomini 04 plus files 05/12/14. Published-review only. Never a client target. Never on a card.

What goes wrong: founder builds a "Happy Score" = 0.5×SE + 0.5×attendance and posts it.

How you catch it: §8. No composite in v1. SE is Jomini's.

What goes wrong: founder uses Jomini's ≥5 mornings × 4 weeks as a fire rule in week 2.

How you catch it: that rubric is number-side, week-6 shaped. Davout fires on diary refusal after onboarding (file 07), not on a completeness miss in week 2. Reach-out on 48h silence (file 08).

What goes wrong: no window assigned, founder marks every night window_held = no and starts Trigger B.

How you catch it: §1 item 3. Rise-time hold + SC + diary until a window exists.

What goes wrong: safety-refer clients are coded core_container_complete = no and then used as a shame story in an ad.

How you catch it: refer is success-when-indicated. Ads wait on Steuben. Do not use them.

What goes wrong: completion marketed as "most clients finish the treatment of insomnia."

How you catch it: forbidden language. About-56% floor is an internal comparison. No public claim.

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Jomini (sleep-number half, now published at sleep-science/04); Smith (kickoff, first-win flags); Slim (official Day-7 first-win count); Steuben (proof/testimonial, ISI/CSD license gates) Evidence: Jomini 04 fetched 20 August 2026 (KST): ISI after license, direction only; CSD Carney et al. 2012, for-profit needs first-author permission; Trauer 2015 abstract TST +7.61 min, CI includes 0; completeness <5 fills → completeness only; both halves required for a model case. Command floors for completion comparison (about 52–60% failure floor, about 56% operating comparison) labeled as command/operating, not as a new paper. Hormozi four-step path translated as optional. Confidence: 0.86 Residual uncertainty: ISI and official CSD remain unlicensed (Jomini residual). Day-7 first-win is closed to Slim ops/03; H stays a guess we will test after the first group reaches day 42; columns stay unmerged. Adherence formula before window assignment is a Davout operational choice (rise+SC+diary); Jomini may later name the pre-window score. Composite happy score is deliberately absent. File 13 audio stays UNBUILT.

First 72 Hours script (client-facing)

Week 0 Install handoff + hour 0 to 72 run-of-show

Internal draft. NOT LIVE. Do not send this page to a real person. Do not collect a name, email, timezone, or diary row. Do not open a form, a calendar product, or a chat thread. Until Steuben Certificate plus an honest counsel-engagement residual, this is practice paper for 이성재 (Seoul). Do not run real clients yet.

Owner: Davout (delivery, habit hold, stay-with-it) Operator: 이성재, Seoul Date of draft: 20 August 2026 (KST) Language: English only Sister founder loop: /workspace/sleep-coaching-business/delivery/09-first-72-hour-activation-loop.md (do not replace it)

---

Rule

This file is the CLIENT-facing run-of-show plus the founder personalize sheet. File 09 is the founder loop (scan, candidate watch, Smith handoff). The client is not asked to self-activate.

Standing founder-to-client notes = two named diary replies per week. That is the only standing note cadence (stop rule, 20 August 2026). A diary is the morning form where the client writes last night's sleep times. Founder may scan the diary internally every morning. Extra outbound only on triggers: 48h diary silence (file 08), 3 consecutive window breaks (file 08), safety, cancel. A window is the assigned hours they may be in bed. Hour 0 Script 1 rides inside the Week 0 Install close, or it counts as the first of the two weekly replies if it is a diary reply. Do not stack a welcome note plus two weekly notes plus a 48h note as four standing slots. Do not invent a Day 1 / Day 2 / Day 3 founder ping sequence.

First win for this script (Monash KEEP, time-to-first-win) = the first completed night protocol. That means the next-morning diary is filled and the assigned ticks are marked. Ticks are yes/no marks that they did each assigned habit that day. It is not total sleep time. It is not an 8-hour night. Official Day-7 first-win is Slim ops/03 (any one of a/b/c). This script does not score day 7.

Restricted sleep window is set at the end of Week 1, after diary baseline and screen clear (Jomini). In the first 72 hours, earliest_bed_or_NONE is usually NONE. If a window is already assigned, copy it. Do not invent one.

Forbidden in every spoken and written line: "CBT-I therapy," "treat insomnia disorder," "diagnose," "cure," "stay until you sleep 8 hours."

Allowed: "CBT-I-informed behavioral sleep coaching" and "research-backed sleep education and habit protocol."

---

1. Personalize sheet (founder, 15 minutes, Week 0)

Fill once after kickoff fields exist. Paper or a local blank page. No cloud form. No person-looking dummy. Use C-00x in rehearsal. client_code is a short ID like C-001, used instead of a name on work sheets.

Founder time budget for this sheet: 0.25h (Monash KEEP). If it runs longer, you are adding modules. Stop.

---

2. Founder spoken close at Week 0 Install (3 to 4 minutes)

Say this live at the end of Install / kickoff. Do not send it again as a welcome note. Hands three paper (or private-doc) objects: this script, the Night-Before Decision Log (file 13), the Morning Restart Card (file 14). Audio for file 13 is UNBUILT; the page is enough.

Spoken text (founder, ~3.5 min):

"Three objects. This is the First 72 Hours script. This is the Night-Before Decision Log. This is the Morning Restart Card.

First win, for these 72 hours, is the first completed night protocol. That means tomorrow morning you fill the diary and you mark the ticks you were assigned. It is not a target number of hours. I will not score the night by how long you slept.

Your rise time is [rise_time_local], local to [tz_name], all seven days. Protect that rise.

Earliest bed is [earliest_bed_or_NONE]. If I said NONE, you wait for sleepiness. Sleepy means heavy-eyed, nodding, hard to keep the eyes open. Tired-and-wired does not count. You still rise at the same time.

Bed is for sleep or sex. If you are clearly awake, you leave the bed and go to [out_of_bed_place]. Dim. Boring. Return when sleepy. Repeat. Do not watch the clock to decide. Turn the clock away.

Wind-down starts at [wind_down_start_local]. Same steps Smith wrote. Phone and clock out of reach after you get into bed.

At [decision_log_time], default 18:00 your time, you fill the Decision Log. Four minutes. Not in bed. You decide the night then. You do not decide it at 23:00.

If a late call blows 18:00, you fill the log at the next moment you are not in bed, using the late-call move you already wrote.

If the night is messy, you do not spiral. In the morning you run the Restart Card: rise on time, light or other assigned anchor, fill the diary and ticks, no catch-up nap, run the day unless a safety item is in play, Decision Log again at 18:00. Leaving the bed last night was the protocol. The card does not repair sleep. The morning was already decided.

I will read your diary. I send two named diary replies a week, in the slots we wrote: [founder_async_windows]. I am not writing you every day. If a night row is missing for 48 hours, that is a separate check, not a daily chat.

If breathing pauses, gasping, legs that force you up, heavy sleepiness when you must be alert, a swing into very little sleep with unusually high energy, a seizure, pregnancy, or safety-critical work is in play, you stop the protocol and you contact a physician. I do not diagnose. I pause coaching and I send the referral path. Keeping the coaching does not override a stop.

Read the script tonight before wind-down. Do not add extra reading."

Timer. End. Do not add a hygiene lecture. Do not add a community invite.

---

3. Client hour 0 → 72 (client does the work)

Times are client-local. Founder does not ping this sequence. Founder may scan internally.

Hour 0 (end of Install)

You have the script, the Decision Log page, the Restart Card. You can say, in your own words: rise time, out-of-bed place, "leave the bed if clearly awake," Decision Log at 18:00. You are not asked to activate yourself or to invent a plan.

Night 1

1. Wind-down at wind_down_start_local. Same written steps.
2. Last work or last call ends at the cutoff you will write at 18:00 tomorrow; tonight, end work before wind-down if you did not yet have a log.
3. Phone and clock out of reach. Charging place is not the bed.
4. Get into bed only when sleepy. If earliest_bed_or_NONE is a time, also not before that time.
5. Bed = sleep or sex. Messages, email, video, planning, rumination: somewhere else.
6. If clearly awake: leave the bed. Go to out_of_bed_place. Return when sleepy. Repeat.
7. Do not watch the clock. Do not log overnight.

Morning 1

1. Rise at rise_time_local. Same as tomorrow and the next day.
2. Morning light or the other circadian anchor you were assigned. Outdoor light in the first hour if weather and street safety allow. No lux target. No light-box sale.
3. Fill the morning diary (file 03 fields). Guess in round numbers. One fill. No overnight notes transferred from 03:00.
4. Mark the assigned ticks. A honest no is a mark. A blank is not.
5. No catch-up nap.
6. If the night was messy: run the Restart Card (file 14). Do not wait for a founder message to start the morning.
7. Do not drive if you are drowsy. Safety outranks the calendar.

Completed Night 1 protocol = this morning's diary filled + assigned ticks marked.

18:00 Decision Log (after Morning 1)

Four minutes. Not in bed. File 13. Copy tomorrow's rise. Do not renegotiate it. Write earliest bed or NONE, wind-down start, last-call cutoff, pre-decided late-call move, out-of-bed place, not-in-bed list. Tick: "I am not deciding this at 23:00." Tick completed near 18:00.

Night 2

Run what the 18:00 log already decided. Same Bootzin-line rules as Night 1. Same rise protection.

Morning 2

Same as Morning 1. Diary + ticks. Restart Card if the night was messy.

Completed Night 2 protocol = this morning's diary filled + assigned ticks marked.

18:00 Decision Log (after Morning 2)

Same page. New date. Copy rise again. Do not bargain because Night 2 felt ugly.

Night 3

Run the log. Same rules.

Morning 3 (close of 72 hours)

Diary + ticks. Restart Card if needed. You have now had three chances at a completed night protocol. One completed night is the first win for this script. Three completed nights is attendance, still not a sleep-hours prize.

Founder reviews internally at hour 72 using file 09. You are not asked to declare yourself activated.

---

4. Assigned ticks in these 72 hours

Mark each night (yes / no, not blank):

Attendance for a night = diary filled and required ticks marked. Hours slept do not decide attendance.

---

5. If / then

Client events. Founder outbound only when the table says so.

---

6. Safety abort (no self-diagnose)

Client does not name a disorder for themselves. Client reports facts. Founder does not diagnose.

Async paste (end of every outbound):

"If breathing pauses, gasping, legs that force you up, heavy sleepiness when you must be alert, a swing into very little sleep with unusually high energy, a seizure, pregnancy, or safety-critical work is in play, stop the protocol and contact a physician. I do not diagnose. I will pause coaching and send the referral path."

Live, shorter:

"If any of the safety items we listed at the start show up, we stop the window and I refer. I do not diagnose. Tell me if one is in play."

Hot list (facts, not labels you assign): apnea signs, RLS-pattern symptoms, breathing problems, high sleepiness, bipolar/mania signs, seizures, safety-critical work, pregnancy.

---

7. Two copy-paste async lines (showing up, zero sleep numbers)

These are instruments. They are not a daily loop.

When Hour 0 may be sent: only if the spoken close in §2 did not happen on the Install call (call dropped, or Install was async). If §2 was spoken, do not send Hour 0 again. Hour 0 is a kickoff remnant. It is not a diary reply (no night exists yet). Do not also send a separate welcome.

When Morning 1 may be sent: only after the Morning 1 diary row exists. It is a diary reply. It consumes one of the two named weekly slots. If Morning 1 diary is missing, send nothing. If it is still missing at 48 hours, file 08.

Do not send a Night 2, Morning 2, Night 3, or Morning 3 founder line as a standing habit.

Hour 0 (kickoff remnant only)

"You have the First 72 Hours script, the Decision Log, and the Restart Card.

First win is the first completed night protocol: tomorrow's diary filled and the ticks marked. I am not scoring hours.

I read the diary. I send two named replies a week, in the slots we wrote. I am not writing you every day. If a safety item from the start is in play, stop and tell me. I do not diagnose."

Morning 1 (diary reply; counts as 1 of 2 weekly)

"I have this morning's diary and ticks. You showed up for the protocol. That is the official count I use.

Keep tonight's 18:00 Decision Log. Four minutes. Not in bed.

If a safety item is in play, stop the protocol and contact a physician. I do not diagnose."

Zero SOL, ISI, TST, SE, WASO, wearable scores, or "you slept X."

---

8. Pointer to the founder loop

Founder operations (handoff fields, candidate A–J watch, hour-72 internal checklist) live in file 09. Smith owns DM → calendar → Zoom → invoice → kickoff and the day-7 first-win flags. This file does not replace 09. This file does not ask the client to run 09.

---

What goes wrong / how you catch it (file 12)

What goes wrong: founder sends a good-morning note on Morning 1, 2, and 3 "to hold them," then still sends two weekly replies and a 48h chase.

How you catch it: stop rule in the Rule. Standing = two named diary replies. Hour 0 rides in Install. Morning 1 is one of those two if the diary exists. File 08 is a trigger.

What goes wrong: founder tells the client the first win is an 8-hour night, or freezes candidate A as "activated."

How you catch it: first win here = completed night protocol. File 09 forbids a frozen activation point before cohort 1 day 42.

What goes wrong: founder writes an earliest bedtime on Night 1 to look organized, before Jomini set a window.

How you catch it: earliest_bed_or_NONE. Default NONE. Window at end of Week 1.

What goes wrong: client is asked to "activate yourself" and build a seventh module.

How you catch it: §3 hour 0. Client runs six items. Founder holds. Subtract (Script 6) if they ask for more.

What goes wrong: Restart Card or spoken close includes "you failed" or "sleep 8 tonight."

How you catch it: file 14 banned box. Rewrite from §2.

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Bedell Smith (Install / kickoff clock, channel, wind-down write); Jomini (window timing, Bootzin-line rules, circadian pick); Monash (KEEP: First 72 Hours as time-to-first-win); Slim (official Day-7 first-win count); Steuben (screen, collection, spoken claims) Evidence: Monash KEEP in offer/01-OFFER-ARCHITECTURE.md (First 72 Hours Install, personalized 0.25h; first win = first completed night protocol). Jomini sleep-science/01-modular-curriculum.md Module B rules and window-at-end-of-Week-1. Jomini sleep-science/04-happy-client-sleep-numbers.md for the sleep-number half (Davout does not score it here). Stop rule 20 August 2026 on 2×/week standing diary replies. File 09 left in place as the founder loop. File 04 Script 1 aligned as Install-close remnant, not a fourth slot. Confidence: 0.83 Residual uncertainty: Official Day-7 first-win is Slim ops/03. This script uses the 72-hour KEEP definition only. window_held when earliest_bed_or_NONE = NONE is a marking convention, not a Jomini column rename. Counsel-engagement residual is not honest; nothing here may go live. File 13 audio stays UNBUILT.

Night-Before Decision Log

1-page log + 12-minute spoken walkthrough (audio UNBUILT)

Internal draft. NOT LIVE. Page: DRAFT. Walkthrough script: DRAFT. Audio: UNBUILT. No audio file exists on disk. Do not record, host, or send a walkthrough file. Do not collect a filled log from a real person. Min-path runs with this page alone. This is practice paper. Do not run real clients yet.

Owner: Davout (delivery, habit hold, stay-with-it) Operator: 이성재, Seoul Date of draft: 20 August 2026 (KST) Language: English only Sister objects: file 12 (First 72 Hours script), file 14 (Morning Restart Card)

---

Rule

Decide the night at 18:00 local, not at 23:00. Four minutes. Never in bed. If 18:00 is missed, fill the log at the next moment you are not in bed. Use the pre-decided late-call move. Do not redesign the night under the duvet.

Fields are process only. No SOL, no ISI, no hours slept, no wearable scores, no "how bad was last night." SOL is time to fall asleep.

This page is a CLIENT instrument. Founder does not send an 18:00 reminder as a standing note. Standing founder-to-client notes remain two named diary replies per week (stop rule). A diary is the morning form where the client writes last night's sleep times. Ticks are yes/no marks that they did each assigned habit that day. A missed log is not a file 08 trigger by itself.

Optional watch only: founder may notice whether a log was ticked. Do not add a 7th required attendance tick without Napoleon.

Audio is not on disk. Founder may record once later (about 30 minutes with retakes). Replay cost at 10 clients is near zero. Until a file exists, speak from §5 in rehearsal and hand the page.

---

1. Use

---

2. One-page log (copy onto paper or a private doc)

Rehearsal: leave values blank. Do not invent a person.

NIGHT-BEFORE DECISION LOG
Status of this page: DRAFT / NOT LIVE
Audio walkthrough: UNBUILT

date: ____________________
tz_name: _________________

1. Tomorrow rise (COPY from the written protocol. Do not renegotiate.)
   rise_time_local: __________

2. Earliest bed or NONE
   earliest_bed_or_NONE: __________
   If NONE: wait for sleepiness. Protect rise.
   If a time: not before that clock, even if sleepy earlier.

3. Wind-down start
   wind_down_start_local: __________

4. Last work / last call cutoff
   last_call_cutoff_local: __________

5. Pre-decided late-call move (pick one; write the words)
   [ ] Decline or move the call to writing
   [ ] Hard stop at last_call_cutoff_local; remaining points async
   [ ] Take the call; run the already-written short wind-down after
   [ ] Other (one line, no new module): __________________________

6. Out-of-bed place (dim, boring)
   out_of_bed_place: __________

7. Not-in-bed list (things that leave the bed tonight)
   ______________________________________________________________

8. If clearly awake
   Leave the bed. Go to out_of_bed_place. Return when sleepy. Repeat.
   Do not watch the clock to decide.

9. Morning already decided
   If the night is messy I run the Morning Restart Card (file 14).
   I do not bargain the rise at 06:00.

10. The 23:00 line
    I am not deciding this at 23:00.

11. Tick
    [ ] Completed near 18:00 local (or at the next not-in-bed moment)

Print or pin one blank. Fill a new date each evening. Do not keep last night's late-call story in the bed.

---

3. Field notes (founder + client)

---

4. Bootzin-line rules this page serves

Coaching rules. Not a therapy protocol name on the page the client stares at.

1. Bed when sleepy, and inside the window once a window exists.
2. Bed = sleep or sex.
3. If clearly awake, out of bed to the dim boring place.
4. No clock-watching.
5. Same rise, 7 days.

Window itself is set at the end of Week 1 after diary baseline and screen clear (Jomini). Until then, NONE plus sleepiness-wait plus protected rise is the correct fill.

---

5. Twelve-minute spoken walkthrough SCRIPT (DRAFT)

AUDIO NOT ON DISK. AUDIO UNBUILT. Do not look for a file. Min-path = the page in §2. This script is for a later single recording (about 30 minutes with retakes). Replay at 10 clients ≈ 0 founder hours.

Rehearse by reading aloud. Do not upload. Do not send a private podcast.

Timer on. Speak in this order. If you run long, cut examples, not the safety line.

0:00–1:00: Why 18:00

"This is the Night-Before Decision Log. One page. Four minutes at about 18:00 your time. You fill it sitting up, not in bed.

The job is to decide tonight's night now. Late calls, wind-down, and what you do if you are awake get written here. At 23:00 you run the page. You do not invent a new plan.

There is no audio file yet. The page works alone. If you are hearing a recording later, it is this same script."

1:00–3:00: Rise time, copy only

"Line 1 is tomorrow's rise. Copy it from the written protocol. Same time you already agreed, all seven days.

You do not renegotiate rise because today was heavy, or because last night was messy, or because a meeting moved. If a true safety item is in play, you stop the protocol. That is a different door. It is not a 15-minute snooze.

Write the clock time. Move on."

3:00–5:00: Earliest bed or NONE

"Line 2 is earliest bed, or the word NONE.

NONE is common in the first week. The restricted window, if you get one, is set at the end of Week 1 after a diary baseline and a clear screen. Do not invent a bedtime to look disciplined.

If NONE: wait for sleepiness. Sleepy means heavy-eyed, nodding, hard to keep the eyes open. Tired-and-wired does not count. You still protect the rise.

If a clock time is written: do not get into bed before it, even if you feel sleepy earlier. If you are not sleepy at that clock, you wait. You still rise on time."

5:00–7:00: Wind-down and last-call cutoff

"Line 3 is wind-down start. Copy the time and the steps already written. Same order every night. Phone and clock will be out of reach after you get into bed.

Line 4 is last work or last call cutoff. Pick a clock that leaves the wind-down intact. Write it. A cutoff you do not write will lose to the next calendar invite."

7:00–9:30: Late-call example

"Line 5 is the late-call move. You pick it now, at 18:00, while you can still think.

Example. It is 18:00. You already know a board pack might explode at 21:30. You do not wait until 21:30 to decide what kind of person you are.

You tick one box tonight:

One: decline or move the remaining points to writing.

Two: take the call, hard stop at the cutoff you wrote, remaining points async.

Three: take the call if it is truly immovable, then run the already-written short wind-down. You do not invent a new wind-down at 22:10.

Write the one line. When 21:30 arrives you execute the box. You do not reopen the log in bed.

If 18:00 itself is blown because a call ran over, fill this page at the next moment you are not in bed. Use last night's move if you have one. Then write tomorrow's move."

9:30–10:45: Out-of-bed place and not-in-bed list

"Line 6: name the place. Chair, sofa, other room. Dim. Boring. Chosen now so 02:00 you are not shopping for a vibe.

Line 7: list what is not allowed in the bed tonight. Laptop. Inbox. Slides. News. Planning pad. The bed is for sleep or sex.

Line 8 is already printed. If you are clearly awake, you leave the bed. You go to the place. You return when sleepy. You repeat. You do not watch the clock to decide you have been awake 'long enough.' Turn the clock away."

10:45–11:30: Morning already decided

"Line 9: if the night is messy, you already know the morning. You will run the Morning Restart Card. Rise on time. Light or other assigned anchor. Diary and ticks. No catch-up nap. Run the day unless a safety item stops you. Decision Log again at 18:00. Leaving the bed was the protocol.

The Restart Card does not claim it repairs sleep. It stops the spiral. You do not wait for a message from me to start the morning.

Line 10: say it. I am not deciding this at 23:00.

Line 11: tick completed near 18:00, or at the next not-in-bed moment."

11:30–12:00: Safety line. Stop.

"If breathing pauses, gasping, legs that force you up, heavy sleepiness when you must be alert, a swing into very little sleep with unusually high energy, a seizure, pregnancy, or safety-critical work is in play, stop the protocol and contact a physician. I do not diagnose. I pause coaching and I send the referral path.

This page does not treat a disorder. It does not promise hours. It does not ask you to stay in bed until you sleep.

Timer. You are done. Put the page where you can reach it at 18:00 tomorrow. Do not take it into the bed."

---

6. Founder time (later, after Legal)

Do not add the completed-tick to the six attendance ticks in file 03 without a Napoleon write.

---

7. How this sits next to files 03, 08, 09, 12, 14

• File 03 attendance stays diary + the six ticks. This log is optional watch.
• File 08 does not fire because a Decision Log was blank. File 08 fires on 48h diary silence or 3 consecutive window breaks.
• File 09 founder loop is unchanged.
• File 12 hands this page at Install and names 18:00.
• File 14 is the morning object this page points to. Different job from milestone cheer cards (file 05).

---

What goes wrong / how you catch it (file 13)

What goes wrong: founder records a 40-minute "sleep masterclass," titles it CBT-I therapy, and promises 8 hours if they fill the log.

How you catch it: §5 cap 12 minutes. Forbidden language list. No hours promise. Audio still UNBUILT until Legal.

What goes wrong: founder adds decision_log_done as a seventh required tick so the official count looks tighter.

How you catch it: Rule and §6. Optional watch only. Napoleon must write a seventh tick.

What goes wrong: founder texts "did you do 18:00?" every evening.

How you catch it: stop rule. Two weekly diary replies. This page is client work.

What goes wrong: client fills SOL and "hours I will sleep" on the page because empty boxes feel medical.

How you catch it: §2 fields are closed. No SOL/ISI/hours. Tear that draft. Recopy §2.

What goes wrong: missed 18:00 becomes a shame event or a file 08 chase.

How you catch it: §1. Next not-in-bed moment. File 08 stays on diary silence and window breaks.

---

Status block

Status: DRAFT / NOT LIVE. Page DRAFT. Walkthrough script DRAFT. Audio UNBUILT (not on disk). Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Monash (KEEP: Night-Before Decision Log, record once); Jomini (window timing, Bootzin-line rules); Bedell Smith (wind-down write, channel); Steuben (recording as a later media asset, collection); Slim (hours: replay about 0 at n=10) Evidence: Monash offer/01-OFFER-ARCHITECTURE.md KEEP line (1-page + 12-min recorded walkthrough, record once; decide at 18:00). Jomini Module B / Module C timing (window at end of Week 1). Stop rule: no daily founder note. File 03 tick list left at six. Confidence: 0.85 Residual uncertainty: Audio file does not exist; min-path depends on the page. A later recording still needs Steuben media/claims pass. Whether Napoleon later wants a seventh tick is open; this file votes no for v1. Counsel-engagement residual is not honest; do not record for clients.

Morning Restart Card

After a messy night. Stops the spiral. Does not claim it repairs sleep.

Internal draft. NOT LIVE. No health data on this card. Do not print ISI, SOL, WASO, SE, TST, hours slept, wearable scores, or diagnoses. Do not mail or message this card to a real person. Do not open a live form. This is practice paper. Do not run real clients yet.

Owner: Davout (delivery, habit hold, stay-with-it) Operator: 이성재, Seoul Date of draft: 20 August 2026 (KST) Language: English only Job: Restart after a messy night. Not a milestone cheer (that is file 05).

---

Rule

Hand this card at Week 0 Install with file 12 and file 13. Re-point to it after a messy night. Re-point happens inside a named weekly diary reply, or inside a trigger touch (safety / 48h silence / cancel). A diary is the morning form where the client writes last night's sleep times. Ticks are yes/no marks that they did each assigned habit that day. Do not send a same-morning pep note as a new standing slot.

Standing founder-to-client notes stay two named diary replies per week (stop rule). The client runs this card without waiting for a founder message.

The morning was planned the night before (Decision Log, file 13). This card does not repair sleep. It does not widen a window. A window is the assigned hours they may be in bed. It does not add a module.

No health data on the card. Digital send, after Legal only, is never after 20:00 client-local, and never inside the window.

---

1. Card front (numbered moves)

Print as one page, front. Client-local clock. No diary numbers.

MORNING RESTART CARD                          DRAFT / NOT LIVE
No health data. No hours. No scores.

After a messy night, run these in order.

1. Rise on time.
   The rise you already wrote. Do not renegotiate it this morning.

2. Light / assigned circadian anchor.
   Outdoor light in the first hour if weather and street safety allow,
   or the other anchor you were assigned. No lux target.

3. Fill the diary and mark the ticks.
   One morning fill. Honest nos count as marks. Blanks do not.
   Guess in round numbers. Do not reconstruct the night from a wearable.

4. No catch-up nap.
   Do not "make up" the night. If sleepiness is unsafe, see the back.

5. Run the day unless safety.
   Work the calendar you already had.
   Do not drive if you are drowsy. Safety outranks the day.

6. 18:00 Decision Log.
   Four minutes. Not in bed. File 13. Decide tonight now.

7. Leaving the bed last night was the protocol.
   If you got up and went to the dim boring place, you ran the rule.
   That does not need a founder verdict this morning.

---

2. Card back (safety + banned box + allowed lines)

BACK                                          DRAFT / NOT LIVE

SAFETY FLAGS → STOP
If any of these are in play, stop the protocol.
Contact the founder on the named channel. Write the word safety.
The founder refers. The founder does not diagnose.
Keeping the coaching does not override a stop.

Facts to report (do not self-diagnose):
- Breathing pauses, gasping, loud habitual snoring plus heavy sleepiness
- Legs that force you up, urge-to-move at rest in the evening
- Heavy sleepiness when you must be alert; drowsy driving; nodding off
- Very little sleep with unusually high energy (mania-like swing)
- Seizure
- Pregnancy
- Safety-critical work (the job itself is the flag)

BANNED ON THIS CARD AND IN THE MARGIN
- Hours slept, "you slept X," "sleep 8 tonight"
- ISI, SOL, WASO, SE, TST, wearable scores
- "You failed"
- "This repaired your sleep"
- "This treated your insomnia"
- A testimonial ask
- A coupon or results guarantee

ALLOWED ONE-SENTENCE LINES (pick one; zero numbers)
A. You showed up for the morning protocol. That is the work.
B. The morning was already decided. Run the card. Fill the diary.
C. Leaving the bed was the rule. Rise, light, diary, 18:00.

Founder: 이성재  |  Seoul  |  coaching, not a clinic

---

3. Three allowed one-sentence lines (zero numbers)

Use at most one, on the card or in a re-point note.

1. "You showed up for the morning protocol. That is the work."
2. "The morning was already decided. Run the card. Fill the diary."
3. "Leaving the bed was the rule. Rise, light, diary, 18:00."

Do not stack all three. Do not personalize with a sleep number. Do not add "proud of your 6 hours."

---

4. When to hand, when to re-point

Digital default until Steuben clears a postal processor. Digital still obeys the 20:00 local cut.

---

5. What this card is not

Do not merge 05 and 14 onto one postcard.

---

6. Founder checklist (after Legal; paper today)

1. Screen still clear? If not, do not hand a restart card as if the protocol is running.
2. Front has the seven moves and zero numbers?
3. Back has safety → stop / contact founder / founder refers?
4. Banned box present?
5. At most one allowed sentence?
6. If digital: clock-legal (not after 20:00 local, not inside the window)?
7. If this is a re-point: is it inside a weekly diary reply or a real trigger? If you are about to open a third standing slot, stop.

---

What goes wrong / how you catch it (file 14)

What goes wrong: founder writes "SE will recover, sleep 8 tonight" because the client sounds wrecked. SE is sleep efficiency.

How you catch it: banned box. Tear the card. Recopy §1–§3.

What goes wrong: founder sends the card at 07:10 every morning "in case last night was messy," plus two weekly replies.

How you catch it: Rule. Client runs the card. Standing cadence is two diary replies. 07:10 daily is a forbidden loop.

What goes wrong: card is used as a D21 cheer with "you made it three weeks."

How you catch it: §5. File 05 owns cheers. This file owns restart.

What goes wrong: back of the card asks the client to tick "I have apnea" as a self-diagnosis.

How you catch it: facts to report. Founder refers. No self-diagnose.

What goes wrong: digital card lands at 21:30 local with last night's diary screenshot attached.

How you catch it: no health data. No diary shot. No send after 20:00 local.

---

Status block

Status: DRAFT / NOT LIVE Owner: Davout (delivery, habit hold, stay-with-it) Co-owners: Monash (KEEP: Morning Restart Card); Jomini (rise, light/anchor, stimulus-control meaning of leaving the bed); Bedell Smith (Install hand, channel); Steuben (no health data, digital/postal clock, claims); file 05 stays the cheer owner Evidence: Monash offer/01-OFFER-ARCHITECTURE.md KEEP line (1-page; after a messy night; stops the spiral; does not claim it repairs sleep; morning planned the night before). File 05 job split (cheer vs restart). Stop rule: no daily founder note. Safety list matches charter / file 04 abort language. Confidence: 0.88 Residual uncertainty: Physical card vendor and cross-border postage wait on Steuben processor list. Digital-only is the default. Whether a later agent tries to merge this with file 05 is a known failure mode; keep the files split. Counsel-engagement residual is not honest; do not send.

Handoff residuals: Davout to Napoleon

Delivery packet, 20 August 2026 (KST)

BANNER. Internal draft. NOT LIVE. This page is the one-page send. The rest of the packet stays in /workspace/sleep-coaching-business/delivery/.

---

Rule

Davout drafted the retention hold. Nothing is live. No Majors created. No other agents contacted. No Skool. No forms. No client PII invented.

Standing founder→client notes = two named diary replies per week (stop rule, 20 August 2026). Daily scan is internal. 48h diary silence is a file 08 re-engagement touch, not a fifth standing note. Do not add a Day 1 / Day 2 / Day 3 founder ping sequence.

---

1. Paths (absolute)

All files sit here:

• /workspace/sleep-coaching-business/delivery/00-index.md
• /workspace/sleep-coaching-business/delivery/01-domain-operating-charter.md
• /workspace/sleep-coaching-business/delivery/02-accountability-retention-system.md
• /workspace/sleep-coaching-business/delivery/03-attendance-instrument.md
• /workspace/sleep-coaching-business/delivery/04-reach-out-cadence-and-aca-scripts.md
• /workspace/sleep-coaching-business/delivery/05-milestone-notes.md
• /workspace/sleep-coaching-business/delivery/06-event-calendar-21-42-63.md
• /workspace/sleep-coaching-business/delivery/07-exit-interview-and-cancel-tree.md
• /workspace/sleep-coaching-business/delivery/08-reengagement-silent-diary.md
• /workspace/sleep-coaching-business/delivery/09-first-72-hour-activation-loop.md
• /workspace/sleep-coaching-business/delivery/10-community-linking-design.md
• /workspace/sleep-coaching-business/delivery/11-happy-client-retention-half.md
• /workspace/sleep-coaching-business/delivery/12-first-72-hours-script.md
• /workspace/sleep-coaching-business/delivery/13-night-before-decision-log.md
• /workspace/sleep-coaching-business/delivery/14-morning-restart-card.md
• /workspace/sleep-coaching-business/delivery/99-handoff-residuals.md

---

2. What is done

• Standing Davout charter with transfer rule (copies to any later Davout agent).
• Spine: 5 Horsemen + 9-item Churn Checklist translated to sleep behavior. Gym % left in the gym.
• Attendance AND-gate: CSD night + ticks. Dummy columns only. Carney et al., 2012 field names locked for Jomini.
• 2×/week named diary replies (stop rule). Six ACA scripts, safety-redirect, clock rules. No daily note loop.
• Milestone notes without health data (file 05 = cheer). Morning Restart Card is a different job (file 14).
• D21 / D42 / D63 agendas that end ≥3h before window, never after 20:00 local. 1:1 until community live.
• Cancel / pause / refer tree. Exit script. Attempt rate 100%. No save-% as the number we watch. No invented refund percent.
• Re-engagement: 48h diary, 3 consecutive window breaks (3-in-7 = watch), cap 3 touches / 7 days. Trigger, not a standing slot.
• Founder 72h loop (file 09) with Smith handoff fields. Candidates A–J listed. Discovery method at day 42. None frozen. One-line pointer to file 12.
• Client-facing First 72 Hours script + personalize sheet (file 12). First win for that script = first completed night protocol (diary + ticks). Not TST.
• Night-Before Decision Log page + 12-minute walkthrough script (file 13). Audio UNBUILT. No file on disk. Min-path runs with the page alone.
• Morning Restart Card (file 14). No health data. Hand at Install; re-point after a messy night inside a weekly reply or a trigger.
• Community design with NOT LIVE banner. Monash TRIM. Not a Week 0 bonus. Skool is a candidate, not a decision.
• Retention-half happy-client + join keys. Jomini sleep-number half exists at sleep-science/04-happy-client-sleep-numbers.md. Completion compared to ~56% automated dCBT-I floor.
• Founder time math at n=10: live-heavy ~6.3h/week; required default async-first ~5.5h/week; cut scope rather than thin the hold.
• Bonus veto for undeliverable solo extras.

---

3. Confidence per file

Packet-level confidence: 0.86. This is practice paper. Do not run real clients yet. (20 August 2026). Official Day-7 first-win locked to Slim ops/03. File 13 audio stays UNBUILT. Unsafe as a launch license.

---

4. What waits on peers

Peers now have drafts. What still waits is listed. Do not treat a draft as a live license.

Jomini (sleep science / program)

Drafts exist: sleep-science/00 through 05, including 04-happy-client-sleep-numbers.md.

Still waits:

• ISI license before client-facing items or isi_t0 / isi_t_end collection.
• For-profit permission for the official Consensus Sleep Diary form.
• Per-client circadian pick (morning light vs fixed rise) written onto the client row.
• Any later alias map. Until then file 03 names win.
• A named pre-window score if Jomini wants one. Davout's operational choice until then: rise-time hold + stimulus control + diary.

Bedell Smith (Funnel)

Drafts exist: funnel/01 through 08, including 05-7-day-first-win-onboarding.md.

Still waits:

• client_code agreement if Smith wants a format other than C- + three digits.
• Residual closed (Napoleon, 20 August 2026): Bedell confirmed funnel/05 is Slim ops/03 only. The ≥4/7 bar is gone. Smith installs; Slim scores. Davout does not rewrite funnel/05.

Steuben (Legal)

Blue Book drafts exist (legal/01 through 25, including screen SOP 05, CSA 07, refund 13).

Still waits:

• Honest counsel-engagement residual (Certificate CS-1 / CS-2). Drafts are not counsel sign-off.
• Kill-authority confirmation if anyone opens a sheet, a room, or a Decision Log recording early.
• Live replacement of Davout's generic stop with counsel-cleared screen language on real calls.

Monash (Price / offer)

Drafts exist: offer/01-OFFER-ARCHITECTURE.md (KEEP stack; First 72 Hours / Decision Log / Restart Card; price written there).

Still waits:

• Davout will not restate or lock a live price from this packet.
• Seat cap vs hours if Napoleon changes Slim's 3-seat cycle.

Slim (ops)

Drafts exist: ops/00 through 11, including ops/03-day-7-first-win-standard.md.

Closed (stop rule, 20 August 2026):

• Official Day-7 first-win = Slim ops/03 only. Any one of: (a) 3 consecutive wind-down nights; (b) 3 consecutive clock-cut nights; (c) diary + ticks ≥5 of first 7 nights.
• Candidate H (all three) stays a guess we will test after the first group reaches day 42, on the day-42 discovery table. It is not the official count.
• Official counts stay unmerged. Field slim_d7_first_win = a | b | c | miss. Field act_H is separate.
• Residual closed: funnel/05 matches Slim ops/03. Davout does not rewrite funnel/05.

---

5. What Davout will not do

1. Collect client or prospect data, including a friend's "test" diary.
2. Stand up Skool, Circle, Slack, Discord, a live form, or an email capture.
3. Create Majors or Sergeants, or contact other agents, or contact the Emperor.
4. Diagnose, treat a disorder, or promise hours slept / AHI / cure.
5. Widen the sleep window to soothe week 1–2 misery.
6. Override medical stop/refer to keep a seat.
7. Set a save-% as the number we watch, or a 90% completion claim, or import gym monthly churn %.
8. Freeze one activation behavior as "the" point before cohort 1 day-42 scoring.
9. Invent a refund percent or a hospital list.
10. Put ISI, SOL, WASO, SE, TST, or diagnoses on a milestone card, Restart Card, Decision Log, or community post.
11. Run late events (after 20:00 client-local, or ending inside 3 hours of window open).
12. Write outside /workspace/sleep-coaching-business/delivery/.
13. Average retention-half and sleep-number-half into a vanity composite in v1.
14. Spend "1/5 CAC" as if CAC were known. Method note only.
15. Add a daily founder note loop, or stack welcome + two weekly replies + 48h as four standing slots.
16. Record or host the Decision Log walkthrough while audio is UNBUILT and Legal is closed.
17. Merge slim_d7_first_win with act_H, or report H as the official Day-7 first-win.
18. Add a seventh required attendance tick for the Decision Log without a Napoleon write.

---

6. Assumptions Davout had to make (explicit)

1. Trigger B pick: action = 3 consecutive broken windows; watch = 3-in-7. Tasking required a pick.
2. Pause length: default 14 days, hard cap 28 without a new conversation. Not a statute.
3. client_code format: C- + three digits. Smith may override.
4. Async-first default at n=10 so the hold fits a solo founder. Live-heavy 4h touches + diary does not.
5. G scored two ways (consecutive 7 and first-7 calendar) so discovery does not pretend one definition.
6. Direction enum proposal (improved | flat | worse | not_scored) for Jomini. Replaceable. Jomini 04 is direction-first.
7. Slim official Day-7 first-win is locked (ops/03, any one of a/b/c). Candidate H remains a guess we will test after the first group reaches day 42. Official counts unmerged.
8. Trauer 2015 named; Jomini 04 restates the abstract means. Davout still does not put those means on cards.
9. ~56% / ~52–60% used as the tasked command floor / operating comparison, not re-cited as a new study.
10. Week 0 rehearsal uses paper and C-000 / C-00x dummies, never a live workbook.
11. earliest_bed_or_NONE = NONE in the first 72 hours unless Jomini already assigned a window (window at end of Week 1).
12. Hour 0 Script 1 rides inside Install. Morning 1 async is a diary reply and consumes one of the two weekly slots.

---

7. Suggested Napoleon next moves

1. Hold the Legal gate. Do not let a "soft friend cohort" open a sheet. Do not authorize a Decision Log recording.
2. Done. Official Day-7 first-win = Slim ops/03. H stays a guess we will test after the first group reaches day 42. Do not ask Davout to merge the cells.
3. Confirm the 2×/week diary-reply standing cadence stays the only founder→client note loop.
4. Use Jomini 04 with the join keys in file 11. ISI/CSD still need license/permission before collection.
5. Ask Steuben for counsel-engagement residual before any paid close; Blue Book drafts are not that residual.
6. Ask Monash / Slim for a seat cap consistent with ~5.5 founder hours/week delivery if the 3-seat cycle moves.
7. Do not authorize a community vendor.
8. If you create a later Davout agent, attach file 01 as standing orders.

---

Red team (this handoff)

What breaks: this page is forwarded as "Legal is done, run clients."

How you catch it: packet-level line. Unsafe as a launch license. Steuben Certificate still locks real-world use.

What breaks: a later agent "helpfully" fills dummy rows with Korean names to make the sheet look real.

How you catch it: no PII, including invented people. Delete.

What breaks: founder treats Slim's any-one first-win and candidate H as the same cell and reports 100% first-win.

How you catch it: §4 lock. slim_d7_first_win and act_H are different fields. Do not merge.

What breaks: founder records the file 13 walkthrough tonight and DMs it.

How you catch it: Audio UNBUILT. Legal closed. §5 item 16.

---

Status block

Status: DRAFT / NOT LIVE Owner: Lieutenant General Davout (Delivery, Accountability, Retention) Co-owners: Napoleon (this send); Jomini, Smith, Steuben, Monash, Slim (drafts exist; items in §4 still wait) Evidence: The fifteen sibling files in this folder (00–14 + 99); Jomini sleep-science/04-happy-client-sleep-numbers.md; Slim ops/03-day-7-first-win-standard.md (official Day-7 first-win); Smith funnel/05-7-day-first-win-onboarding.md (install; confirmed Slim ops/03 only); Monash offer/01-OFFER-ARCHITECTURE.md KEEP; Steuben legal/01-sign-off-certificate.md (draft, not counsel-approved); stop rules on 2×/week diary replies and Slim ops/03 first-win; hormozi-method-cards.md methods only. Confidence: 0.88 Residual uncertainty: File 13 audio stays UNBUILT. Counsel-engagement residual is not honest. Funnel/05 ≥4/7 residual is closed. Re-read this page if Legal residual changes.