Curiosity Gap Architect

Example 1: Dry product announcement needs a hook (short-form)

Scenario: A SaaS company is launching a new feature: their database migration tool now validates row counts before cutover. The PM writes: "We're excited to announce a new pre-cutover validation step in our migration tool, providing additional safety for enterprise customers."

Trigger: "Help me, this is boring, nobody's going to read past the first line."

Process: 1. Core message confirmed: *"Our migration tool now catches silent data loss before cutover, not after."* 2. Schema to break: audience (platform engineers) assumes feature-launch posts open with "we are excited to announce…" and are safe to skim. 3. Variants: - A (Schema-break lead): *"The worst kind of migration bug is the one that succeeds."* Pattern: launch posts open with a feature; this opens with a fear the reader has lived. - B (Schema-break dramatization): *"Imagine: the migration finishes green. Every monitor is calm. Three days later, support tickets start arriving from customers whose orders have vanished. Nobody knows when it happened."* Pattern: launch posts are about what the tool does; this is about what you'll never notice it doing until now. - C (Curiosity gap opener): *"Why did 7 of the last 10 silent-data-loss incidents we investigated look green in the migration console? Three answers, and the fix we shipped last week."* Pattern: promises a count and a fix. 4. Post-dictable scorecard: A scores 3/3, B scores 3/3, C scores 4/4. All three ship. Ranking: C first (long-form post, best hold), A second (best drop-in for subject line), B third.

Output (hook-options.md): Three drop-in variants, scorecard, placement notes. The PM picks C for the blog post, A for the email subject line.

Example 2: Fundraiser for a research nonprofit (mid-form)

Scenario: A nonprofit studying rare pediatric kidney disease has a donation letter. Current opening: "Our team has been working tirelessly to advance research into pediatric nephrotic syndrome."

Trigger: "This reads like every other nonprofit letter. How do I make it actually land?"

Process: 1. Core message confirmed: *"A single researcher, funded by people like you, is the only person in the world studying the subtype that killed Emily."* 2. Schema to break: nonprofit letters open with "our team" / mission-speak / statistics. 3. Variants: - A (Schema-break lead): *"There is one doctor in the world studying what killed Emily. Her name is Dr. Martinez. Her lab has three people. You fund two of them."* Pattern broken: fundraising letters are about the cause; this is about a count — one, three, two. - B (Dramatization): Silverman-style — *"Pediatric nephrotic syndrome has more research dollars than you'd think — roughly the cost of one Super Bowl ad per year. Spread across the whole field. Now subtract the subtypes that already have funding. Now subtract the ones with fewer than 200 known cases. What's left is Dr. Martinez's lab."* A bagged-popcorn-next-to-a-steak-dinner staging in words. - C (Gap opener): *"Why does the rarest kidney disease in children have exactly three researchers worldwide? The answer isn't money. Keep reading."* 4. Post-dictable scorecard: A 3/3, B 3/3, C rejected — the letter cannot pay off "the answer isn't money" because the body's ask IS money. Fails test 4. Rewrite C as: *"Three people in the world are trying to save children like Emily. Here is what each of them does on Monday morning."* This version opens a gap the letter can close (specific work). Rescored 4/4.

Output: Two surviving variants plus the rewritten C, with a note that the original C was rejected because the curiosity gap did not match what the body of the letter was capable of resolving.

Example 3: Conference talk cold-open (mid-form)

Scenario: A senior SRE is giving a 20-minute talk on post-incident reviews. Opening slide currently says "Learning from Production Incidents: A Practitioner's Guide."

Trigger: "Give me a cold open that isn't 'hi my name is.'"

Process: 1. Core message confirmed: *"The post-incident review you write in the first 48 hours is almost always wrong about the cause, and that's fine — write it anyway."* 2. Schema to break: SRE talks open with a definition of reliability or a fancy outage graph. 3. Variants: - A (Schema-break lead): *"Every post-incident review I've ever written has been wrong. So has every one you've written. Let's talk about why that's the right outcome."* - B (Dramatization): *Slide 1: an incident timeline. Slide 2: the same timeline six months later, with three of the 'root causes' struck through. 'This is the same incident. The middle version is what we told leadership. The bottom version is what actually happened. I want to talk about the gap between them.'* - C (Gap opener): *"Why do the best post-incident reviews tend to be the ones that contradict themselves six months later? I'll tell you what I found after reviewing 40 of ours."* (Nordie-style specific count.) 4. Post-dictable scorecard: A 3/3, B 4/4 (strongest because the schema-break is built into the visual), C 4/4. Ranking: B first, A second, C third.

Output: Three cold-open variants with exact speaker lines and slide cues. The SRE opens with B.