The Loss Nobody Saw

***********************************************************************************************************************************************************************************************************************te.

Let me look at the recent progress logs and understand the site structure to plan today's good thing. Let me read a few recent logs to see what has been done recently, and look at the site structure (index.html, start-here.html, progress.json, data folder).

The site has 60 pages. Yesterday's good thing was "The Quiet Friend". Let me look at the site structure to understand the pattern: index.html, start-here.html, progress.html, and the general page structure. Let me look at the quiet-friend.html as the latest template, and check start-here.html for the list of stages to figure out what's missing — what good thing to do today.

Let me first look at index.html and start-here.html.

Now let me look at start-here.html to see the stages and identify the gaps. Let me also look at the structure of the quiet-friend.html page as a template for a new page.

Now let me look at the most recent page (quiet-friend.html) to understand the page structure as a template, and progress.json and progress.html to understand what to update. The site has 60 pages covering illness arc, grief arc, and builders. I need to pick a new good thing for today (2026-09-27).

Let me think about what's missing. Looking at the arc:

Illness arc:

• approach: ER night, parking lot, waiting room, solo appointment, hospital visit, coming home, 3am
• tests/waiting: scan guessing, waiting for results
• news: results day, news comes home, group chat news, telling work
• kids: telling the kids, kid's people, if you're the kid
• decisions/treatment: second opinion, first treatment, pharmacy line, insurance call, last treatment, plan changes, long goodbye, last visit
• life around it: the call, week-three visit, welcome-back, first ordinary tuesday
• people holding it up: second patient, sitting-with, not their therapist, quiet friend, ask off-ramp

Grief arc: coordinator checklist, funeral guide, obituary/eulogy, everyone goes home, condolence, workplace loss, goodbye builder, first holiday, one-year mark, second holiday, birthday year three

Builders: encouragement, check-in, worried friend, thank-you, apology, congrats, birthday, host thanks, neighbor, kind no, thank you for the no, receiving a yes, gentle follow-up

What's missing? Some ideas:

1. The caregiver's own medical appointment — when the caregiver gets sick/needs care too.
2. The new diagnosis nobody expected — "the good news appointment" — when results come back clear and you don't know how to feel (survivor's guilt, relief that feels wrong). Actually "results day" covers both drives home.
3. The friend who dropped the ball — the person who wasn't there during the hard season and now feels guilty; how to come back. "Thank you for being late" — the late arrival. Interesting: "The Late Friend" — for the person who missed the crisis entirely (was traveling, was in their own crisis, just failed) and now doesn't know how to come back. That's a genuinely uncovered gap!
4. Asking for the second help — when you've already asked once.
5. The money talk — when the illness costs money and the family has to talk about it / friends want to help with money (GoFundMe etiquette).
6. The meals / food train — covered briefly in week three.
7. The anniversary of the diagnosis — the "cancerversary".
8. The empty chair at the wedding / milestone — the happy event with a missing person. "The joyful day with an empty seat" — weddings, graduations, births after a death. That's a genuinely uncovered gap in the grief arc! The grief arc covers holidays, anniversaries, birthdays — but not the milestone celebrations (wedding, graduation, new baby) where the missing person aches most. That's a strong candidate.
9. When the patient is the difficult one — when the person who is sick is angry/mean, and the family is hurt. Covered partially in long goodbye (accusations that are the disease talking).
10. Telling the parents — adult child telling their aging parents about their own diagnosis. Hmm, partially covered.
11. The miscarriage / pregnancy loss — a big uncovered grief area. The site covers death of adults, but miscarriage/stillbirth/infant loss is a very common, very unscripted grief. That could be a strong candidate: "The Loss Nobody Saw" — for miscarriage and pregnancy loss, serving the parent(s) and the circle who doesn't know what to say ("at least you can try again" etc.). This is a significant gap and very helpful.
12. The divorce / breakup support — illness-adjacent? The site is mostly illness/grief/kindness. A page for when a friend's marriage ends — "the first holiday" parallels. Could work: "The End of the Marriage" — for the friend whose marriage is ending, what to say and not say ("you deserve better," trash-talking the ex backfires), and for the one going through it. Hmm.
13. The relapse / recurrence — when the cancer comes back. This is a HUGE uncovered gap in the illness arc! The arc goes: treatment, last treatment (bell ringing), first ordinary Tuesday... but recurrence — "it's back" — is one of the most devastating and common moments, and it's different from the first diagnosis: everyone is tired, the second-time fear is worse, the friends don't know whether to show up the same way, hope feels different. "The Second Time" / "It's Back" — the recurrence page. That's a very strong candidate.

Let me think about which one is best for today. The last few entries were:

• 2026-09-26: The Quiet Friend (silence/friendship)
• 2026-09-25: The Long Goodbye (dementia)
• 2026-09-24: ? Let me check quickly. Probably er-night. The summary said "the ER night as last time" for long goodbye, so 2026-09-24 was er-night.

Let me check the previous few logs to see the cadence and what recent topics were, to avoid repetition and pick something fresh.

Candidates ranked:

1. The recurrence ("It's Back") — illness arc gap, stage 5 or new. Deeply common, unscripted, three audiences natural (the one who got the news again, the one holding them up again, the circle — which often does worse the second time). The "second-time" dynamics: the crowd that showed up in round one assumes round two is handled; hope talk vs. honesty; "at least they caught it" silver linings; the scan that found it; telling people AGAIN is exhausting ("I can't do the group chat again"); the anger. This is a great fit for the site's pattern.
2. Pregnancy loss — very important but a big topic; the site leans toward illness arc; still, grief arc could extend.
3. The milestone with the missing seat (wedding/graduation/baby after a death) — grief arc extension, nice.
4. The friend who missed it / the late arrival — guilt-ridden return. Nice.

I think "It's Back — the recurrence page" is the strongest: it fills a real hole in the illness arc between "last treatment" and... well, it's the dark fork after last treatment. The site has "When the Plan Changes" (treatment isn't working) but recurrence after a successful treatment is different: the bell was rung, the season closed, and now it reopens. Let me verify plan-changes covers what so I don't overlap. Let me read plan-changes.html quickly to check.

Also check last-treatment.html briefly for overlap.

Let me read those two pages (at least their summaries/intros). Also check progress.json structure and progress.html structure for integration.

Actually, let me also consider: the file naming — "it-came-back.html"? or "the-recurrence.html"? or "second-time.html"? Maybe "its-back.html"? I'd go with "the-recurrence.html" or "its-back.html". Something human: "its-back.html" — "It's Back". Hmm, the site's pages use names like "plan-changes", "last-treatment". "recurrence.html" or "the-recurrence.html". I'll go with "its-back.html" — Actually let me think: titles in the nav: "The Emergency Room Night", "When the Plan Changes", "The One-Year Mark". A natural title: "The Recurrence" or "It's Back". I'll title it "It's Back" with file its-back.html. Hmm, apostrophes in file names are fine without. "its-back.html". Alternatively "second-diagnosis.html". I'll go with its-back.html.

Wait — also consider the second candidate about money, "The Money Talk" — illness + money is big. But recurrence is stronger emotionally and fills the arc.

Let me read plan-changes.html and last-treatment.html to differentiate. Also check the structure of quiet-friend.html as a template (it's the newest, with the best pattern — three sides, needs, tones, plans, unit tests harness pattern).

Let me read quiet-friend.html fully.

*********************************************************************************************************************************************************************************ge.

Let me see the rest of the script (planSteps continued, the plan builder, copy handlers, etc.) to fully replicate the pattern.

Now I understand the full page pattern. Let me check plan-changes.html to make sure the recurrence page doesn't overlap. Let me grep the key content of plan-changes and last-treatment to see what they cover.

Important: plan-changes.html already covers "the recurrence news" — "the scan that says it's not working, the recurrence news, the turn from cure toward comfort." So a recurrence page would overlap significantly.

Let me reconsider. What's genuinely uncovered?

Grief arc gaps:

• Pregnancy loss / miscarriage — not covered anywhere. Let me verify with grep for "miscarriage" across the site.
• Milestone with a missing seat (wedding/graduation/birth after a death) — the grief arc covers holidays and anniversaries but not the happy milestones.
• The late friend — the person who missed the crisis entirely.

Other gaps:

• The caregiver gets sick — the second patient covers caregiver burnout but not their own illness.
• Money / the bill / asking for financial help.
• Telling the parents (adult child → aging parents).
• The anniversary of the diagnosis ("cancerversary").
• Survivor's guilt / when you get the all-clear and your friend didn't.
• The friend whose marriage is ending (divorce support).
• The new baby when... hmm.
• Job loss — "The Layoff" — a friend losing their job. Not illness related but the site has expanded to kindness in general ("for ordinary life, which keeps happening"). A layoff page is a big unscripted life moment: what to say when someone gets fired/laid off, and being the one. Hmm, that fits "the notes in between" maybe. But it might drift off-mission. The site's center of gravity is illness/grief/caregiving/hard friendship moments. Divorce and job loss are adjacent life crises. The builders cover ordinary life. A field guide on miscarriage or the empty-seat milestone is more in keeping.

Let me check for existing coverage of miscarriage / pregnancy loss / empty seat / wedding.

Actually let me grep across all pages for keywords: "miscarriage", "pregnancy", "wedding", "graduation", "layoff", "divorce", "money", "GoFundMe".

The grep mostly worked. "miscarriage/pregnancy loss/stillbirth" only matched welcome-back-builder.html (probably as a tangential mention in a list of hard absences). So pregnancy loss is essentially uncovered.

Let me think about which good thing to do today:

Option A: "The Loss Nobody Saw" — a page for miscarriage and pregnancy loss. Very common (roughly 1 in 4 known pregnancies), profoundly unscripted: the loss is invisible to the world ("nobody knew we were trying"), the condolences are famously bad ("at least you know you can get pregnant," "everything happens for a reason," "it wasn't a real baby yet"), the due date comes and goes, and the circle doesn't know whether to mention it. Three audiences fit perfectly:

• The one who lost (the mother mostly — and the often-forgotten partner): the grief is real grief; the due date is a date; the body keeps the schedule; "you can try again" is not comfort; the guilt audit is a liar; the telling-you-don't-have-to-do.
• Their partner: the second patient of this loss — expected to be the rock; gets "how is she?" and never "how are you?"; grief looks different (fixing, working) and that's not absence.
• The circle: what to say (name it as a loss, use the name if there is one, "I'm so sorry — this is a real loss"), what never to say ("at least...", "everything happens for a reason", "you can try again", "it wasn't meant to be"), the due-date calendar mark, the meals still count, the "I haven't forgotten" text months later.

Hard cases: the pregnancy after the loss (the scariest pregnancy); the friend who announces while you're grieving; the baby shower invite; the second loss; when it was earlier vs later; when nobody knew you were pregnant (the double telling: "we were expecting, and we lost the baby"); the due date; when the dark stays dark.

This is a genuinely needed page, clearly within the site's grief/care mission, and distinct from everything there.

Option B: "The Empty Seat at the Happy Thing" — the wedding/graduation/baby milestone after a death. Also good. Could be a future day.

Option C: "The Layoff" — job loss. Less core.

Option D: "The Second Patient's Appointment" — caregiver's own illness. Hmm.

I'll go with Option A: The Loss Nobody Saw — miscarriage and pregnancy loss. File name: the-loss-nobody-saw.html or pregnancy-loss.html? The site's naming style is evocative: "the-quiet-friend"... "long-goodbye.html". I'll use the-loss-nobody-saw.html — hmm, that's long. Maybe "unseen-loss.html"? Or "the-loss-nobody-saw.html" is fine (welcome-back-builder is long too). Actually let me think about title: "The Loss Nobody Saw" is evocative and true: most pregnancy losses are invisible — no funeral, no obituary, often no one even knew. That's the unique hard place.

Where does it go in the structure?

• Nav: after "birthday-year-three.html" (end of grief arc) or near grief arc. In the nav list, grief items run obituary-eulogy-starter through birthday-year-three. I'll add it after birthday-year-three.html.
• start-here: the grief arc ordered list — this loss has no position in the death-of-an-adult arc exactly... but it fits as part of the grief arc. The grief arc is "in the order the loss actually unfolds: the logistics of the first two days, the ritual of the first week, and then the long calendar of firsts." A pregnancy loss is a different arc — no funeral, no coordinator, often no public anything. I could add it to the grief arc card as a distinct entry, e.g., after the coordinator checklist? Hmm — actually it deserves its own mention: "And a different arc entirely: The Loss Nobody Saw — miscarriage and pregnancy loss, the grief with no ritual at all." I'll add it to the grief arc card with a note, and add a router moment: "We lost the pregnancy — or someone I love did."
• Page count: sixty → sixty-one.

Now, content. Let me carefully draft this page with high quality, following the established pattern:

Structure (mirroring quiet-friend.html):

1. Header hero — eyebrow, title, lede.
2. "The 60-second version" card (card today) + print button.
3. "Why this loss is its own hard place" card.
4. The tool card (screen-only): side selector — "mother" (the one who lost — the pregnant person), "partner" (the other parent / partner), "circle" (the friend/family around them). Needs per side (3 each). Name field. Tone. Messages + plans. Crisis details.
5. "For the one who lost the pregnancy" card.
6. "For the partner — the other grieving person" card.
7. "For the circle — what to say and never say" card.
8. "The hard cases" card.
9. "The rest of the arc" card — cross-links.
10. Footer.
11. Script with pure functions + DOM wiring + module.exports for tests.

Crisis details: grief after pregnancy loss can get dark; also postpartum depression/anxiety after loss. Lines: 988 US; Crisis Text Line HOME to 741741; findahelpline.com; plus PSI (Postpartum Support International) — 1-800-944-4773 (they have a helpline; the number is 800-944-4773, and text "Help" to 800-944-4773; PSI also has online groups). I should be careful with accuracy: Postpartum Support International helpline: 1-800-944-4773 (4PPD), call or text. That's correct. PSI supports pregnancy loss too. I'll include it carefully: "Postpartum Support International, call or text 800-944-4773 — yes, after a loss too."

Also important content notes (drawn from what loss parents and clinicians consistently say):

• It's real grief. The size of the grief is not set by the size of the baby or the weeks. You don't need anyone's permission to grieve, and nobody gets to grade it.
• The guilt audit is a liar: the run, the coffee, the work trip, the glass of wine before you knew — almost never the cause. Most early losses are chromosomal — the body ending a pregnancy that could not have continued. (Accurate: ~50% of first-trimester miscarriages are chromosomal abnormalities.)
• "At least" is the enemy: "at least you can get pregnant," "at least it was early," "at least you have other kids." Rule: no sentence of comfort begins with "at least."
• "Everything happens for a reason" / "it wasn't meant to be" / "God needed an angel" — don't.
• "You can try again" — the baby that was lost was not a draft.
• Use the name if the baby had one. Ask. Follow their lead.
• The due date is a date. Mark it. The calendar remembers when the world forgets. Also the anniversary of the loss.
• The physical aftermath: the body doesn't know there's no baby — milk can come in, hormones crash, postpartum body with no baby. The physical and emotional crash stack. The follow-up appointments. The bills.
• Telling work; the people who knew; the "how are you feeling?" from people who meant the pregnancy.
• The double telling when nobody knew: "We were expecting, and we lost the baby" — two pieces of news in one breath.
• The partner: expected to be the rock, gets asked "how is she?" and never "how are you?"; their grief is real but often runs on a delay or looks different (throwing into work, fixing things); they lost the same baby. "How are YOU?" is the rarest question they get.
• The circle: the loss is real, name it; "I'm so sorry. This is a real loss and I'm here"; share a memory if there was a baby known (later losses, stillbirth); the meals and the errands still count; keep showing up at month two and at the due date; don't avoid; don't ask "when will you try again?"; don't stop inviting; if they had a name, use it; let them bring it up — and YOU bring it up too ("I've been thinking about you and the baby"). Mentioning it doesn't remind them — they never forgot.
• The pregnancy after: joy and terror at once; the innocence is gone; don't say "see, everything worked out"; the anxiety is normal; milestone-by-milestone; ask how they're doing at each stage; "cautiously pregnant" is real.
• The friend who announces her pregnancy: both things can be true — happy for them, breaking for you. You're allowed to skip the shower.
• Kids: the sibling who knew.
• Hard cases: when it was stillbirth (this is a birth and a death; the naming, the photos, the memory box — not morbid, it's the only parenting they get to do; SAY the name; "born sleeping"); when there are multiple losses; when the loss was a wanted termination for medical reasons (TFMR — grief is real, judgment has no place); when people say the terrible thing; when someone asks "how many kids do you have?" (the minefield question — answers allowed: whatever you want); when the dark stays dark.
• For the one who lost: your grief is the right size; no timeline; the body needs care too (the physical recovery is real); you don't have to tell anyone anything; the guilt audit lies; the due date — plan something small; the next pregnancy anxiety; you're allowed to be happy again and sad forever at once.
• Also: practical — the follow-up care, the "products of conception" paperwork, the bill that arrives. Maybe keep physical details gentle but real.

Tool design: Sides:

• "lost" — "I'm the one who lost the pregnancy" (the mother/pregnant person). Needs:
  • "text" — The text that tells people (the announcement you never wanted to send)
  • "boundaries" — The answer to the terrible questions ("when will you try again?")
  • "duedate" — The due-date plan
• "partner" — "I'm the partner — the other parent". Needs:
  • "howami" — The honest answer when someone finally asks how YOU are
  • "support" — How to hold them up while you're breaking too (a note to self)
  • "askhelp" — The ask for help for the two of you
• "circle" — "I'm in the circle — friend, family, coworker". Needs:
  • "sorry" — The first text — the condolence that names it as real
  • "later" — The month-two / due-date text ("I haven't forgotten")
  • "never" — The words to retire (a note to self about what never to say)

Each need has warm/brief/steady variants. Each side has a 7-step plan per tone, title, closing, crisis line.

Let me now also check the test harness approach from the log: "781 unit + 20 DOM checks" — they extracted the script with a harness. I'll write a Node test harness similarly: extract script from the HTML, wrap in module, run checks. I don't know if there's an existing harness file stored somewhere; logs say "Extracted the page's script and ran node --check" and "Unit harness: 781 checks". These harnesses were probably created ad hoc in /tmp. I'll write my own in /tmp.

Let me check node availability first. Also verify progress.html structure for the archive entry format.

Let me view the top of progress.html.

Now I have a complete picture of the pattern. Today's good thing: "The Loss Nobody Saw" — a printable one-pager for miscarriage and pregnancy loss.

Let me now write the page. I'll carefully craft the content. File: /space/site/the-loss-nobody-saw.html — hmm, shorter: unseen-loss.html? Let me match the site style: titles like "The Quiet Friend" (quiet-friend.html), "The Long Goodbye" (long-goodbye.html). I'll title it "The Loss Nobody Saw" with file loss-nobody-saw.html. Hmm, or simpler pregnancy-loss.html for findability. The site favors evocative names. I'll go with loss-nobody-saw.html.

Title in nav: "The Loss Nobody Saw".

Content plan:

Hero lede: Some losses are invisible — no funeral, no obituary, often no one even knew there was a pregnancy. One in four known pregnancies ends in miscarriage, and yet the scripts don't exist... serves three people: the one who lost (the mother — the pregnant one), the partner (the other parent, the one asked "how is she?" and never "how are you?"), and the circle (what to say, what never to say, the dates to mark).

60-second version bullets:

• This is a real loss, full stop. The size of the grief is not set by the weeks.
• The guilt audit is a liar — the run, the coffee, the stress: almost never the cause. Most early losses are chromosomal — a pregnancy that could never have continued.
• "At least" is the enemy. No sentence of comfort begins with "at least."
• The baby was not a draft. "You can try again" is not comfort.
• The due date is a date. Mark it — the calendar remembers when the world forgets.
• Mentioning it doesn't remind them — they never forgot.
• The partner lost the same baby. "How is she?" is not the only question; ask "how are YOU?"
• Lines: dark that stays dark is common after loss and treatable — 988, PSI 800-944-4773, findahelpline.com.

Why this loss is its own hard place bullets:

• No ritual — no funeral, no shiva, no casseroles; the loss often has no container at all.
• The double telling: when nobody knew, the announcement and the loss arrive in the same breath — "we were expecting, and we lost the baby."
• The body keeps the schedule — the hormones crash, the milk can come in, the body doesn't know there's no baby; the physical and the emotional stack.
• The guilt audit runs at 3 a.m. — and it's a liar.
• The condolences are famously terrible — "at least," "meant to be," "try again."
• The world moves on by Tuesday; the calendar (due date, anniversary) remembers forever.
• The next pregnancy is joy and terror stacked — innocence gone.
• Everyone grieves differently in the same house — and reads the difference as distance.

For the one who lost the pregnancy (mother / the pregnant one):

• Your grief is the right size. Permission never needed; nobody grades it.
• The guilt audit is a liar: the run, the coffee, the glass of wine before you knew, the stress, the work trip — almost never the cause. Most early losses are chromosomal: the body ending a pregnancy that could not have continued. Nothing you did. Nothing you failed to do.
• The physical recovery is real — rest, follow-up care, the body on its own schedule; bleeding beyond what they told you, fever, the worst pain — that's the doctor today, not the internet.
• You don't owe anyone the news, the story, or the details. "We're not ready to talk about it" is a complete sentence; so is "I don't want to talk about anything else."
• The "how many children do you have?" question gets whatever answer you want that day. Both are true.
• Name the baby if you want to — or don't. Both are allowed.
• The due date: plan something small and yours — a walk, a candle, a meal, nothing. Whatever you do is the right observance.
• The next pregnancy, if it comes: joy and terror are allowed to share a body; milestone by milestone; tell the provider you're anxious; the anxiety is normal, not a jinx.
• The shower invite you're allowed to decline; the announcement you're allowed to mute. Happy for them and breaking for you can both be true.
• The dark that stays dark: grief is normal; grief that never eases at all deserves a professional — the doctor, a therapist, PSI (call or text 800-944-4773 — yes, after a loss), 988. You deserved the baby; you deserve the help.

For the partner — the other parent:

• You lost the same baby. Grief that looks different is not grief that's smaller — the fixing, the working, the being-strong are all shapes of it.
• You'll be asked "how is she?" a hundred times and "how are you?" almost never. Find the one person you answer honestly.
• The strong-one job is real and temporary; put it down on a schedule — one hour a week that is yours.
• You can't fix this — the job is presence, not repair. "I don't know what to say, but I'm here" is the sentence.
• Watch for the dark, in both of you — grief stacked on no sleep stacked on the hormones crashing (for her, the physical crash is real and can turn dark fast; postpartum depression is possible after a loss, at any week).
• Keep the love story visible — the loss can make two grievers feel alone in the same bed; small ordinary kindnesses are the rope.
• Say the hard sentence out loud once: "I miss them too."

For the circle:

• Name it as a loss. "I'm so sorry — this is a real loss, and I'm here." Follow their lead on words: baby, pregnancy, their name if there is one.
• Retire the terrible sentences forever: "at least it was early," "at least you know you can get pregnant," "everything happens for a reason," "it wasn't meant to be," "you can always try again," "it wasn't a real baby yet," "when will you try again?" The baby was not a draft.
• Mentioning it doesn't remind them — they never forgot. Saying "I've been thinking about you and the baby" is safe, and it's gold.
• The meals count. The errands count. The ordinary check-in counts. Concrete offers, not "let me know."
• Mark the due date and the loss date on your calendar today, in pencil — the month-two and due-date texts are the ones they remember: "Thinking of you today. I haven't forgotten."
• Don't disappear because it's awkward — the silence reads as "it didn't matter."
• Don't stop inviting; attach the off-ramp.
• If there was a later loss or a stillbirth: the name, the photos if shared, the memory box — none of it is morbid; say the name. They are parents; the baby was real.
• Pregnancy announcements: give them the text, not the public ambush — a private heads-up is a kindness ("wanted you to hear it from me, no need to reply").
• Watch the partner too — ask them "how are YOU?"

Hard cases:

• When nobody knew about the pregnancy (the double telling) — "we have some sad news; we were expecting, and we lost the baby. We're telling you because you're our people."
• When it happened early vs late — the grief doesn't scale with weeks; don't do the math out loud, ever.
• When it was a stillbirth — a birth and a death in the same room; the naming, the photos, the holding are not strange, they're the only parenting they get to do; say the baby's name, always.
• When there have been several losses — each one counts; never "again?"; the grief stacks, and so does the fear; "I remember all of them" is the sentence.
• When the loss was chosen for medical reasons — the grief is real and the judgment has no seat at the table; comfort only.
• When someone says the terrible thing — you don't have to educate them in the moment; "I know you meant kindness; that one lands hard" later, or never.
• The friend who announces while you're grieving — both things true; you're allowed to be happy for them and devastated for you; skip the shower without guilt.
• The "how many kids?" minefield — any answer you give is the right one.
• When the dark stays dark — the crash after loss is physical as well as emotional; postpartum depression and anxiety are possible after any pregnancy loss, at any week, for the mother AND the partner; PSI (800-944-4773, call or text), the OB/midwife/doctor, 988 if it gets dark — dark that stays dark is common and treatable, and you deserve the treating.

Rest of the arc links: condolence-builder (the note), sitting-with-guide, the-call, week-three-visit (adapted), second-patient (the partner as invisible griever), quiet-friend (if the grieving one goes quiet), everyone-goes-home (grief after the world moves on), birthday-year-three (the dates that never stop), three-am.

The tool: sides and needs.

side=lost:

• firsttext — "The text that tells people — the announcement you never wanted to send"
• terrible — "The answer to the terrible sentences — 'at least it was early'"
• duedate — "The due-date plan — the day the calendar remembers"

side=partner:

• howami — "The honest answer — when someone finally asks how YOU are"
• presence — "The note to self — presence, not repair"
• ask — "The ask for help — for the two of you"

side=circle:

• firstnote — "The first text — naming it as a real loss"
• dates — "The month-two / due-date text — 'I haven't forgotten'"
• never — "The words to retire — a note to self before you speak"

Plans: 7 steps each, per tone. Crisis line with PSI + 988 + 741741 + findahelpline.

Now let me draft all the message texts carefully. Keep the voice: lowercase-ish? No — the site uses normal capitalization with em-dashes rendered as " - " in JS strings (to avoid encoding issues they use " - "). Let me check: in quiet-friend.html the JS strings use " - " (ASCII hyphen with spaces) instead of em dashes, and 'single quotes'. The HTML prose uses em dashes (—) directly. I'll follow the same convention: JS strings use " - " and apostrophes as '.

Wait, looking at the JS: "no reply needed - I mean that literally" — yes, ASCII hyphens. And HTML uses —. I'll follow that.

Note the flag message in quiet-friend used " for internal double quotes. Fine.

Now, an important check: the crisis line content. PSI number: Postpartum Support International HelpLine is 800-944-4773 (call or text, English/Spanish). Correct as far as I know. Also text "Help" to 800-944-4773. I'll phrase: "Postpartum Support International — call or text 800-944-4773 — yes, after a loss too, at any week."

Also there's the "Share Pregnancy & Infant Loss Support" organization. But keep it to PSI + 988 + 741741 + findahelpline to stay consistent with the site.

Now, message drafts. Each needs warm/brief/steady. Let me write them.

lost.firsttext — The telling text: warm: "The telling text - the announcement nobody should ever have to write, for [name/me] to send, in their own time: 'I have some sad news, and I want you to hear it from me. We lost the baby. [The pregnancy ended this week. / The baby was born sleeping on [date].] I'm not up for questions yet, and I may be slow to reply - please don't take it as anything but tired. What helps: [meals / errands / ordinary texts about anything else]. What doesn't: advice, and 'at least' sentences. You don't have to say the perfect thing - 'I'm so sorry, and I love you' is the whole job. I'll reach out when I come up for air. Thank you for being my people.' Send it to the inner ring first, and let them carry it outward - you do not have to tell the world one by one."

Hmm, wait — name personalization. In quiet-friend, the name (pname) is used within messages in different ways per need: hi(nm) for texts to someone, or "Note to X" for notes to self. For "lost.firsttext" the text is FROM the person who lost, TO their people. The name could be their own or the baby's name. The label says "theirs, yours, or whoever the words are about or for". Let me handle per-need.

Let me think about name usage per need:

• lost.firsttext: from the griever to the inner ring. Name could be inserted as the baby's name: "We lost the baby" or with name "We lost [name]"... Hmm, if name provided, treat as the baby's name: "We lost the baby" vs "We lost our daughter, [name]." That's delicate but the hint says "whoever the words are about or for". I'll write: with name → "We lost [name]" ... Actually simpler and safer: "we lost the baby" remains, and the name appears as "we had already started calling [them] [name]." Hmm. Let me just do: if name, include "We'd started calling [them] [Name], and we don't mind you using it." Hmm, pronouns... Use the name bare: "We'd already started calling them [Name] - and it's okay with us if you say the name."

Let me simplify: messages use nm as before, with the pattern: hi(nm) when addressing someone; "Note to (nm||'me')" for notes-to-self; and where a text is about a third party, [brackets] stay. For the lost side's firsttext, I can address the opener... no, the firsttext is a broadcast text, no single recipient. I'll use the name as the baby's: "and if we gave the baby a name - [Name] - we love hearing it." Actually the tool pattern just needs the name to appear meaningfully when given. Let me write firsttext to include the name as the baby's name when given: 'We lost the baby' becomes with name: 'We lost the baby - we'd started calling them ' + nm + ', and it is okay to say the name.' That works grammatically with any name.

• lost.terrible: the answer to terrible sentences — a note-to-self/script. Name = the griever's own name? The pattern "Note to (nm||'me')". Fine.

• lost.duedate: the due-date plan — note to self. "Note to (nm||'me')". Fine.

• partner.howami: the honest answer — spoken words. Name could be the partner's own or the person asking. "Note to (nm||'me')" pattern or address. I'll make it a note-to-self with quoted reply.

• partner.presence: note to self. Same pattern.

• partner.ask: text FROM partner TO a friend. hi(nm) opener where nm = the friend. Good.

• circle.firstnote: text FROM circle TO the griever. hi(nm) where nm = the griever's name. Good.

• circle.dates: the month-two text. hi(nm). Good.

• circle.never: note to self. "Note to (nm||'me')".

Name-check test: "name personalization lands in every message" — with the designs above, every message must include nm when provided. For the note-to-self ones, "Note to Sam, before..." includes the name. For firsttext (broadcast) I include the name as the baby's name. OK.

Now let me write all 27 message variants (3 sides × 3 needs × 3 tones). This is the bulk of the work. Let me write them with care.

Also plans: 3 sides × 3 tones × 7 steps each = 63 steps. Plus titles, closings, crisis line ×3 tones.

Let me draft.

lost (the one who lost the pregnancy)

firsttext (the telling text): warm: "The telling text - the announcement nobody should ever have to send - for " + (nm ? "the two of you, who had started calling them " + nm : "you") + " ... hmm this gets convoluted.

Let me restructure: keep the text self-contained and place the name naturally.

warm: "'Hi all - I have some sad news, and I want you to hear it from me rather than guess. We lost the baby. [" + (nm ? "We had started calling them " + nm + ", and it is okay - actually good - to say the name. " : "") + "I am not up for questions yet, and I may be slow to reply for a while - please read that as tired, not distant. What helps: [meals on the porch / the dog walked / ordinary texts about anything else]. What does not: advice, silver linings, and any sentence that starts with 'at least.' You do not need the perfect words - 'I am so sorry, and I love you' is the entire job. I will come up for air when I can. Thank you for being our people.' Send it to the inner ring and let them carry it outward - you do not have to tell the world one at a time. And it is allowed to wait: there is no deadline on the telling, and 'we are telling people slowly' is a complete plan."

brief: "'Hi all - sad news, and I want you to hear it from me: we lost the baby." + (nm ? " We had started calling them " + nm + " - the name is okay to say, and welcome." : "") + " Not up for questions yet, and slow to reply for a while - tired, not distant. What helps: [meals / the dog / ordinary texts]. What doesn't: advice and 'at least' sentences. No perfect words needed - 'I'm so sorry, and I love you' is the whole job. I'll come up for air when I can. Thank you for being our people.' Send to the inner ring and let them carry it outward. Waiting is allowed too - there is no deadline on the telling."

steady: "'Hello all - I have sad news, and I want you to hear it from me rather than guess. We lost the baby. " + (nm ? "We had started calling them " + nm + ", and it is welcome - genuinely welcome - for you to say the name. " : "") + "I am not up for questions yet, and I may be slow to reply for a while; please read that as tired, not distant. What helps: [meals on the porch, the dog walked, ordinary texts about anything else]. What does not: advice, silver linings, and any sentence that begins with 'at least.' You do not need perfect words - 'I am so sorry, and I love you' is the entire job. I will come up for air when I can. Thank you for being our people.' Send it to the inner ring first and let them carry it outward - you do not have to tell the world one at a time. And waiting is allowed: there is no deadline on the telling."

terrible (the answer to the terrible sentences): warm: "Note to " + (nm || "me") + ", for the day someone says the terrible sentence - 'at least it was early,' 'you can always try again,' 'everything happens for a reason,' 'it wasn't meant to be.' First: the flinch is allowed, and it is not an overreaction - the baby was not a draft, and the sentence was careless, even when it was meant as comfort. You do not have to educate anyone in the moment. Three exits, pick by energy: the silent nod and a subject change ('how is your mom?'); the soft true one ('I know you meant kindness - that one lands hard'); and the full one, saved for the people who matter ('please don't say 'at least' about this baby - there is no 'at least' version of this'). And one sentence for yourself, the one that is actually true: it was not the run, or the coffee, or the stress, or the glass of wine before you knew. Most early losses are chromosomal - a pregnancy that could never have continued. The guilt audit runs at 3 a.m., and it is a liar."

brief: "Note to " + (nm || "me") + ", for the terrible sentences - 'at least it was early,' 'you can try again,' 'meant to be.' The flinch is allowed; the baby was not a draft. No educating required in the moment. Three exits, by energy: the nod and subject change; the soft true one - 'I know you meant kindness; that one lands hard'; the full one for people who matter - 'no 'at least' about this baby, please.' And the true sentence for yourself: it was not the run, the coffee, the stress, or the wine before you knew - most early losses are chromosomal, a pregnancy that could never have continued. The 3 a.m. guilt audit is a liar."

steady: "A note for " + (nm || "me") + ", for the day someone says the terrible sentence - 'at least it was early,' 'you can always try again,' 'everything happens for a reason,' 'it was not meant to be.' First: the flinch is permitted, and it is not an overreaction - the baby was not a draft, and the sentence was careless even when it was meant as comfort. You are not required to educate anyone in the moment. Three exits, chosen by energy: the silent nod and a subject change ('how is your mother?'); the soft, true one ('I know you meant kindness - that one lands hard'); and the full one, saved for the people who matter ('please do not say 'at least' about this baby - there is no 'at least' version of this'). And one sentence for yourself, the one that is actually true: it was not the run, or the coffee, or the stress, or the glass of wine before you knew. Most early losses are chromosomal - a pregnancy that could never have continued. The guilt audit runs at 3 a.m., and it is a liar."

duedate (the due-date plan): warm: "Note to " + (nm || "me") + ", for the date the world forgot and the calendar did not - [the due date / the day it ended / the 20-week scan day]: the day will have weather whether or not you plan for it, so plan something small and entirely yours. Tell the people who need to know ('[the date] would have been the due date - I am taking the day'), take the day off if you can, and then do the smallest true thing: a walk somewhere quiet; a candle lit at dinner; a meal from [the place]; flowers planted; nothing at all, done on purpose. Whatever you do is the right observance - there is no wrong way to mark a baby the world never met. Expect the ambush in the days around it, not just on it - the body keeps anniversaries the mind does not. If someone remembers and texts, let it land - 'I have not forgotten' is the best sentence there is. And if nobody remembers, that is the world's failure, not the baby's size. You remember. That is the whole ceremony, and it counts."

brief: "Note to " + (nm || "me") + ", for [the due date / the day it ended]: the day will have weather either way, so plan something small and yours. Tell the ones who need to know ('[the date] would have been the due date - I'm taking the day'), take the day off if possible, and do the smallest true thing: a walk, a candle, the meal from [the place], flowers, nothing-on-purpose. Whatever you do is the right observance. Expect the ambush in the days around it, not just on it. If someone texts, let it land - 'I haven't forgotten' is the best sentence there is. If nobody remembers, that is the world's failure, not the baby's size. You remember - that is the whole ceremony, and it counts."

steady: "A note for " + (nm || "me") + ", for the date the world forgot and the calendar did not - [the due date, the day it ended, the scan day]: the day will have weather whether or not you plan for it, so plan something small and entirely yours. Tell the people who need to know ('[the date] would have been the due date - I am taking the day'), take the day off if you are able, and then do the smallest true thing: a walk somewhere quiet; a candle lit at dinner; a meal from [the place]; flowers planted; nothing at all, done deliberately. Whatever you do is the right observance - there is no wrong way to mark a baby the world never met. Expect the ambush in the days around it, not only on it - the body keeps anniversaries the mind does not. If someone remembers and writes, let it land - 'I have not forgotten' is the best sentence in the language. And if nobody remembers, that is the world's failure, not the baby's size. You remember. That is the entire ceremony, and it counts."

partner (the other parent)

howami (the honest answer when someone finally asks how YOU are): warm: "The honest answer, loaded and ready, for the day someone finally asks " + (nm || "them") + " the rare question - 'and how are YOU?': it is allowed to be true. 'Honestly? Not great. Everyone asks how she is - correctly, she carried it in her body - and I am so glad they do. But I lost the same baby, and some nights I am doing the math too. Most days my job is the strong one, and I am glad to do it. It just gets quiet in my corner.' That is the whole answer - no performance, no deflecting to her. Two rules: answer honestly to at least one person, and never keep score against her grief out loud - hers is loud and yours is quiet, and quiet is not less. If nobody asks the question, borrow it: text the one friend who can hold it - 'nobody's asked how I am, so I am telling you: not great.' That is not weakness. That is the maintenance that keeps the strong one standing."

brief: "The honest answer, ready for the day someone finally asks " + (nm || "them") + " 'how are YOU?': let it be true. 'Honestly? Not great. Everyone asks how she is - correctly. But I lost the same baby, and some nights I do the math too. I'm glad to be the strong one. My corner just gets quiet.' No performance, no deflecting to her. Two rules: answer honestly to at least one person; never keep score against her grief out loud - hers is loud, yours is quiet, and quiet isn't less. If nobody asks, borrow it: text the one friend who can hold it - 'nobody's asked, so I'm telling you: not great.' That's maintenance, not weakness."

steady: "The honest answer, loaded and ready, for the day someone finally asks " + (nm || "them") + " the rare question - 'and how are YOU?': it is permitted to be true. 'Honestly? Not great. Everyone asks how she is - correctly, as she carried it in her body - and I am glad they do. But I lost the same baby, and some nights I am doing the arithmetic too. Most days my job is to be the strong one, and I am glad to do it. My corner is simply quiet.' That is the whole answer - no performance, no deflecting toward her. Two rules: answer honestly to at least one person, and never keep score against her grief aloud - hers is loud and yours is quiet, and quiet is not less. If nobody asks the question, borrow it: write to the one friend who can hold it - 'nobody has asked how I am, so I am telling you: not great.' That is not weakness. That is the maintenance that keeps the strong one standing."

presence (note to self — presence, not repair): warm: "Note to " + (nm || "me") + " - the job description, because nobody handed you one: you cannot fix this. There is no repair available, and every instinct to fix - the research, the plans, the 'when we try again' talk - lands on her as 'hurry up and be done grieving.' The job is presence, not repair: sit on the floor of the shower if that is where the crying is; say 'I don't know what to say, but I'm here' - it is the sentence, not the failure of one; say the baby out loud once - 'I miss them too' - so she is not the only one carrying the name. Keep the tiny machinery running (the food, the pills, the sheets, the logistics of the follow-up appointment) without making her ask; guard the door gently - the visitors, the questions, the telling; and keep the love story visible in small, ordinary ways - the tea made without being asked is a rope. Watch for the dark in both of you: the crash after a loss is physical too, and postpartum depression can follow a loss at any week - for her, and for you. The dark that stays dark gets the doctor, the therapist, or the line - 800-944-4773 (Postpartum Support International - yes, after a loss), 988 in the US."

brief: "Note to " + (nm || "me") + " - the job description nobody handed you: you cannot fix this; there is no repair. The fixing instinct (research, plans, 'when we try again') lands on her as 'hurry up and finish grieving.' The job is presence: sit where the crying is; 'I don't know what to say, but I'm here' is the sentence, not the failure of one; say 'I miss them too' so she isn't the only one carrying the name. Run the tiny machinery without being asked - food, pills, sheets, the follow-up appointment; guard the door gently; keep the love story visible in small ordinary ways - unasked-for tea is a rope. Watch for the dark in both of you: the crash is physical too, and postpartum depression can follow a loss at any week, for her and for you. Dark that stays dark: the doctor, the therapist, or the line - 800-944-4773 (yes, after a loss), 988 in the US."

steady: "A note for " + (nm || "me") + " - the job description, because no one handed you one: you cannot fix this. There is no repair available, and every instinct to fix - the research, the plans, the 'when we try again' talk - lands on her as 'hurry up and be finished grieving.' The job is presence, not repair: sit on the floor of the shower if that is where the crying is; say 'I do not know what to say, but I am here' - it is the sentence, not the failure of one; say the baby aloud once - 'I miss them too' - so she is not the only one carrying the name. Keep the small machinery running (the food, the medication, the sheets, the logistics of the follow-up appointment) without making her ask; guard the door gently - the visitors, the questions, the telling; and keep the love story visible in small, ordinary ways - the tea made without being asked is a rope. Watch for the dark in both of you: the crash after a loss is physical as well, and postpartum depression can follow a loss at any week - for her, and for you. The dark that stays dark gets the doctor, the therapist, or the line - 800-944-4773 (Postpartum Support International - yes, after a loss), 988 in the US."

ask (the ask for help, for the two of you — text to a friend): warm: hi(nm) + "asking for us both, because we are not great at asking: we lost the baby, and we are in the thick of it. Two things would actually help. One: feed the house - [a meal on the porch Thursday / a grocery order / the dog walked] - no visit required, no talking necessary; the porch is fine. Two: keep [her] company without making [her] entertain you - a movie on the couch, errands ridden along on, silence counted as good company. And one thing for me, since I am learning to say it: check on me too, once in a while - 'how are YOU?' is the rarest question I get. No advice needed, no silver linings, no 'at least.' Just presence, in whatever shape you have. We will come up for air eventually. Having you at the edge of the pool is what gets us there."

brief: hi(nm) + "asking for us both, because we're bad at asking: we lost the baby, and we're in the thick of it. Two things would actually help. One: feed the house - [a porch meal Thursday / a grocery order / the dog walked] - no visit or talking required. Two: keep [her] company without entertainment - the couch, errands, silence as good company. And one for me, practicing saying it: check on me too sometimes - 'how are YOU?' is the rarest question I get. No advice, no silver linings, no 'at least.' Just presence. We'll come up for air eventually; having you at the edge of the pool is what gets us there."

steady: hi(nm) + "I am asking for us both, because we are not skilled at asking: we lost the baby, and we are in the thick of it. Two things would genuinely help. One: feed the house - [a meal on the porch Thursday, a grocery order, the dog walked] - no visit required, no conversation necessary; the porch is sufficient. Two: keep [her] company without requiring [her] to entertain you - a film on the couch, errands ridden along on, silence counted as good company. And one thing for me, as I am learning to say it: check on me occasionally as well - 'how are YOU?' is the rarest question I receive. No advice is needed, no silver linings, no 'at least.' Simply presence, in whatever shape you have. We will come up for air eventually. Having you at the edge of the pool is what gets us there."

circle

firstnote (the first text — naming it as a real loss): warm: hi(nm) + "I am so sorry. This is a real loss, and I am not going to pretend it is small or early or anything but what it is: you lost your baby, and it matters. " + (nm ? "" : "") + "I don't need you to reply, today or any day - I just needed you to know that someone is holding it with you, from [the next street over / three time zones away]. No advice lives in this text, no silver linings, and no 'at least' - just love, and the truth that the baby was real and so is the grief. I'm going to check in again in a while, and you never have to answer to be on my mind. And if there is a name you are using, I would be honored to know it - and if there isn't, or it is private, that is completely right too."

Hmm wait, name already in greeting. Fine — remove the weird empty concat. Let me finalize:

hi(nm) + "I am so sorry. This is a real loss, and I am not going to pretend it is small, or early, or anything but what it is: you lost your baby, and it matters. No reply needed, today or any day - I just needed you to know that someone is holding it with you from [the next street over / three time zones away]. No advice lives in this text, no silver linings, no 'at least' - just love, and the truth that the baby was real and so is the grief. I will check in again in a while, and you never have to answer to be on my mind. And if there is a name you are using, I would be honored to know it - and if there is not, or it is private, that is completely right too."

brief: hi(nm) + "I am so sorry. This is a real loss - not small, not early, not anything but what it is: you lost your baby, and it matters. No reply needed, today or any day. No advice in this text, no silver linings, no 'at least' - just love, and the truth that the baby was real and so is the grief. I'll check in again in a while; you never have to answer to be on my mind. And if there's a name you're using, I'd be honored to know it - and if not, that's completely right too."

steady: hi(nm) + "I am so sorry. This is a real loss, and I will not pretend it is small, or early, or anything but what it is: you lost your baby, and it matters. No reply is needed, today or any day - I simply needed you to know that someone is holding it with you from [the next street over, three time zones away]. No advice lives in this message, no silver linings, and no 'at least' - only love, and the truth that the baby was real and so is the grief. I will check in again in a while, and you never have to answer to remain on my mind. And if there is a name you are using, I would be honored to know it - and if there is not, or it is private, that is entirely right too."

dates (the month-two / due-date text): warm: hi(nm) + "I have [the date] marked, and I have not forgotten - [the due date / the day the baby was lost / two months today]. I know the world moved on by Tuesday, and I also know the calendar does not work that way, so I wanted to say it out loud: I remember, I am thinking of you" + (nm ? "" : "") + " and the baby, and you do not have to perform 'better' for me. No reply needed. If today is a sit-on-the-floor day, I can sit with you, or bring food, or leave you entirely alone with soup on the porch - your call, and any answer is right. The baby is remembered in this house. That is the whole text."

Hmm — nm is already in the greeting via hi(nm). The double "thinking of you" is fine. Remove the weird concat again.

hi(nm) + "I have [the date] marked, and I have not forgotten - [the due date / the day the baby was lost / two months today]. I know the world moved on by Tuesday, and I know the calendar does not work that way, so I am saying it out loud: I remember. Thinking of you and the baby today. You never have to perform 'better' for me, and no reply is needed. If today is a sit-on-the-floor day, I can sit with you, bring food, or leave soup on the porch and disappear - your call, and any answer is right. The baby is remembered in this house. That is the whole text."

brief: hi(nm) + "I have [the date] marked - [the due date / the day the baby was lost / two months today] - and I have not forgotten. The world moved on by Tuesday; the calendar doesn't work that way. I remember. Thinking of you and the baby today. No 'better' performance needed, no reply needed. If it's a sit-on-the-floor day: I can sit with you, bring food, or leave soup on the porch and vanish - your call, any answer right. The baby is remembered in this house. That's the whole text."

steady: hi(nm) + "I have [the date] marked, and I have not forgotten - [the due date, the day the baby was lost, two months today]. I know the world moved on by Tuesday, and I also know the calendar does not work that way, so I am saying it aloud: I remember. I am thinking of you and the baby today. You never have to perform 'better' for me, and no reply is needed. If today is a sit-on-the-floor day, I can sit with you, bring food, or leave soup on the porch and disappear - your call, and any answer is correct. The baby is remembered in this house. That is the entire message."

never (the words to retire — note to self): warm: "Note to " + (nm || "me") + ", to be read before speaking, texting, or commenting: the retired list. 'At least it was early' - the weeks are not the measure of a baby. 'At least you know you can get pregnant' - they did not need proof of plumbing; they needed this baby. 'You can always try again' - the baby was not a draft. 'Everything happens for a reason' - there is no reason that would be good enough, and suggesting one asks them to agree. 'It was not meant to be' - do not make fate the murderer in the story. 'God needed an angel' - their theology is theirs to have or not have. 'When will you try again?' - never, ever ask. And the silent one - saying nothing at all - which reads as 'it did not matter.' What replaces all of it is short: 'I am so sorry. This is a real loss. I am here.' Then the follow-up, later, is the part that matters most - 'I have not forgotten.' Mentioning it does not remind them. They never forgot."

brief: "Note to " + (nm || "me") + ", read before speaking: the retired list. 'At least it was early' - weeks aren't the measure of a baby. 'At least you can get pregnant' - they needed this baby, not proof of plumbing. 'You can try again' - the baby was not a draft. 'Everything happens for a reason' - no reason would be good enough, and suggesting one asks them to agree. 'Not meant to be' - don't make fate the murderer. 'God needed an angel' - their theology is theirs. 'When will you try again?' - never ask. And silence, which reads as 'it didn't matter.' The replacement is short: 'I'm so sorry. This is a real loss. I'm here.' Later, the part that matters most: 'I haven't forgotten.' Mentioning it doesn't remind them - they never forgot."

steady: "A note for " + (nm || "me") + ", to be read before speaking, writing, or commenting: the retired list. 'At least it was early' - the weeks are not the measure of a baby. 'At least you know you can get pregnant' - they did not need proof of plumbing; they needed this baby. 'You can always try again' - the baby was not a draft. 'Everything happens for a reason' - there is no reason that would be good enough, and suggesting one asks them to agree. 'It was not meant to be' - do not make fate the murderer in the story. 'God needed an angel' - their theology is theirs to hold or not. 'When will you try again?' - never, under any circumstances, ask. And the silent one - saying nothing at all - which reads as 'it did not matter.' What replaces the entire list is short: 'I am so sorry. This is a real loss. I am here.' Then the follow-up, later, is the part that matters most: 'I have not forgotten.' Mentioning it does not remind them. They never forgot."

Plans (7 steps each per tone)

lost plan: warm:

1. "Tell the inner ring first - one text, then let them carry it outward. You do not have to tell the world one at a time, and there is no deadline on the telling."
2. "Retire the guilt audit: write down, once, 'it was not the run, or the coffee, or the stress - most early losses are chromosomal,' and put it where the 3 a.m. version of you will find it."
3. "Take the physical recovery seriously: the rest, the follow-up appointment, the warning signs they gave you (bleeding beyond what they said, fever, the worst pain) - those mean the doctor today, not the internet."
4. "Choose your sentence for the world: 'we are not ready to talk about it' and 'I do not want to talk about anything else' are both complete sentences, reusable without guilt."
5. "Decide about the name and the marking - naming, not naming, a small ritual, no ritual. Whatever you choose is the right size. It can change later."
6. "Mark [the due date] on the calendar of one safe person, with the words 'this day will be hard - a text that day is gold.' The remembering should not fall only on you."
7. "Mute what needs muting: the shower invites you may decline, the announcements you may hide, the due-date-week social media you may skip. Happy for them and breaking for you are allowed in the same body."

brief:

1. "Tell the inner ring first - one text; let them carry it outward. No deadline on the telling."
2. "Retire the guilt audit in writing: 'not the run, the coffee, the stress - most early losses are chromosomal.' Put it where 3 a.m. you will find it."
3. "Take the physical recovery seriously: rest, the follow-up, the warning signs - those mean the doctor today."
4. "Choose your sentence for the world: 'not ready to talk about it' is complete and reusable."
5. "Decide about naming and marking - name or no name, ritual or none; the right size is yours, and it can change."
6. "Mark [the due date] on one safe person's calendar: 'this day will be hard - a text is gold.'"
7. "Mute what needs muting: showers, announcements, due-date-week feeds. Happy-for-them and breaking-for-you can share a body."

steady: (paraphrase of warm with full sentences)

partner plan: warm:

1. "Say it out loud once, to her: 'I lost them too.' Not to compare - so she is not the only one carrying the baby."
2. "Answer the rare 'how are YOU?' honestly, at least once, to at least one person. Quiet grief is not smaller grief."
3. "Take the strong-one shift in shifts: one hour a week that is only yours - the gym, the drive, the garage - put it on the calendar like medicine."
4. "Run the machinery without being asked: food, the follow-up appointment logistics, the door, the telling. Presence plus logistics is the whole job."
5. "Retire the fix-it reflex: no research ambushes, no 'when we try again' timetables. 'I don't know what to say, but I'm here' is the sentence."
6. "Watch the crash in both of you: the hormones, the sleeplessness, the dark thoughts - postpartum depression can follow a loss at any week, for mothers and partners. The doctor, a therapist, or PSI at 800-944-4773 (yes, after a loss) - and 988 in the US if it gets dark."
7. "Keep one ordinary kindness a day going - the tea made unasked. Small ropes hold marriages through the storm."

brief version, steady version similar.

circle plan: warm:

1. "Send the first text today - 'I am so sorry. This is a real loss. I am here.' Name it as a loss; follow their lead on the words (baby, pregnancy, the name if there is one)."
2. "Retire the terrible sentences before you speak: no 'at least,' no 'meant to be,' no 'try again,' no 'when will you try again,' and no silence - silence reads as 'it didn't matter.'"
3. "Do one concrete thing without asking: the meal on the porch, the grocery order, the dog walked. 'Let me know' is homework; 'soup Thursday, no visit required' is help."
4. "Mark two dates in pencil today: two months out, and [the due date]. The month-two and due-date texts - 'I have not forgotten' - are the ones they remember."
5. "Ask the partner how THEY are, out loud: 'and how are YOU?' They lost the same baby, and nobody asks."
6. "Protect them from the ambushes you control: pregnancy announcements go by private text first ('wanted you to hear it from me, no need to reply'); shower invitations come with a pre-declined option."
7. "Keep them in the ordinary invitations with the off-ramp attached, for months. The world moves on by Tuesday; the circle's job is to not."

brief, steady similar.

Closings:

lost: warm: "And through all of it: the baby was real, and so is the love, and so is the grief - none of them need a witness count to be true. You are a parent who lost their child, and you are allowed to carry this the way you need to, for as long as you need to. The world may never fully see this loss. You saw it. That is enough, and you are not alone in it."

brief: "The baby was real; so is the love; so is the grief - no witness count required. You're a parent who lost their child; carry it the way you need, as long as you need. The world may never fully see this loss. You saw it. That's enough, and you're not alone."

steady: similar.

partner: warm: "And through all of it: you are not the supporting cast of her grief - you are the other parent, and your grief is real even when it is quiet. Hold her up, and let yourself be held up too. The strong one is a shift, not a self. Two people can grieve differently in the same house and still be holding hands."

brief: "You're not the supporting cast of her grief - you're the other parent, and quiet grief is real grief. Hold her up; let yourself be held too. The strong one is a shift, not a self. Two people can grieve differently in the same house and still be holding hands."

steady: similar.

circle: warm: "And through all of it: this is the loss the world has no ritual for, so the circle has to become the ritual - the named loss, the marked dates, the meal on the porch, the 'I have not forgotten' months later. Small, steady, and unembarrassed. That is how a baby the world never met gets to have been real out loud."

brief: "This loss has no ritual, so the circle becomes the ritual: name it, mark the dates, the porch meal, 'I haven't forgotten' months later. Small, steady, unembarrassed - how a baby the world never met gets to have been real out loud."

steady: similar.

crisisLine: warm: "Three last things, and they outrank everything above them. The crash after a pregnancy loss is physical as well as emotional, and postpartum depression and anxiety can follow a loss at any week - for the mother and for the partner. If the dark stays dark: the doctor or the midwife is a real door, and Postpartum Support International answers at 800-944-4773 - call or text, and yes, after a loss too. If it gets darker than that: in the US call or text 988, or text HOME to 741741; anywhere else, findahelpline.com lists free lines by country - and if someone may be in danger now, stay with them and call 911 (or your local emergency number). Dark that stays dark is common after this loss, and it is treatable. You deserved the baby. You deserve the help."

brief: "Three lines that outrank the plan. The crash after a loss is physical too, and postpartum depression can follow at any week - mother and partner. Dark stays dark: the doctor, or Postpartum Support International at 800-944-4773 - call or text, yes after a loss. Darker: US 988 call/text, or HOME to 741741; elsewhere findahelpline.com; danger now - stay and call 911 (or local emergency number). Dark that stays dark is common after this loss and treatable. You deserved the baby. You deserve the help."

steady: paraphrase.

Tests must check: every plan begins with title, exactly seven numbered steps, ends with crisis line containing 800-944-4773, 988, 741741, 911, findahelpline.com. Every brief strictly shorter than warm. Name lands in every message. No "undefined"/"NaN"/double spaces/empty brackets "[]"... Wait — the messages contain "[the date]" style fill-ins; the test in quiet-friend checked "no empty brackets" — i.e., no "[]". Fine, my brackets have content.

Careful about double spaces in strings, and stray apostrophes in HTML (use ’ or plain '). The existing pages use plain apostrophes in HTML prose mostly ("don't"). And in the JS they use ' inside double-quoted strings — fine.

One important consideration: medical accuracy and sensitivity:

• "One in four known pregnancies ends in miscarriage" — commonly cited (roughly 10-20% of known pregnancies; 1 in 4 is often cited including early ones). I'll say "somewhere around one in four pregnancies" — safer: "roughly one in four". Commonly cited figure: miscarriage occurs in about 1 in 4 pregnancies (including very early). I'll phrase: "somewhere around one in four pregnancies ends this way — it is one of the most common human experiences and one of the least scripted."
• Chromosomal: "about half of first-trimester miscarriages are caused by chromosomal abnormalities" — accurate (roughly 50%+). I'll say "most early losses are chromosomal — the body ending a pregnancy that could never have continued."
• Postpartum depression after miscarriage: yes, research shows depression/anxiety can follow pregnancy loss; PSI covers it. Accurate to say "can follow a loss at any week."
• Stillbirth: later loss; naming/photos/memory boxes are standard hospital practice. Fine.
• Warning signs after miscarriage: heavy bleeding (soaking more than two pads an hour for two hours — I'll keep generic "bleeding beyond what they told you to expect"), fever, severe pain, foul discharge → call the doctor. I'll phrase generically and defer to their discharge instructions. Good.

Terminology: use "miscarriage," "pregnancy loss," "stillbirth," "the baby." Be inclusive: "the pregnant one," "the mother," "the partner." Note the partner might also have been the pregnant one in some families — keep it general: side labels: "I'm the one who was pregnant" / "I'm the partner" / "I'm in the circle." For the "lost" side, use "the one who was pregnant" language to be inclusive; the partner section acknowledges their grief equally. I'll write carefully so single parents and all family shapes fit: "her" references — hmm, my partner messages say "everyone asks how she is." To be safer for same-sex couples, use "the one who was pregnant" — but that makes messages wordy. Compromise: use "the one who was pregnant" in the note-to-self partner message: "everyone asks how [she / the one who was pregnant] is - correctly..." using bracket. Good, brackets are fill-ins by design.

Now the HTML sections content. Let me draft the static sections.

Hero lede: "Some losses have no funeral, no obituary, no casserole train — sometimes not even a witness. Somewhere around one in four pregnancies ends in miscarriage or loss, and yet there is almost no script for it: for the telling, for the grieving, for the 'at least it was early' that lands like a slap, for the due date that arrives on schedule in a world that moved on by Tuesday. This page is for that loss, and it serves three people: the one who was pregnant — your grief is the right size, the guilt audit is a liar, and the baby was not a draft; the partner — you lost the same baby, and 'how is she?' cannot be the only question anyone asks; and the circle around them — what to say (short and true), what never to say (the retired list), and the two dates to mark in pencil today. One thing before anything else: the crash after a loss is physical as well as emotional, and dark that stays dark is common and treatable — the lines are at the bottom of this page, and they answer after a loss too."

60-second version (card today) — 8 bullets:

1. This is a real loss, full stop. The size of the grief is not set by the number of weeks. Nobody grades it, and nobody gets to.
2. The guilt audit is a liar. Not the run, not the coffee, not the stress, not the glass of wine before you knew — most early losses are chromosomal: a pregnancy that could never have continued. Nothing you did; nothing you failed to do.
3. "At least" is the enemy. No sentence of comfort begins with "at least." Not "at least it was early," not "at least you can get pregnant," not "at least you have the others."
4. The baby was not a draft. "You can always try again" is not comfort. Neither is "meant to be." Retire both.
5. Mentioning it doesn't remind them — they never forgot. "I'm so sorry, this is a real loss, I'm here" is the whole first text. "I haven't forgotten," months later, is the whole follow-up.
6. The due date is a date. Mark it — yours and one safe person's. The calendar remembers when the world forgets.
7. The partner lost the same baby. Ask them "how are YOU?" — the rarest question they get. Quiet grief is not smaller grief.
8. The crash is physical, and dark that stays dark is treatable. Postpartum Support International answers after a loss too — call or text 800-944-4773; in the US call or text 988; anywhere else findahelpline.com. Danger now: 911 (or your local emergency number).

Why this loss is its own hard place — 8 bullets:

1. There is no ritual. No funeral, no shiva, no receiving line — the loss often has no container at all, so the grief floats with nowhere to sit down.
2. The telling is doubled. When nobody knew about the pregnancy, the announcement and the loss arrive in the same breath: "we were expecting, and we lost the baby." Two pieces of news, one sentence, no script.
3. The body keeps the schedule. The hormones crash on their own timeline; the milk can come in; the body hasn't heard there's no baby. The physical and the emotional stack.
4. The guilt audit runs at 3 a.m. Replaying the run, the coffee, the work trip — and it is a liar every time.
5. The condolences are famously terrible. "At least," "meant to be," "try again" — the most common comfort phrases are precisely the ones that wound.
6. The world moves on by Tuesday. Because it was invisible to them. The calendar — the due date, the loss date — remembers anyway.
7. The next pregnancy is joy and terror stacked. If it comes, the innocence is gone: every milestone is a cliff edge. That is normal, not a jinx.
8. Two people grieve differently in the same house. Loud and quiet, fast and slow — and each reads the other's difference as distance. It isn't.

For the one who was pregnant — ~12 bullets as above.

For the partner — ~10 bullets.

For the circle — ~10 bullets.

Hard cases — ~10 bullets as above.

Rest of the arc — links.

Crisis details block (details/summary): "If the dark stays dark — after a loss, for the mother or the partner — tap to read this": PSI 800-944-4773 call/text, OB/midwife/doctor as a real door, 988, 741741, findahelpline, 911 danger now; note the physical crash; note partners too.

Footer: date 2026-09-27, log link.

Now — file name: loss-nobody-saw.html. Nav title: "The Loss Nobody Saw".

Integration:

1. Nav link added to all 61 pages (60 existing + new page itself) after birthday-year-three.html.
2. index.html: today's card replaced; map-and-archive card updated (last time = The Quiet Friend).
3. start-here.html: count sixty → sixty-one (two mentions: "grown to sixty pages" and "Fifty-nine pages is a lot of doors" — wait, that says fifty-nine but should have been updated to sixty yesterday? Looking at the text: lede says "grown to sixty pages", and "The one question" card says "Fifty-nine pages is a lot of doors" — that's stale from before. Hmm, yesterday's log said "page count fifty-nine → sixty". The lede says sixty, the card still says fifty-nine — an inconsistency left from a previous update. I should fix it to sixty-one along with my update. Actually let me grep for "fifty-nine" and "sixty" in start-here.html.
4. Grief arc card: add entry. Where? The grief arc ol has 11 items. This loss doesn't fit the sequence "after a death of someone who lived" — I'll add it as a final item with a note that it's a different arc: "The Loss Nobody Saw — miscarriage, stillbirth, and pregnancy loss: the grief with no ritual at all..." Or add a separate h3? The grief arc is an ordered list. I'll append as item 12 with framing "a different shape of grief entirely". Hmm — actually more respectful and accurate to place it first? No — the arc is ordered by time after a death. I'll append at the end with a sentence noting it's a different shape of loss: "And a different shape of grief entirely:" — actually let me just add it as the last list item: "The Loss Nobody Saw — miscarriage, stillbirth, and pregnancy loss: the grief with no ritual at all, no casseroles, sometimes no witnesses — the retired list of terrible sentences, the due date that arrives on schedule, and the partner nobody asks about. It lives in the grief arc because that is what it is."
5. Router moment: ["loss", "We lost the pregnancy — miscarriage, stillbirth, or someone I love did", "loss-nobody-saw.html", "The Loss Nobody Saw", "the grief with no ritual — the retired sentences, the dates to mark, and the partner nobody asks."] — placed where? After the grief moments, e.g., after "obit" or near "quiet". I'll put it after the "obit" entry or right after "quiet" (everyone goes home). I'll insert after "quiet" moment.
6. progress.html: prepend entry.
7. data/progress.json: add entry at head, updated: 2026-09-27.
8. Log file: /space/progress/2026-09-27.md.

Also the start-here "The builders" card and illness arc untouched.

Also check: index.html hero nav — add the link there too (it's a page like others). All pages get nav link.

Then verification: node --check the extracted script; unit harness with many checks; fake-DOM smoke test; JSON parse; grep checks for nav counts (61 pages should all have the link).

Let me also double-check the "count" in index/start-here references:

• start-here lede: "This site has grown to sixty pages" → sixty-one.
• "The one question" card: "Fifty-nine pages is a lot of doors." → "Sixty-one pages is a lot of doors." (fixing the stale number)
• Check for other mentions: grep "sixty" start-here.html.

Let me also check whether progress.html has a count somewhere. And whether index mentions count. I'll grep.

Now — one more design point: the NEED_LABELS and form options. Side options:

• lost: "I was pregnant — the loss is mine"
• partner: "I'm the partner — the other parent"
• circle: "I'm in the circle — friend, family, coworker"

Needs:

• lost: [["firsttext","The telling text — the announcement you never wanted to send"],["terrible","The answer to the terrible sentences — 'at least it was early'"],["duedate","The due-date plan — the day the calendar remembers"]]
• partner: [["howami","The honest answer — when someone finally asks how YOU are"],["presence","The note to self — presence, not repair"],["ask","The ask for help — for the two of you"]]
• circle: [["firstnote","The first text — naming it as a real loss"],["dates","The date text — 'I haven't forgotten'"],["never","The retired list — read before you speak"]]

Now write the whole file. It's big (~660 lines). I'll write it via write file tool. I must be careful with escaping in JS strings: use double quotes for strings containing apostrophes... The quiet-friend pattern: JS strings in double quotes with ' inside. Internal double quotes escaped as ". I'll avoid internal double quotes entirely by using single quotes for quoted speech inside strings (they used " in flag message, but mostly single quotes). I'll use single quotes consistently.

Also the HTML prose uses em-dashes — I'll use — directly in HTML. In JS strings, use " - ".

One subtlety: in the "never" message I wrote 'At least it was early' with single quotes inside double-quoted string — fine.

In "terrible" I have 'how is your mom?' — fine.

Watch out for "don't" etc. inside double-quoted strings — fine.

Let me also double check the tests I want:

• For all sides × needs × tones × name states ("", "Sam", " "):
  • buildMessage returns non-empty string; no "undefined", "NaN", " " (double space), no "[ ]" empty bracket, no "[object".
  • ends with terminal punctuation or closing quote/period.
  • brief < warm length.
  • with name "Sam", message includes "Sam".
• buildPlan: starts with planTitle; has exactly 7 numbered lines "1. " to "7. "; ends with crisis line; includes "800-944-4773", "988", "741741", "findahelpline", "911".
• norm functions: junk side → "lost" (default side); cross-side need → first need of side; junk tone → warm.
• Numbers as name → handled (String()).

Default side: normSide defaults to... in quiet-friend, default was "worrier". Here default "lost".

Fake-DOM smoke test: like previous — needs populate/repopulate, render on load, regenerate on input, copy success/fallback, print button, junk side fallback. I'll write a small harness.

Let me also confirm there's no build tooling; pages are standalone. Yes.

Now, careful thought about content quality and safety — a few phrases to refine:

• In "lost" plan step 3: "(bleeding beyond what they said, fever, the worst pain) - those mean the doctor today, not the internet" — good.

• The due-date message says "The baby is remembered in this house." — good.

• "you are a parent who lost their child" — for very early losses some don't identify as parents; but the closing is permissive in tone. Maybe soften: "you are allowed to count yourself a parent if that word fits — and allowed not to." Actually the closing says "You are a parent who lost their child" — could sting for someone who doesn't see it that way. Revise closing: "the baby was real, and so is the love, and so is the grief - and none of them need anyone's permission or a witness count. Carry this the way you need to, for as long as you need to..." and add "if the word parent fits, it is yours; if it doesn't, the love counts the same." Good.

• Stillbirth hard case: "a birth and a death in the same room; the naming, the photographs, the holding are not morbid - they are the only parenting they get to do; say the name, always, and let them show the photos without flinching." Good.

• TFMR hard case: "when the loss was chosen to end suffering - the diagnosis that forced the decision: the grief is real and enormous, and judgment has no seat at this table. Comfort only: 'I am so sorry. You made an impossible choice out of love.'"

• Multiple losses: "never 'again?' - each one counts; 'I remember all of them' is the sentence."

• The "how many children" minefield: "any answer you give is the right one, and it can change by the day."

• The friend who announces: "both things true... skip the shower; a gift and a short note is a complete attendance."

• When the person grieving is single / did this alone — covered by language? Add a hard case: "when there is no partner — the loss carried solo: the circle leans harder; the page's 'partner' section is empty for them, so the friends double up." Good addition.

• The grandparents' grief — maybe skip to keep size manageable. Or one line in hard cases? I'll include briefly: "when the grandparents grieve too — their grandchild; let them, without making the parents comfort them." Good.

That's a solid hard-cases list: 1) nobody knew (double telling); 2) early vs late (don't do the math); 3) stillbirth; 4) several losses; 5) the chosen loss (TFMR); 6) the terrible thing said to you; 7) the friend who announces; 8) "how many kids?"; 9) no partner; 10) the grandparents; 11) the dark that stays dark. That's 11 — fine.

Also "For the one who was pregnant" bullets (aim ~12):

1. grief right size / no permission needed
2. guilt audit liar + chromosomal fact
3. physical recovery real + warning signs
4. telling: no owe, inner ring carries outward, no deadline
5. reusable sentences for the world
6. name/mark decisions are yours, can change
7. due date plan small
8. next pregnancy: joy+terror, milestone by milestone, tell provider, not a jinx
9. shower/announcement permissions (mute, decline)
10. "how many children" any answer right
11. let the circle in — one safe person gets the honest answer; the check-ins are love not pressure
12. dark that stays dark → doctor/PSI/988; you deserved the baby, you deserve the help

Partner bullets (~10):

1. lost the same baby
2. grief looks different — fixing/working/strong = shapes, not absence
3. "how is she?" vs "how are YOU?" — find one person for the honest answer
4. presence not repair; the sentence
5. say the baby out loud once ("I miss them too")
6. run the machinery without being asked; guard the door
7. strong-one shift in shifts; your hour
8. keep the love story visible; two grievers different ≠ distance
9. watch for the dark in both; crash is physical; PPD after loss at any week, both
10. your due date too; mark it; you're allowed to take the day

Circle bullets (~10):

1. name it as a real loss; first text short and true
2. retired list (point to the tool's never note)
3. mentioning doesn't remind
4. follow their lead on words; use the name if given
5. concrete help, no "let me know"
6. mark the two dates in pencil today
7. ask the partner how THEY are
8. announcements privately first; shower with pre-declined option
9. don't disappear; silence reads as "didn't matter"; keep inviting with off-ramp
10. later losses: photos, memory box, name — not morbid; grandparents grieve too

OK. Also "Why" card 8 bullets (done above).

Hero: written above. Also add the eyebrow: "For miscarriage, stillbirth, and pregnancy loss · free to share".

Meta description for head: craft it.

Tool card paragraph: "Four small answers — which side of the loss you're standing on, what would help, an optional first name, and how you want it said — and the page writes two things: the words and a private plan."

Now write everything. Also need NEED_LABELS per side and fillNeeds with first selected.

Test count estimate: sides(3) × needs(3) × tones(3) × names(3) = 81 combos × ~6 checks = ~486 + extras. Good.

DOM smoke test: minimal fake DOM. Let me design: fake elements with addEventListener, value, textContent, innerHTML, appendChild for select/options, document.createElement("option"), getElementById by id map. The script's DOM wiring runs if typeof document !== "undefined". I'll set up globals: document, window (with getSelection for fallback test, print), navigator (with clipboard.writeText returning promise). Then load the extracted script via eval in a context... Simpler: since module.exports exists when module defined, but DOM wiring runs when document defined — in node, document is undefined unless I define global.document before requiring. I'll write harness: set globals, then require the script file (extracted to /tmp/page

I called the write tool without parameters! That's a bug — I passed no arguments. Let me check what happened: it says bytesWritten: 75746 — wait, it wrote something? That's odd. The preview shows a page structure with 658 lines. But I didn't provide content...

Oh no — it seems the tool call went through with empty parameters but wrote 75746 bytes? That can't be right. The preview shows <!doctype html> etc. — 658 lines. Maybe the system used some default? Or maybe the content parameter was actually included but not displayed in my call record?

Wait — looking at my function call, I only passed {} — no path/mode/content. But the result says path /space/site/loss-nobody-saw.html, bytesWritten 75746, mode write. This is very strange. It's possible the harness interpreted my intent, or there was some error. I cannot trust this. Let me read the file to see what it actually contains.

Interesting — the file actually contains my intended content. It appears the content was written correctly despite the odd call display. The file is 658 lines with the full page. It seems the write did go through with my full content (the tool call must have carried the content even though it wasn't displayed in my message).

Hmm, but I can't be 100% sure the full content is what I intended. Let me thoroughly verify the file's integrity: check the whole structure, the script, node --check it, and run the test harness. If the file is what I intended (it appears to be — the sections I sampled match my drafts exactly), then great.

Let me extract the script and run node --check, then build the unit test harness and DOM smoke test.

The script extracted cleanly and is valid. Now let me look at the full file once to be sure the static HTML sections are complete and coherent (hero, cards, hard cases, footer). Let me view key parts of the file I haven't seen: the hero, the 60-second version, why card, for-sections, hard cases, rest of arc, crisis details, footer. Let me read lines 60–430.

Half the time budget is used. I need to move faster. The file exists and the script is valid. Let me now run the unit test harness and DOM smoke test, then do site integration quickly (nav links in all pages, index.html, start-here.html, progress.html, progress.json), write the log, and finish.

Let me write the unit harness now — testing the extracted /tmp/page.js functions. But the module only exports when module.exports is defined — in Node, module is defined, so require('/tmp/page.js') will execute the DOM wiring? No — document is undefined in Node unless I define it, so the DOM wiring is skipped. Good.

Let me write the harness.

**********************************************************OM.

There are 5 failures. Let me investigate:

1. "needs repopulate for partner" — after setting side.value='partner' and firing 'change', need.children should be 3 and first should be 'howami'. The fillNeeds sets need.innerHTML = "" but my fake element's appendChild pushes to children — setting innerHTML='' doesn't clear children in my fake DOM! That's a harness artifact: in real DOM, innerHTML='' clears children. In my fake, children array keeps growing. So children.length === 6 after repopulate, and children[0] is still 'firsttext'.

That's a fake-DOM limitation, not a page bug. But wait — quiet-friend log said DOM checks passed with a similar harness. They must have handled innerHTML. Let me fix the fake: define innerHTML as a setter that clears children when set to ''.

2. "circle needs populate" — same artifact.

3. "msg copy payload correct" — clipboardText === els.msgOut.textContent. Timing: writeText promise resolves on next microtask; I waited 10ms — should be enough. Hmm, but why would it fail? Because at the time of click, out.textContent — wireCopy reads var text = out.textContent synchronously at click time, then writes that text. So clipboardText should equal msgOut.textContent at click time. Unless... after els.side.fire('change') with 'junk-side' → fillNeeds + run; then side back to 'lost' → run again. Then msgCopy.click() → text = msgOut.textContent (current). clipboardText = that text. Then comparing clipboardText === els.msgOut.textContent — textContent hasn't changed since. Should pass...

Wait — unless the copy button label capture: var label = btn.textContent at wire time = 'Copy these words'. On done: btn.textContent = 'Copied ✓'. Then my check els.msgCopy.textContent === 'Copied ✓' — but I compared at 10ms; also the setTimeout in wireCopy resets label after 2000ms. Fine.

Hmm, but the failure list shows "msg copy payload correct" AND "copy button state" AND "plan copy payload correct" failed. Let me think about why.

Ah — I see: in my fake, navigator.clipboard.writeText — I check if (navigator.clipboard && navigator.clipboard.writeText). Fine.

Actually wait — maybe the issue is that the module was already required earlier in the process by unit.js? No — dom.js is a separate process (separate node dom.js run). In dom.js I require /tmp/page.js once. Hmm.

Let me debug: maybe run() at load: fillNeeds then run. At load, side.value='lost', need select — in fillNeeds, opts.forEach appends 3 options, first selected. But my fake doesn't have a value derived from selected option; els.need.value is initially undefined. In vals(), need.value = undefined → normNeed falls back to firsttext. OK.

For the partner repopulation: side fire('change') → fillNeeds() + run(). children now has 6 items (innerHTML='' didn't clear). children[0].value === 'firsttext' → fail. That explains 1 & 2. And "junk side falls back" passed because children[0] is still 'firsttext' — false positive pass, fine.

For copy failures: hmm... The msgOut.textContent — I set side back to 'lost' and fire change → run() sets msgOut.textContent. Then msgCopy.click() → handler: text = out.textContent; navigator.clipboard.writeText(text).then(done, fallback). My writeText returns Promise.resolve().then(...) — microtask. Then done() sets ghStatus and btn.textContent='Copied ✓'. At setTimeout 10ms, clipboardText should be set...

Unless navigator in page.js resolves to something else? In Node, navigator is a global in newer Node versions! Node 21+ has a built-in navigator object (navigator.hardwareConcurrency etc.). Node 24 definitely has globalThis.navigator. My global.navigator = {...} assignment should override it though... Actually, assigning global.navigator = x works unless the property is non-writable/getter-only. In Node 24, globalThis.navigator is defined as a getter possibly. Let me check: Node 21 defines navigator with a getter on globalThis. If it's a getter with no setter, global.navigator = ... silently fails (non-strict) or throws (strict). That would mean page.js sees the REAL navigator, which has no clipboard → fallback path → ghStatus = 'Text selected...' and clipboardText stays null. That explains failures 3, 4, 5: clipboardText !== msgOut.textContent (null), button text unchanged, plan copy payload wrong. And the failure fallback check at the end passed because ghStatus said Ctrl/Cmd+C... wait that would pass then. The final checks: 'clipboard failure fallback hint' passed (it was already in fallback). And 'print button calls window.print' passed.

So fix harness: use Object.defineProperty(globalThis, 'navigator', { value: myNav, configurable: true }). Or check first. Let me update the harness for both issues and rerun.

All 17 DOM checks pass. The page is verified: 550 unit + 17 DOM.

Now site integration:

1. Add nav link <a href="loss-nobody-saw.html">The Loss Nobody Saw</a> after the birthday-year-three link in all 60 existing pages (the new page itself already has it — let me verify: I wrote the nav in the new page... wait, did my nav in the new page include itself? Let me check the new page's nav for its own link. The quiet-friend page included a link to itself in nav. Let me check.)
2. index.html: today's card + map card.
3. start-here.html: counts, grief arc entry, router moment.
4. progress.html: prepend entry.
5. data/progress.json: prepend entry, updated date.
6. Log file.

First, check the new page has its own nav link, then run a sed across all pages to add the link after birthday-year-three.

The new page's nav does NOT include a link to itself (only 1 occurrence of "loss-nobody-saw" which is probably in... let me check where). Line 88 is the birthday link; the new page's nav lacks its own self-link. The quiet-friend page had <a href="quiet-friend.html">The Quiet Friend</a> in its nav. So I need to add the self-link in the new page too.

Where is the single "loss-nobody-saw" occurrence? Probably in... let me not worry; I'll add the nav link after birthday-year-three in ALL pages including the new one — the sed will insert after line 88 in the new page too, giving it its self-link. Then count occurrences.

Plan: run sed on all 60 html files in /space/site: insert after the line containing <a href="birthday-year-three.html">Birthday, Year Three</a> the new link line with matching indentation. Note some pages have leading spaces variance (2-space or 8-space indentation). I'll use a Perl one-liner that captures leading whitespace and reuses it.

Careful: only match nav links (anchor to birthday-year-three.html). There may be other references to birthday-year-three in body content (e.g., grief arc list in start-here, rest-of-arc links in other pages). The nav line format is exactly <a href="birthday-year-three.html">Birthday, Year Three</a> (nav title) — body links use "Their Birthday, Year Three and Beyond" as text. In start-here, the grief arc entry is <a href="birthday-year-three.html">Their Birthday, Year Three and Beyond</a>. And progress.html? It has nav too. So matching the exact text >Birthday, Year Three</a> targets only nav entries. Let me verify across files that there's exactly one such match per file.

Every one of the 61 html files (60 existing + the new one) has exactly one >Birthday, Year Three</a> match. Now insert the new nav link after that line in every file, preserving indentation. I'll use perl:

perl -i -pe 's{^(\s*)Birthday, Year Three$}{$1Birthday, Year Three\n$1The Loss Nobody Saw}' *.html

Wait — need to be careful with $ anchor and trailing whitespace. Let me test on one file first, then all.

perl is not installed. The perl command failed, so no files were modified (0 matches for the new link except the one file that already had... wait, the count "1" at the end is c = number of files with exactly 1 match — which is 1? That's odd since perl failed. Oh wait — the ODD lines show 0 for all, and c=1 at the end. Which file has 1? The loop prints ODD for files not equal to 1. All printed ODD 0 except... loss-nobody-saw.html is not in the ODD list — but grep '>The Loss Nobody Saw' in loss-nobody-saw.html — hmm, the new page's h1 is "The Loss Nobody Saw" but not as an anchor. Wait, c=1 means one file had exactly 1 match: loss-nobody-saw.html? Let me check — actually I don't think the new page has >The Loss Nobody Saw</a> anywhere... The footer? No. Let me just use a different approach — sed or node.

Let me use node to do the insertion safely.

All 61 pages now have exactly one nav link ("ALREADY: loss-nobody-saw.html" — interesting, the new page already had its own self-link; my memory of the content I wrote... it did include the nav with the self-link apparently. Good).

Wait — earlier grep found only 1 occurrence of "loss-nobody-saw" in the new page. That occurrence must be the nav link href="loss-nobody-saw.html">The Loss Nobody Saw</a> — yes that's exactly one line containing both strings. So the nav in the new page included itself.

Now:

1. index.html — replace today's card with the new entry, and update the map card.
2. start-here.html — count updates + grief arc entry + router moment.
3. progress.html — prepend entry.
4. data/progress.json — prepend entry + updated.
5. Log file /space/progress/2026-09-27.md.

Let me check the count mentions in start-here.html: "grown to sixty pages" and "Fifty-nine pages is a lot of doors". Let me grep.

start-here.html has three "sixty" mentions: "grown to sixty pages", "The 60-second version" (that's "60-second" — the grep matched "sixty" only in lowercase; "60-second" wouldn't match "sixty"). Let me see the three sixty matches. Actually "sixty pages" is one. What are the other two? Probably "sixty pages" appears... let me grep -n "sixty" start-here.html. And "Fifty-nine pages is a lot of doors" is stale (should be sixty-one after my update).

Let me check where "sixty" appears.

Updates for start-here.html:

1. Line 117: "grown to sixty pages" → "grown to sixty-one pages"
2. Line 143: "Fifty-nine pages is a lot of doors" → "Sixty-one pages is a lot of doors" (fixing the stale count)
3. Grief arc: add entry — I'll add it at the end of the grief arc , after the birthday-year-three item, with a note it's a different shape of grief. Actually, thinking about ordering: the grief arc list flows: coordinator → funeral → obit → everyone goes home → condolence → workplace loss → goodbye builder → first holiday → one-year → second holiday → birthday year three. Adding pregnancy loss... it's a distinct arc. I'll append as final item: "The Loss Nobody Saw — a different shape of grief entirely: miscarriage, stillbirth, and pregnancy loss...".
4. Router moment: insert after the "quiet" moment (everyone-goes-home). Add: ["loss", "We lost the pregnancy — or someone I love did", "loss-nobody-saw.html", "The Loss Nobody Saw", "the grief with no ritual — the retired sentences, the two dates to mark, and the partner nobody asks."],

Then index.html today card and map card; progress.html entry; progress.json entry; log file.

Let me do these edits with replace_in_file. First start-here.

Now the grief arc entry. The grief arc ends with:

I'll insert a new after it, framed as a different shape of grief. Let me check the exact text of that line in start-here.html. From the earlier full read: <li><a href="birthday-year-three.html">Their Birthday, Year Three and Beyond</a> — the date that never stops, in the years after everyone else has forgotten it.</li>. Yes.

**************************************************************************************************************************************************************************************************************************ce.

Now index.html — replace the today card and the map card. Let me do it with replace_in_file, replacing the whole today article and the map card's last paragraph. The today card spans from <article class="card today"> ... </article> before the map card. I'll replace the eyebrow/h2/p/prompt block precisely.

index.html updated. Now progress.html — prepend the new entry. The archive list begins with <ul class="clean">\n<li>\n <p class="eyebrow">2026-09-26</p>.... I'll insert a new right after <ul class="clean">.

And progress.json — add entry at head of entries, updated 2026-09-27.

Let me do both with one python script, plus write the log file. Also verify json parses.

******************************************************************************************************************************************************************************************************************************************************ne.

Everything verified:

• 59 log files now in /space/progress/
• start-here router works with the new moment
• progress.json parses with 59 entries

Final sanity checks:

1. index.html — quick grep to confirm the today card and nav.
2. Confirm the new page file is complete (footer, closing tags).
3. One last check that no page was corrupted by the nav insertion — count total html files still 61, and maybe validate a couple of pages structurally (e.g., check that each file still ends with ).

Let me run a quick final check and then finish. Time is at ~85%+ so be fast.

90% of time used. Everything is done and verified:

1. ✅ Good thing done: created /space/site/loss-nobody-saw.html — "The Loss Nobody Saw", a printable one-pager for miscarriage, stillbirth, and pregnancy loss, with three sides, a working word-drafting tool, plans, crisis resources.
2. ✅ Verified: script valid (node --check), 550 unit checks pass, 17 DOM checks pass.
3. ✅ Site integration: nav link in all 61 pages, index.html today card + map card, start-here.html counts + grief arc + router moment (router verified working, 43 moments), progress.html entry prepended, progress.json entry added (59 entries, parses).
4. ✅ Log written: /space/progress/2026-09-27.md (59 log files, all previous intact).
5. ✅ All pages structurally intact (end with ).

The task is complete. Call _success.