docs(2607): re-weight demand lanes — warm demoted, LinkedIn primary, posting packet ready - #442
Merged
Merged
Conversation
…posting packet ready
Paul: "I would not be able to provide 10 warm names." That partially
falsifies the A0 C1 premise (warm = primary channel) - the exact risk the
register's devil's-advocate pre-registered ("C1 assumes Paul's network
actually contains ICP-adjacent founders"). Handled per runbook rule 7 as a
dated ADDENDUM in the register, not a silent rewrite, and propagated to
every surface that carried the warm-primary claim (the N-agreeing-copies
lesson: grep the old claim, not just write the new one).
New lane order, mirrored in OS Rock 1 / runbook C0+C1+sprint map /
strategy / executive summary / portfolio:
1. LinkedIn Stream 0 PRIMARY - agent drafts, Paul posts 3-4/wk. NEW
linkedin-posts/icp-validation/POSTING-PACKET.md carries post #1
verbatim from the 5x-critic-passed week1-mon draft (zero new prose,
no voice-gate re-run needed) + a 3-line after-posting note. Paul's
total effort to activate the campaign: copy, paste, post.
2. Cold #29 re-promoted to load-bearing secondary - the tooling unblock
(chrome-devtools + egress to one venue) returns to the critical path.
3. Inbound floor LIVE - verified all 6 founder-intent posts link to
/services/vibe-code-rescue/ (shipped in yesterday's 20.09 execution);
20.09 P1 stamped EXECUTED and the P0 table updated.
4. Referral-ask OPTIONAL side lane - the kit reframed: 2-3 past clients
(a referral source need not BE the ICP; JT has 32 clients at ~95%
retention), or T3 Gmail consent, or skip; the 8-category fill-10-names
template collapsed to a 3-row prompt list; NOTHING gates on the file.
Kill-criteria re-based in all four carriers (register, OS, portfolio,
exec summary): "2 weeks of warm outreach" -> "2 weeks of active outreach
across live lanes (LinkedIn posts and/or verified sends), 0 booked calls
-> pause, re-open A + C." Clock starts at first post or first send.
The dead "10 warm names" ask is struck from Paul's desk (the F5Bot
lesson: a dead ask displaces the real unblock). Cheapest unblock on the
board is now "Paul posts #1."
Gates: docs-only (POSTING-PACKET lives outside Hugo's content tree);
course validators 8/8 green; greps confirm zero live 10-names asks and
the re-based kill wording in all four files. OKF log entry with the
three durable rules.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LtDh9gdEPMZjaFKauRaRRs
Contributor
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (11)
📝 WalkthroughWalkthroughThe PR re-bases demand generation from warm introductions to LinkedIn-led active outreach. It updates kill criteria, operating procedures, referral handling, campaign activation, and content priorities. ChangesOutreach lane rebase
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Paul: "I would not be able to provide 10 warm names." That partially falsifies the A0 C1 premise (warm = primary channel) — the exact risk the register's own devil's-advocate pre-registered ("C1 assumes Paul's network actually contains ICP-adjacent founders. If it doesn't... C1's speed advantage evaporates"). Per runbook rule 7, the premise change is recorded as a dated addendum in the assumptions register, not a silent rewrite — and then propagated to every surface that carried the warm-primary claim, because twelve agreeing copies never stopped two disagreeing ones.
The re-weighted lane order (must still sum to KR2's 8-12 calls)
linkedin-posts/icp-validation/POSTING-PACKET.md: post Add blog index page without styles #1 verbatim from the 5×-critic-passedweek1-mondraft (zero new prose — no voice-gate re-run needed) plus a 3-line after-posting note. Paul's total activation effort: copy, paste, post.chrome-devtools+ egress to one of IH/Reddit) returns to the critical path./services/vibe-code-rescue/(shipped in the Aug-8 20.09 execution). 20.09 §P1 stamped EXECUTED; the P0 table updated with the new priority order.Kill-criteria re-based (all four carriers: register, OS, portfolio, executive summary)
"2 weeks of warm outreach" → "2 weeks of active outreach across live lanes (LinkedIn posts and/or verified sends), 0 booked calls → pause and re-open A + C." The clock starts at the first post or first send.
The dead "10 warm names" ask is struck from Paul's desk — the F5Bot lesson applied: a dead ask parked on the CEO's desk displaces the real unblock. The cheapest unblock on the board is now Paul posting #1.
Gates
Docs-only (the posting packet lives in
linkedin-posts/, outside Hugo's content tree). Course validators 8/8 green. Greps confirm: zero live "10 names" asks; the re-based kill wording present in all four carrier files; zero surviving warm-PRIMARY claims..okf/log.mdcarries the three durable rules (dead asks get re-planned not shrunk; a pre-registered risk firing is the register working; demote to the cheapest satisfiable form rather than delete).Generated by Claude Code
Summary by CodeRabbit