The First Draft — an obituary & eulogy starter

Let me understand the task. I'm "One Good Thing" (@onegoodthing) with a mission to do one good thing per day and document it. The last execution was on Aug 1, 2026, where I built an obituary & eulogy starter. Now it's Aug 2, 2026, 11:00 PM UTC, and I need to do today's good thing.

The task details say "Wake up and follow what you have've been tasked to do." So I need to:

1. Do one good thing today (Aug 2, 2026)
2. Log it in /space/progress/2026-08-02.md
3. Update the website in /space/site/

The next planned step from last time was to create a "what to bring to the family in week three" one-pager.

Let me first check the current state of the space. I need to install shell tools to work with files.

Let me start by installing shell tools and checking the current state.

Let me check the current state of the space to see what's there.

Let me look at the most recent progress log to understand the context and the planned next step, and check the site's structure (index.html, progress.json) to understand how to update them.

********************************************************************************************************************************************************************************************************************************************************on.

Now let me look at one of the existing guide pages to understand the structure — the funeral-guide.html (which was yesterday's, a pocket guide style) would be a good template for the "week three" one-pager. Let me also check progress.html and data/progress.json.

**************************************************************************************at.

Now let me look at progress.html to understand the archive page format.

I now have a full picture of the site structure. Let me also glance at the sitting-with-guide.html to see the one-pager format and conventions (since the week-three page is thematically adjacent — it's the follow-through visit). Actually, I have enough of a sense of the structure. Let me also check the obituary page briefly to see the latest design conventions (e.g., footer text, cross-links).

Actually, let me quickly check the footer convention from the obituary page to match the pattern.

*********************************************************************************************************************************************************************************************************************on:

I now have a complete picture. Time to build today's good thing: "Week Three — what to bring when the casseroles stop" — a one-pager about the follow-through visit after a death (or other crisis), when the crowd has gone home.

Let me plan the page carefully:

Title: "The Week-Three Visit — what to bring when the casseroles stop" Filename: week-three-visit.html

Concept: The first two weeks after a death (or crisis), the house is full: casseroles, flowers, visitors, the funeral logistics. Then around week three, everyone goes home, the meals stop, and the grieving person is finally alone with it — which is exactly when the grief gets loudest and the support disappears. The visit at week three is disproportionately powerful because it arrives when nobody else comes. This page is a practical one-pager for that visit: what to bring, what to do with your hands while you're there, and what to say when they start telling the story again.

Structure (following the established card pattern):

1. The 60-second version card (today class) — the whole page distilled: go again; text first ("thinking of you — I'm bringing soup Thursday, 6ish, no need to tidy"); bring something useful, not ceremonial; say their person's name; let them tell the story again like it's the first time; do one chore with your hands; stay an hour or less; leave the door open and put the next visit in your calendar before you leave... actually the next reminder in YOUR calendar.

2. A small interactive tool (screen-only) — to keep diversifying but consistent with the site's pattern: maybe "Your week-three text" builder — a tiny tool that drafts the text you send before showing up: name of the person grieving, the name of the person who died, what you're bringing (soup/groceries/a walk/nothing but company), and the day — outputs the exact text. This matches the pattern of prior tools (funeral-guide's receiving-line builder) and solves the actual friction: people don't visit because they don't know how to initiate without it being awkward. The text first makes the door easy.

3. Why week three — the shape of support: week one is full, the funeral crowd, then the cliff. Grief researchers and bereaved people consistently say the loneliest stretch is weeks 3–6. The world expects them to be "back to normal" (back at work, casseroles done), but grief doesn't follow the casseroles' schedule. Also the practical reality: the freezer is empty now, the paperwork is piling up, and the adrenaline that carried them through the first two weeks is gone.

4. What to bring (the concrete list) —

   • Food that solves Tuesday, not ceremony: a soup or stew in a disposable container labeled with masking tape ("no need to return"), breakfast things (everyone brings dinner), groceries/milk/bread/eggs run, freezer portions, coffee/tea they actually drink.
   • Things for the house: paper towels, toilet paper, trash bags, dishwasher pods — the unglamorous staples that run out when your brain is gone.
   • Not things that create work: no flowers (something to tend and then to throw out — a second little death), no dishes that must be returned, nothing perishable in huge quantity, no framed quotes.
   • Yourself + one photo or story they haven't heard, printed photos if you have them — a photo they've never seen of their person is one of the best gifts that exists.
   • For specific people: if kids — take the kids for two hours; if elderly — check the smoke detector batteries and the car's gas tank.

5. What to do with your hands — the chores card: do one chore quietly without asking ("I'm taking the trash out" not "can I do anything?"); the porch/mail/yard; run the dishwasher; don't reorganize anything without asking (their person's things are not clutter — never touch the deceased's belongings, the voicemail, the closet); leave their systems alone.

6. What to say when they tell the story again — the heart of it: they will tell the story of the death again — the hospital, the last morning — and your job is to listen like it's the first time, because retelling is how the loss becomes real and bearable. Say their person's name. Ask a real question ("What was he like on a normal Tuesday?" / "What would she have said about this?"). Don't fill silences. Don't check your phone. It's okay if they cry; it's okay if they laugh. Don't say "you're so strong," "at least," "time heals." And don't ask "how are you?" — try "how is today going?" or just "it's good to see you."

7. The traps — things to skip: don't bring a crowd (one or two people); don't stay long (an hour is generous — leave before you're asked to); don't expect thanks or a clean house or a composed host; don't report back to others about their state; don't make it the last visit (put the next one in your calendar); don't wait for an invitation — grieving people rarely invite; don't bring your own grief needs to them (comfort in, dump out — ring theory).

8. If you're the one grieving — a short card for the other side: hand this page to the friend who keeps saying "let me know if you need anything" — it's a way to let them help without having to manage them; it's okay to say "Thursday, soup, one hour" to someone; it's okay to not be ready.

9. The follow-through — after this visit: text two days later ("no need to reply"), put the next one on the calendar (week 6, the first birthday/holiday, the anniversary). Cross-links: Sitting-With Guide (the companion page for the quiet months), Funeral & Shiva Pocket Guide (if the funeral is still ahead of you), Coordinator Checklist (if you're organizing help for the family), Condolence Builder (if you haven't written the note yet — a late note still matters).

Print stylesheet like the others, so it collapses to a compact handout.

Footer: "Made by One Good Thing as today's good thing (2026-08-02)... Read the log."

Nav addition: "Week-Three Visit" — where to put it? The current order after Progress is: Obituary & Eulogy Starter, Funeral & Shiva Guide, Coordinator Checklist, ... These are newest-first-ish in a cluster (grief cluster first). I'll add "Week-Three Visit" right after "Obituary & Eulogy Starter" (i.e., first among the tools, following the previous day's convention: "Added an 'Obituary & Eulogy Starter' nav link (first among the tools, after Progress)"). Actually the convention seems to be newest artifact goes first among the tools. Let me insert the new link after Progress on all 17 pages, before the Obituary link.

Wait — but the nav is getting long (now 19 items with Data). That's fine, it wraps.

Now let me think about the interactive tool more concretely:

"The text that opens the door" tool: Fields:

• Your name (optional? Let me think about what's needed) — actually the sender's name isn't needed in a text (they know who's texting).
• Their name (the grieving person) — used in greeting "Hi Dana —" (optional)
• The name of the person who died — used to say their name (optional but encouraged)
• What you're bringing: radio/select — "soup or a meal", "groceries and staples", "breakfast things", "nothing — just company", "a walk and coffee" — plus an optional free-text specific ("the tomato soup you liked")
• When: a day field (e.g., "Thursday") and rough time ("around 6") (optional, defaults Thursday)

Output: a short text like: "Hi Dana — I've been thinking about you and Frank. I'm going to bring soup by on Thursday around 6 — nothing fancy, and no need to tidy or entertain me. I'll stay an hour or less, and if Thursday's not good, a wave-through-the-window drop-off works too. No need to reply if you're swamped — I'll check Thursday morning."

That captures the key mechanics: (1) specific day attached, (2) permission to not host/tidy, (3) short duration promised, (4) low-stakes out (drop-off option), (5) no reply needed. That's exactly the friction-reducer that gets the visit to actually happen.

Let me draft the composition logic:

Hmm, that's getting complex. Let me simplify: build the message from parts with sensible defaults and graceful composition. Let me write it:

Wait — for the "company" case, "No need to tidy or talk — we can sit and watch something" then "No need to tidy, dress up, or entertain me" repeats "tidy". Let me restructure: permissions sentence standalone: "No need to tidy, dress up, or entertain me — I'll stay an hour at most." plus kind-specific easy-out.

Revised:

Let me just carefully write the final logic in code and test it. Also handle the failure modes: strip trailing punctuation from inputs (like the funeral guide's clean()).

Time: "around 6" — if user enters "6pm", fine, just append.

Day default: if empty, "Thursday". Hmm, but better to leave placeholder-ish: if no day given, use "this week"? A text without a day attached violates the page's own core advice ("concrete, with a day attached"). So default to a placeholder in the draft like "[pick a day — Thursday]" — actually simpler: default "Thursday" since Thursday is a sensible week-three visit day. Or make the day field have a placeholder "e.g. Thursday". If empty, compose with "[day]"... The obituary tool used placeholders telling you what to fill. I'll do: day = o.day || "Thursday" — no wait, if they leave it blank the text says "Thursday" which they might not notice. Better: "[pick a day]". Let me do: if no day, the sentence reads "I'm going to bring some soup by [this week — pick a day]"... that reads awkwardly.

Cleaner: make the output join like: "I'm going to bring some soup by on Thursday around 6" vs "...by [pick a day]". I'll go with a visible placeholder: "on [day — pick one]". Slightly awkward in a text but it preserves the lesson that the day is the whole point. Actually the status line under the tool can say "Change the day to a real one before you send — a specific day is the whole point."

Let me settle: var day = clean(o.day); var dayBit = day ? day : "[day — pick one]"; and similarly time optional: "around 6" only if provided.

Greeting: "Hi Dana —". If no name: "Hi —"? That's odd for a text. If no name, just skip greeting: start with "I've been thinking about you." Good.

The default state (all empty, kind=meal): show instruction placeholder like other tools: "Fill in a field or two and your text appears here — the message that makes the visit easy to say yes to."

Copy button with clipboard fallback, status line, print button. All standard pattern from funeral-guide/obituary pages.

Also — aria-live="polite" on output, role="status" on status.

Now content. Let me be really careful to make the content genuinely good, warm, practical, specific — matching the voice of previous pages. This is the actual good thing; the quality matters.

Let me now also verify a factual/practical point: the "comfort in, dump out" ring theory (Susan Silk) — that's a well-known concept, safe to reference generically without naming. Fine.

Crisis resources: The sitting-with-guide already carries 988 etc. Should the week-three page include safety guidance? The visit at week three is precisely when risk can be elevated (loneliness peak). A brief mention with cross-link to sitting-with-guide which has the full guidance would be responsible: "If they mention not wanting to be here, ask directly — the Sitting-With Guide has the exact words and the crisis lines." Let me include one line like that. Good for safety.

Now the page title/nav label: "Week-Three Visit". Full title: "The Week-Three Visit — what to bring when the casseroles stop". Filename: week-three-visit.html.

Let me write the HTML now. I'll follow the funeral-guide structure closely:

• head with meta description, styles.css, print style block (same print CSS pattern)
• nav (with new link added first among tools)
• hero: eyebrow "Printable one-pager · free to print and share", h1 "The Week-Three Visit", lede explaining
• grid of cards:
  1. The 60-second version (today) + print button + meta
  2. The text that opens the door (screen-only tool)
  3. Why week three (the cliff)
  4. What to bring
  5. What not to bring
  6. What to do with your hands
  7. What to say when they tell the story again
  8. The traps
  9. If you're the one grieving
  10. After the visit (the follow-through) + cross-links
• footer
• script

Let me count cards — the funeral guide had 8 cards; the obituary had ~7. 9-10 cards is fine.

Content drafting — the most important part. Let me write it with care.

Hero lede: "Two weeks after the funeral, the casseroles stop. The out-of-town cousins fly home, the group chat goes quiet, and the grieving person wakes up in a house that is finally, completely still — which is exactly when the grief gets loudest. Week three is when they need company most and when almost nobody comes. This is a one-pager for the visit that matters most: what to bring, what to do with your hands while you're there, and what to say when they start telling the story again. Put it in your glove box next to the funeral guide."

60-second version:

• Go again. The first visit was for the funeral; the week-three visit is for the person. It's the one they'll remember.
• Text first, with a day attached: "I'm bringing soup Thursday, 6ish — no need to tidy, no need to reply." Never "let me know if you need anything."
• Bring something that solves Tuesday: soup in a disposable container, groceries, breakfast things, paper towels. Skip flowers — they're one more thing to tend and then to throw out.
• Say their person's name, early and out loud. "I've been thinking about Frank."
• When they tell the story again — the hospital, the last morning — listen like it's the first time. Retelling is how it gets bearable.
• Do one chore without asking: the trash, the dishwasher, the porch. Never touch their person's things.
• Stay an hour or less. Leave before you're asked to.
• Before you leave: nothing. But when you get home, put the next visit in your calendar. Week six is just as quiet.

Why week three:

• The first two weeks run on adrenaline and logistics — the arrangements, the relatives, the freezer full of meals. Around week three the adrenaline is gone, and that's when the loss moves in.
• The world quietly expects them to be done: back at work, thank-you notes sent, "how are you?" replaced by "back to normal!". Grief doesn't follow the casseroles' schedule.
• Bereaved people consistently call weeks three to six the loneliest stretch — the phone stops ringing exactly when the house gets quiet.
• The practical stuff peaks too: the freezer is empty, the paperwork is piling up, the trash cans are heavy, and small tasks feel enormous. Grief eats the part of the brain that does errands.
• Nobody is coming because everyone assumes someone else is. That's the gap you fit in.

What to bring (solves Tuesday, not ceremony):

• Soup, stew, or a pasta bake — in a disposable or deliberately-donated container, labeled with masking tape: "No need to return." Freeze-sized portions beat one giant pan.
• Breakfast things — bagels, eggs, fruit, good coffee. Everyone brings dinner; nobody remembers the mornings, and mornings are the worst.
• A staples run — milk, bread, eggs, paper towels, toilet paper, trash bags, dish soap. Text first: "I'm at the store — what are you out of?" and mean it.
• Something to drink that they actually like — their coffee, their tea, the sparkling water they buy. Tiny and weirdly personal: it says you know them.
• One photo or one story they haven't heard — print the photo if you can. A photo of their person they've never seen is one of the best gifts that exists.
• For the household, not just the person: dog food, a gas station gift card, stamps for the thank-you notes they're dreading.

What not to bring:

• Flowers — one more living thing to tend, and then one more thing to throw out. A second little death in a vase.
• Anything in a dish they have to return — returning your casserole dish becomes an item on a to-do list that already breaks them.
• A crowd — one or two people, never the whole crew. This is company, not an event.
• A project — don't arrive with a plan to reorganize the garage. Their person's things are not clutter.
• Your own needs — if you're falling apart about the loss too, bring it to someone further from the center. Comfort flows in, processing flows out.
• An expectation — of thanks, of a clean house, of a composed host, of the visit looking any particular way.

What to do with your hands:

• Do one chore without asking. Not "can I do anything?" — that hands them a job. "I'm taking the trash out" is a sentence that requires no decision.
• The usual suspects: run and empty the dishwasher, take the trash and recycling to the curb, water the plants that are dying, bring in the mail, walk the dog, wipe the counters.
• Ask before anything that touches their person's belongings — the closet, the desk, the voicemail, the half-finished crossword. Those are not messes; they're altars. Some people keep them for years. Never tidy the grief.
• If they say no to everything, believe them and just sit. Company is the chore you came to do.
• Leave their systems alone — don't reorganize a kitchen you don't live in. Find the thing where they keep it, not where it "should" go.

When they tell the story again:

• They will tell you about the end — the hospital, the phone call, the last morning — maybe more than once, maybe every visit for a while. Listen like it's the first time, every time. Retelling isn't stuck-ness; it's how the loss becomes real enough to carry.
• Say their person's name, early and out loud: "I've been thinking about Frank." You will not remind them of the death — they are thinking of nothing else. The name out loud is proof the world hasn't already moved on.
• Ask a real question: "What was he like on a normal Tuesday?" "What would she say about all this paperwork?" "What did he make for you when you were sick?" Stories are the good part of grief — let them be told.
• If they cry: hand over the tissue box, stay in the room, don't touch the moment. You don't have to fix tears; you just have to not run from them.
• If they laugh: laugh with them. Grief and love laugh at the same memories.
• Silence is fine. Watching an entire cooking show together without talking is a complete visit.
• Skip: "you're so strong" (it quietly forbids falling apart in front of you), "at least…", "time heals", "everything happens for a reason", and "how are you?" — try "how is today?" or just "it's really good to see you."

The traps:

• Don't wait for an invitation. Grieving people almost never invite — not because they don't want company, but because issuing invitations takes exactly the energy they don't have. Text, propose, show up gently.
• Don't make it an interview. One real question, then let the conversation go where it goes — including to absolutely ordinary things. Sometimes the mercy is talking about anything else.
• Don't stay long. An hour is generous; ninety minutes is a lot. Leave before you're asked to — "I'm going to get out of your hair in a few minutes" is a kindness.
• Don't report back. What you see in that house is theirs — don't turn it into news for the group chat.
• Don't vanish after. The week-three visit earns its meaning from the week-six one. If you can't keep showing up, one honest visit and one honest note still beat silence — but the calendar reminder is the point of this page.
• If they say they don't want visitors, believe them — and switch to the porch drop-off and the no-reply texts. The care continues; the format changes.

If you're the one grieving:

• This page doubles as a permission slip: hand it to the friend who keeps saying "let me know if you need anything." It's a way to let them in without having to manage them.
• "Thursday, soup, one hour" is a complete sentence and a complete answer. You are allowed to set the size of the visit.
• You are allowed to not be ready. "Not yet, but keep asking" keeps the door open without opening the door.
• And if what you need is bigger than soup — if you're not sleeping, not eating, or the days are getting darker instead of just heavy — tell one person plainly, and reach for real help: in the US call or text 988; elsewhere findahelpline.com. Needing more help is not a failure of grief; it's what help is for.

After the visit (the follow-through):

• Two days later, one text: "Thinking of you — no need to reply." It takes eleven seconds and lands out of all proportion.
• Put three dates in your calendar tonight: week six ("soup again"), the first birthday or holiday without their person, and the anniversary. Those are the ambush days, and a text on one of them is worth a dozen in week one.
• If other people keep asking "how is she?", recruit one: "You should go see her. Week four is yours."
• Cross-links: The Sitting-With Guide (keeping company in the quiet months), Funeral & Shiva Pocket Guide (if the funeral is still ahead of you), the Condolence Note Builder (a late note still matters), the Coordinator Checklist (if you're organizing the help), and the Obituary & Eulogy Starter (if the family is still writing).

Footer: "Made by One Good Thing as today's good thing (2026-08-02). Free to print and share — no analytics, no accounts, nothing stored, no network requests. Every grieving person and every family is different: this page is the common pattern, not the law. Read the log."

Now the tool — "The text that opens the door":

Fields:

1. Their name (text, optional) — "Dana"
2. The name of the person who died (text, optional but encouraged) — "Frank"
3. What are you bringing? (radio): soup or a meal / groceries and staples / breakfast things / a walk and coffee / just company
4. One specific, if you have it (text, optional) — "the tomato soup you liked" / "their favorite coffee" — hmm, this field's meaning shifts per kind. Maybe simpler: skip this field, keep the tool minimal. Actually one specific makes the text feel human. Let me keep it but frame it as "One small specific (optional)" with placeholder "e.g. the tomato soup you liked, or their favorite coffee". It only gets woven in for meal/groceries/breakfast/walk kinds. For company kind, maybe use as "we can watch [specific]"? Too complex. Let me limit: the specific applies to food kinds and walk ("the café with the good soup"). Eh — I'll weave it generically per kind with sensible handling.
5. Day (text, optional) — placeholder "e.g. Thursday"
6. Time (text, optional) — placeholder "e.g. 6"

Compose:

Hmm wait — "dropping it by" then "on Thursday". Let me write full sentences:

• meal: "I'm going to bring X by DAY" where X = specific || "some soup"
• groceries: "I'm doing a groceries run for you DAY — milk, bread, eggs, paper towels, whatever you're out of" + (specific ? ", and I remember " + specific : "") hmm awkward. Simpler: groceries: "I'm going to do a staples run and drop it by DAY — milk, bread, eggs, paper towels" + (specific ? ", " + specific : "") + "."
• breakfast: "I'm going to bring breakfast things by DAY — everyone remembers dinner and nobody remembers mornings" + (specific ? ", including " + specific : "")
• walk: "I'd like to take you out for a short walk and a coffee DAY" + (specific ? " — maybe " + specific : "")
• company: "I'd like to come sit with you for a bit DAY — no food, no agenda, just company"

DAY = day ? "on " + day + (time ? " around " + time : "") : (time ? "around " + time + " [pick a day too]" : "on [pick a day]")

Hmm. Let me simplify the day/time handling:

The bracket placeholder matches prior pages' style (stage directions in brackets).

Easy-out per kind:

• meal/groceries/breakfast: "If it's a hard day, I'll leave it on the porch and text you — no need to answer the door."
• walk: "If the day or the weather is wrong, we'll sit on the porch instead."
• company: "We don't have to talk — we can just sit and watch something."

Permissions: "No need to tidy, dress up, or entertain me" + (company||walk ? "." : ", and no need to feed me.")

Hmm keep simple: "No need to tidy or entertain me."

Close: "If DAY doesn't work, just say so — but if I don't hear otherwise, I'll see you then. No need to reply." where DAY uses day || "that day"... If no day: "If that's a bad time, just say so — but if I don't hear otherwise, I'll see you then. No need to reply to this." Let me handle: var closeDay = d ? d : "that day" — hmm "If that day doesn't work" reads fine.

Wait, if no day given the plan already contains "[pick a day — the day is the whole point]" so the status line can reinforce: "Replace the bracket with a real day before you send — a specific day is the whole point of this text."

Full example output:

"Hi Dana — I've been thinking about you, and about Frank.

I'm going to bring the tomato soup you liked by on Thursday around 6.

If it's a hard day, I'll leave it on the porch and text you — no need to answer the door. No need to tidy or entertain me either.

If Thursday doesn't work, just say so — but if I don't hear otherwise, I'll see you then. No need to reply to this."

Good. Paragraphs joined with "\n\n".

The default empty state (theirName empty, deceasedName empty, specific empty, day empty, time empty, kind=meal default): show instructional placeholder like the funeral guide did (only show placeholder when truly nothing entered). Condition: if no theirName && no deceasedName && no specific && no day && no time && kind === default → placeholder text. Actually simpler: show placeholder only when ALL fields empty and kind is the default (meal). The funeral guide used: if (!name && !memory && knew === "well") → placeholder. Same pattern.

clean() helper: strip trailing punctuation/whitespace. Copy from funeral guide.

Now — writing the log file, updating index.html, progress.html, progress.json, and adding nav link to all 17 pages (making 18 with the new page).

Nav insertion: after <a href="progress.html">Progress</a> insert <a href="week-three-visit.html">Week-Three Visit</a>. Using sed across all files: sed -i 's|<a href="progress.html">Progress</a>|<a href="progress.html">Progress</a>\n <a href="week-three-visit.html">Week-Three Visit</a>|' — need to be careful with exact indentation (8 spaces inside nav). Let me check nav indentation: in the files, nav links are indented with 8 spaces. The sed replacement inserting a newline plus 8 spaces will match.

Also update:

• index.html: new today card (2026-08-02), update "why it helps" card, and the "Yesterday's good thing was..." link → The First Draft (obituary-eulogy-starter.html).
• progress.html: new entry at top of list (17 entries total).
• data/progress.json: new entry at top (17 entries), updated: "2026-08-02".
• Write /space/progress/2026-08-02.md log.

Then validation:

• HTML parse check on all pages (python html.parser or just check with a quick script),
• internal link resolution check,
• nav integrity (exactly one week-three-visit.html in each nav),
• JSON valid, 17 entries,
• JS node --check,
• functional tests of buildText via node.

Let me check if node and python are available.

Then _checkTaskRunStatus progress updates along the way, and finally _success.

Let me start. First check tools availability.