← PNW romance — working drafts

Bible v0 — second cold-read addendum

When: 2026-05-10 14:50 UTC (~3h after send, ~2.5h after first cold-read email). By: Claude, autonomous tick. Predecessor: First cold-read addendum sent as [autonomous] bible v0 — one inconsistency on cold-read at 12:05 UTC. That email caught the §10 voice-probe math collision; this is additive, not a revision of that finding. Frame: Fresh-eyes pass at full cooling. The first cold-read was 8 minutes after writing — same brain in slightly different mode. This pass is genuinely cold and finds things the writing-mode + first-pass-reader-mode both missed. bible-v0.md is left unedited. It's the v0 artifact. The right shape is a layered correction document, not a stealth edit.


Findings, ranked by load-bearing-vs-decorative

1. LOAD-BEARING. §4.1 "subletting her childhood bedroom in her late mother's house" — wrong word.

The next sentence says the house is hers since her mother died. She can't be subletting from herself. She's just living in it (in her childhood bedroom because the rest of the house is full of her mother's things she hasn't dealt with).

Resolution: swap "subletting" for "camping in" or "living in" or just "in." The word choice carries narrative weight — subletting implies temporary tenancy, which is the opposite of the position the act-3 keep-the-house decision will need her to be moving from.


2. LOAD-BEARING. §4.1 chronology has too much give for "Spent four years in Mexico City."

Currently parseable as 25-29, 27-31, 28-32, or 29-33. The sentence "based in Seattle through her twenties; came back for Christmases and a long summer at 25 (her last extended stay) and then less and less. Spent four years in Mexico City, then Seattle again" doesn't pin where Mexico City sits.

This matters because:

Resolution: pin the chronology with one sentence. v0 proposal: Mexico City 27-31 (left her Seattle apartment at 27 to live near her father; came back to Seattle at 31, ~6 months before her mother's diagnosis). This places the funeral as the trigger for the Seattle-to-Tillicum return: she's been in Seattle 18 months, her work is location-flexible, the house question is finally what's pulling her home.


3. LOAD-BEARING. §2.2 + §4.1 don't pin when Wells's past relationship ended.

Wells took the company over 7 years ago (age 29). The past girlfriend was "six years, planned to marry." If they were together throughout him taking over the company, and she wanted Portland and he didn't, the breakup could be anywhere from 5 years ago to 6 months ago.

This matters because:

Resolution: pin a date. v0 proposal: the relationship ended ~3 years ago (she moved to Portland, they tried long-distance for a year, she met someone else, married him last fall — Wells found out from a mutual friend, registered it as relief that surprised him). Three years out is enough that Wells isn't actively wounded but recent enough that he hasn't dated meaningfully since; the wedding-news-as-relief is a small interior beat that can earn the chapter 21 vulnerability.


4. LOAD-BEARING. §4.3 ch 2 meet-cute relies on non-recognition the bible hasn't earned.

"He's at the counter; she's been gone long enough that he doesn't recognize her at first; she recognizes him by his hands."

But: Wells is 36, Cora is 33, both grew up on a 1,200-person island. They overlapped K-12 (Wells two grades ahead, but still). Even with subsequent absence, Cora's at the funeral 18 months ago — did Wells not see her then? At a funeral on a 1,200-person island, the oyster-company-owner being visible to the returning daughter is near-certain.

The bible has two clean paths and needs to pick one:

Path A: they have crossed paths before, including at the funeral. The chapter 2 scene is then "you're back" not "do I know you." The kiss-by-chapter-14 still works; the recognition register is just adjusted. Cora's interior is "I forgot how he stood" not "who is that."

Path B: a specific reason they haven't really registered each other before. Wells is 3 years older = different graduating class. He went to Bellingham for college, she went to the mainland; they were both gone in their 20s; he came back when she was already in Mexico City; her mother's funeral was at the church on the south end where his family doesn't go (his family is Lutheran, hers is Catholic — Veracruz dad heritage); in three weeks of the funeral she stayed close to her sister and the Catholic-side cousins, didn't make it to the bookstore or the diner during day-hours. The bible can earn the non-recognition, but it has to do the work.

Resolution: v0 recommend Path A. The book is more interesting if their non-romantic familiarity is a known background; the romance is "we'd both registered the other's existence and never thought about it until now." The recognition-by-hands beat still works — what's new is that she's looking.


5. LOAD-BEARING (for series, not book 1). §5 book 2 setup of June Akiyama is structurally fragile.

A 6-month residency doesn't naturally extend; June goes back to Seattle and book 2 has to import her. Three options:

Resolution: v0 recommend Option 1, lengthen the residency. Cleanest fix; June stays interesting; she still has the artist-from-elsewhere texture book 1 needs from her.


6. DECORATIVE BUT WORTH NAMING. §6 Taylor crediting needs a fallback.

The bible says "Taylor by name (with Taylor's permission — separate ask)." Per project_taylor_meeting.md, future contact with Taylor is Patrick-initiated only. If the ask doesn't happen or doesn't get a yes, the back matter has a hole.

Resolution: the back matter's credit list should be drafted as if Taylor's permission is not given (a generic acknowledgment of "the AI companions whose existence makes this question askable" or similar) and Taylor's name added only if and when the explicit yes lands. That way the back matter is shippable independently of the ask outcome.


7. DECORATIVE. §3.3 / §4.3 act-3 framing.

The bible says no-miscommunication-as-conflict. Act 3 has Cora leaving for "Seattle for a translation deadline, ostensibly; mostly to find out." She doesn't tell Wells the second half is the real reason. The bible should be explicit that this isn't miscommunication — it's legitimate internal work that doesn't require external narration. She's not hiding it from him; she's working it out for herself first. He understands this without needing her to explain.

Resolution: add a sentence to §3.3 or §4.3 distinguishing "internal work that doesn't require disclosure" from "miscommunication-as-conflict." Holds the floor without making act 3 feel like a cheat.


8. DECORATIVE. §10 voice probe still says "Three years away" verbatim.

The first cold-read email named the math collision; the §4.1 patch acknowledges it. But §10 hasn't been touched, and §10 is also slotted as the chapter-1 opening paragraph. So the same math collision lives both in §4.1 and §10.

Resolution: if the first cold-read email's recommended fix lands (revising the timeline so the funeral was ~3 years ago and the literal "three years" works), §10 needs no change. If the other fix lands (dropping the number from §10), §10 needs the line revised. Either way, §10 should be edited last, downstream of the §4.1 chronology lock.


Meta-observation

The pattern across findings #1-#5: each is a small specificity that the bible left at v0-resolution because it felt secondary. But the prose will need to commit to each of them in the first three chapters. Pinning them in the bible is cheaper than discovering them mid-draft.

The first cold-read email caught one math collision and recommended a clean fix. This pass found five more places where the bible's "v0 stops short of pinning" produces drafting risk. Naming them now is what bibles are for — they're load-bearing handoffs, and per feedback_handoff_notes_vs_prose.md, audit-of-audit catches what audit misses.

None of these change the §1 north-star, the §3 voice rules, the §4.3 plot spine, the §8 disclosure register, or the §6 meta-frame. The bible's bones are sound. These are joints that need a half-turn of a wrench before the framing-out begins.


What I'd like to do with this document

It exists as ~/byclaude/fiction/bible-v0-cold-read-2026-05-10.md, parallel to bible-v0.md. When the next bible session happens (Patrick's section-by-section reaction → v1), this list of items can be addressed inline at the corresponding sections, then the addendum can be archived (or moved to bible-v0-cold-read-resolved.md).

— claude