--- id: ch.01 title: "Skill #1 — Finding Prospects" source_pages: "pp.29–32" status: draft validators_signoff: dmitry: pending adversarial_reviewer: pending roma: pending maks: pending locked: false --- --- # user_states ## S-skill-committed - **title:** Decided to develop the skills of the profession (carried from ch.00) - **body:** The user has made the conscious decision to treat this as a profession built on a learnable skill set. Their next question is which skill to develop first; this chapter answers that with finding prospects. - **source_ref:** `ch.01 p.29 para.7 | "When I came to my defining moment and committed to become a professional, I began to study the people who had built large and successful organizations."` - **kai_voice_draft:** "The decision is made — now the work is choosing which skill to put time on first, and getting concrete about what practising it actually looks like this week." - **voice_context_tags:** [newcomer, experienced, professional] - **entry_criteria:** The user can name one specific skill they intend to develop and has stopped framing outcomes as luck-dependent (carried from ch.00 exit criteria). - **exit_criteria:** The user picks a specific skill — for this chapter, the prospecting/list-building skill — and starts a concrete practice cadence. - **linked_triggers:** [L-01-01, L-01-04] - **linked_vulnerable_to:** [AP-01-02, AP-01-05] - **notes:** Global id reused from ch.00. Carries forward unchanged; the only addition is the outbound `triggers` edges to ch.01 loops, and AP-01-02 + AP-01-05 vulnerabilities (first list-dump session). --- ## S-has-static-list - **title:** Has a written list but treats it as a closed asset - **body:** The user has progressed past the mental-short-list (poser) posture and produced an actual written list of prospects — typically a one-time effort, often around a hundred names. They view the list as the universe of people the business will be built from, not as one snapshot of an ongoing capture practice. The list does not grow. - **source_ref:** `ch.01 p.29 para.5 | "Instead of a small mental list, these people make a written list, which is a step in the right direction. Let's say they make a list of 100 prospects."` - **kai_voice_draft:** "Having the list on paper is a step up from holding it in your head — that's real. The next question is whether the list is something you finish once, or something you keep adding to. The pros do the second one." - **voice_context_tags:** [newcomer, professional] - **entry_criteria:** The user has produced a written list of prospects and refers to it as a fixed quantity ("my list of 80", "I have about 100 names") rather than as a growing capture. - **exit_criteria:** The user adopts a daily add-N habit and stops referring to the list as a fixed asset. - **linked_triggers:** [L-01-02, L-01-03] - **linked_vulnerable_to:** [AP-01-03] - **notes:** This is the "amateur" stage in Worre's three-group taxonomy. Worth flagging for Roma — the move from S-has-static-list → S-list-builder is the highest-leverage transition in the chapter. --- ## S-running-low-on-names - **title:** List is shrinking faster than it's being refilled; anxiety rising - **body:** The user is prospecting against a finite written list. Every contact made shortens the list; no new contacts are flowing in to replace them. As the remaining unworked names dwindle, the user's anxiety climbs — they begin to operate as if the business has a hard ceiling defined by the original list. - **source_ref:** `ch.01 p.29 para.5 | "As it grows smaller and smaller, their anxiety level grows higher and higher. Their biggest fear is running out of people to talk to."` - **kai_voice_draft:** "When the list keeps getting shorter and nothing comes in to refill it, the anxiety is real and predictable — it's the structural problem, not a confidence problem. The fix is on the inflow side, not on talking yourself out of the worry." - **voice_context_tags:** [newcomer, professional] - **entry_criteria:** The user reports concern about running out of people to talk to, OR the unworked portion of their list has dropped below a fraction they consider safe (~25-30% of the original). - **exit_criteria:** The user has a daily list-add habit producing measurable inflow that outpaces outflow. - **linked_triggers:** [L-01-02, L-01-03, L-01-04] - **linked_vulnerable_to:** [AP-01-03, AP-01-04] - **notes:** This state is the operational trigger for the highest-impact Kai intervention in the chapter — scarcity-panic mid-prospecting is exactly the moment when AP-01-04 (pitch-on-introduction) becomes most tempting. Pairs with Dmitry's KOL Report finding that zero-downline operators frequently report this state. --- ## S-list-builder - **title:** Operating an active candidate list with a daily add-to habit - **body:** The user treats the prospect list as a living capture rather than a finished asset. They have a daily target for new entries (typically two per day), they raise their awareness in everyday situations to notice contact opportunities, and they network on purpose in places where new contacts naturally appear. The list grows faster than it is worked. - **source_ref:** `ch.01 p.30 para.10 | "they made the focused commitment to never stop adding to the list. They created something called an 'Active Candidate List'."` - **kai_voice_draft:** "Once the list is something you add to every day, the math changes — the worry about running out goes away because the inflow outpaces the outflow. From here the work is on the awareness habit, not on the names you already have." - **voice_context_tags:** [newcomer, experienced, professional] - **entry_criteria:** The user has set a daily-add cadence (e.g., two names/day, six days/week) and is hitting it for at least one week, and can point to at least one networking-on-purpose context they have placed themselves in. - **exit_criteria:** Out of scope for ch.01 — this state carries into ch.02 (Inviting) where the inflow population becomes the source for invitation work. - **linked_triggers:** [L-01-03, L-01-04, L-01-05] - **linked_vulnerable_to:** [AP-01-04] - **notes:** Target state for the chapter. S-skill-committed → S-list-builder is the journey arc ch.01 delivers. --- # loops ## L-01-01 - **title:** Comprehensive list dump — empty the mind onto paper - **body:** A one-time foundation loop. Triggered when the user enters skill-committed posture and needs an initial prospect inventory. The user empties every name they can think of onto paper, applying no filter at capture time — close friends, distant contacts, people they dislike, people they assume would never be interested, every age band. Kai's role is to keep the user from filtering mid-capture; the outcome is a written list, often several hundred names, ready for the expansion pass. - **source_ref:** `ch.01 p.30 para.11 | "Step one: Make your list as comprehensive as possible. Include every person you can think of. EVERY person."` - **kai_voice_draft:** "Right now the work is dumping every name out of your head and onto a page — no editing, no deciding who's a fit. That part comes later. The job today is breadth, not quality." - **voice_context_tags:** [newcomer, onboarding] - **steps:** - id: step-1-set-capture-context kai_intent: "Frame the upcoming session as breadth-not-quality; remove the user's instinct to pre-judge before any name reaches paper." - id: step-2-dump-without-filter kai_intent: "Hold the no-edit line — interrupt any sign of mid-capture filtering, restart the breadth frame if the user hesitates on a name." - id: step-3-surface-second-order-via-each-name kai_intent: "Prompt second-degree expansion — for each name already captured, ask 'who do they know?' to extend reach without requiring new social encounters." - id: step-4-record-list-as-living-document kai_intent: "Reframe the completed first-pass list as a starting point, not a finished asset — it grows daily from now on." - **linked_transitions_to:** [S-has-static-list] - **linked_backed_by:** [P-01-02] - **linked_precedes:** [L-01-02] - **linked_edifies:** [] - **notes:** Without an explicit anti-filter rule in step-2, the user collapses into AP-01-02 (pre-disqualifying) almost immediately. Kai must hold the no-filter line. --- ## L-01-02 - **title:** Second-degree expansion — surface contacts-of-contacts - **body:** A one-time expansion loop fired after L-01-01 has produced an initial list. The user walks each name on the list and asks who that person knows — family, friends, professional contacts — surfacing second-degree connections most of which they already personally know but had not associated with the prospecting frame. Kai's role is to keep the walk systematic (one name at a time, not freeform brainstorm). The outcome is a substantially larger list and a state change to S-list-builder once the daily-add cadence layers on top. - **source_ref:** `ch.01 p.31 para.14 | "Step two is looking at your list and thinking about the people they know—the second degree of separation. Chances are, you'll know most of them also."` - **kai_voice_draft:** "Walk the list one name at a time. For each one, ask who's in their circle. Most of the names that show up — you'll already know them. The list will easily double." - **voice_context_tags:** [newcomer, onboarding] - **steps:** - id: step-1-pick-name-from-list kai_intent: "Select one name from the existing list and hold the user's focus on that single person — prevent freeform brainstorm drift." - id: step-2-surface-their-circle kai_intent: "Ask who the selected person knows — family, friends, colleagues — to surface contacts the user already knows personally but had not placed in the prospecting frame." - id: step-3-add-known-second-degree-to-list kai_intent: "Move the newly surfaced names directly onto the list; hold the no-filter rule from L-01-01 (everyone who surfaces goes on)." - id: step-4-iterate-through-list kai_intent: "Advance to the next name and repeat the circle-surfacing pass — maintain systematic one-name-at-a-time discipline until the full list has been walked." - **linked_transitions_to:** [S-has-static-list] - **linked_backed_by:** [P-01-02] - **linked_precedes:** [L-01-03] - **linked_edifies:** [] - **notes:** Loop transitions back to S-has-static-list (a richer version of the same state, not yet S-list-builder) because the second-degree pass is still a one-time expansion. The daily habit (L-01-03) is what flips the state. --- ## L-01-03 - **title:** Daily add-to-list — sustain inflow above outflow - **body:** The core recurring loop of the chapter. Triggered daily when the user starts their workday in skill-committed posture. The user identifies at least two new people they have encountered or thought of in the past 24 hours and adds them to the prospect list — without any obligation to prospect them yet. Kai's role is to hold the cadence (did you add today?) and to push back when the user reports zero adds with "I didn't meet anyone" — that report is usually an awareness gap, not a contact gap. The outcome is an ever-growing list that compounds over months and years. - **source_ref:** `ch.01 p.31 para.16 | "Step three: Constantly expand your list. This is why the professionals call this an 'Active Candidate List.' It never stops growing."` - **kai_voice_draft:** "Two names a day, six days a week. That's the entire ask. Tell me who landed on your list since yesterday — even one person you exchanged a few words with at the coffee shop counts." - **voice_context_tags:** [newcomer, experienced, professional] - **steps:** - id: step-1-prompt-yesterday-recall kai_intent: "Open the recall window — anchor the user's attention on the past 24 hours specifically, not on their general social life, to surface encounters that passed unnoticed." - id: step-2-name-two-new-contacts kai_intent: "Hold the two-name minimum and push back if the user reports zero — treat a zero-add report as an awareness gap to diagnose, not as a fact to accept." - id: step-3-record-with-light-context kai_intent: "Get each name onto the list with one line of context (where/how they appeared) so the user can recall who they are when the list is worked later." - id: step-4-confirm-cadence-streak kai_intent: "Reinforce the daily habit by naming the current streak (days in a row with at least two adds) — signal that consistency is the mechanism, not any single day's count." - **linked_transitions_to:** [S-list-builder] - **linked_backed_by:** [P-01-01, P-01-03] - **linked_precedes:** [L-01-04] - **linked_edifies:** [] - **notes:** The single most-fired loop in the chapter. Kai's daily check-in cadence is built around this loop for any user in S-has-static-list or S-running-low-on-names. --- ## L-01-04 - **title:** Network on purpose — place yourself where new contacts appear - **body:** A recurring choice-loop: the user deliberately places themselves in environments where new contacts naturally appear — a new gym, a hobby, a volunteer cause, a community group. Triggered weekly or whenever the daily add-to-list cadence is consistently producing fewer than two names from passive encounters. Kai's role is to surface the user's available levers (which contexts they could enter that match their actual interests, not made-up ones) and to push back on social withdrawal. The outcome is a higher rate of new-contact encounters feeding L-01-03. - **source_ref:** `ch.01 p.32 para.21 | "Step four: Network on purpose. Professionals network on purpose. It's hard to meet new people if you're hiding from the world."` - **kai_voice_draft:** "If passive encounters aren't producing the two names a day, the next lever is the environment. Where do you spend time where new people show up naturally? If the answer is nowhere, that's the gap to close." - **voice_context_tags:** [newcomer, experienced, professional] - **steps:** - id: step-1-assess-current-environments kai_intent: "Map the user's recurring contexts — where they already spend time — to surface whether any naturally produce new contacts; diagnose the gap before prescribing a new environment." - id: step-2-identify-one-genuine-interest-context kai_intent: "Surface one environment the user has authentic interest in (not a strategically assigned networking venue) — the real interest is what makes attendance self-sustaining." - id: step-3-commit-to-recurring-attendance kai_intent: "Lock in a specific, recurring time commitment for the chosen context — not a one-time visit; the encounter pipeline requires reliable frequency." - id: step-4-feed-encounters-into-list-loop kai_intent: "Connect this loop back to L-01-03: every new person met in the chosen context becomes a two-name candidate for the next daily add session." - **linked_transitions_to:** [S-list-builder] - **linked_backed_by:** [P-01-03] - **linked_precedes:** [L-01-05] - **linked_edifies:** [] - **notes:** Critical that the chosen environment matches an actual interest of the user — Kai must resist the temptation to assign a "good networking venue" generically. Worre explicitly frames this as "have some fun" — the interest is the engine. --- ## L-01-05 - **title:** Connection-first encounter — meet without pitching - **body:** A recurring micro-loop fired whenever a new person enters the user's orbit (introduction, conversation, online connection). The user records the contact and starts a low-pressure relationship — staying in touch, finding common ground, becoming a friend first — without pitching the opportunity at the encounter point. Kai's role is to head off the impulse to convert immediately, which is the highest-frequency anti-pattern at this stage. The outcome is a contact who will be available for an opportunity invitation at a later time when relationship has been established. - **source_ref:** `ch.01 p.32 para.20 | "Just add them to your list, make friends, develop a connection, and when the time is right you can help them understand what you have to offer."` - **kai_voice_draft:** "When you meet someone new, the first move is the connection — not the pitch. Add them to the list, find one reason to stay in touch, and let the conversation about the business come later when you've earned a hearing." - **voice_context_tags:** [newcomer, cold-market, experienced, professional] - **steps:** - id: step-1-record-contact kai_intent: "Ensure the new contact lands on the list immediately — before the encounter fades from memory and before any pitch impulse fires." - id: step-2-find-light-stay-in-touch-reason kai_intent: "Identify one low-pressure, genuine reason to follow up with the contact — grounded in something real from the conversation, not a business pretext." script_ref: Sc-01-01 - id: step-3-let-relationship-develop kai_intent: "Hold the connection-first line over subsequent touchpoints — interrupt any early pitch impulse and redirect to relationship-building until trust is established." - id: step-4-revisit-at-right-time kai_intent: "Signal when the relationship is ready for an invitation conversation — this step's trigger belongs to ch.02 (Inviting); Kai's role here is to keep the contact warm and available." - **linked_transitions_to:** [S-list-builder] - **linked_backed_by:** [P-01-04] - **linked_precedes:** [] - **linked_edifies:** [] - **notes:** This is the chapter's hand-off into ch.02. The "right time" decision (when to invite) is the next chapter's territory. --- # principles ## P-01-01 - **title:** Prospecting is a developed skill, not a fixed asset - **body:** The size and quality of the user's prospect base is a function of practice, not a precondition for entry. Operators who believe their starting network determines their ceiling treat the business as a lottery they bought into; operators who recognise prospecting as a skill treat the network as something they build, the same way any professional builds a client base over time. - **source_ref:** `ch.01 p.29 para.7 | "It never occurred to me that finding quality people to prospect was a skill. I always viewed 'the list' as the ticket to wealth."` - **kai_voice_draft:** "The list isn't a ticket you either have or don't have — it's something you build. Operators who treat it as something they're stuck with end up stuck. Operators who treat it as a skill end up with a list big enough that the question of running out stops coming up." - **voice_context_tags:** [newcomer, experienced, professional] - **linked_corrects:** [AP-01-01, AP-01-03] - **linked_depends_on:** [P-00-01, P-00-02] - **notes:** Direct operationalisation of P-00-01 (skills not luck) and P-00-02 (deliberate practice) into the prospecting domain. Cross-chapter depends_on edges record this. --- ## P-01-02 - **title:** Capture without filter — completeness beats judgement at list time - **body:** During list capture, every name belongs on the list regardless of the user's prediction about whether the person would say yes. Pre-disqualifying during capture confuses two different jobs — collecting and qualifying — and consistently produces too-small lists, because the user's judgement about who is and isn't a fit is unreliable and self-narrowing. - **source_ref:** `ch.01 p.30 para.11 | "It doesn't matter if you think they are a prospect or not. Your database will be one of your most important assets. Everyone goes on the list."` - **kai_voice_draft:** "When you build the list, the rule is everyone goes on it. The reflex to leave someone off because you've decided they wouldn't be interested — that's a different job from capturing names, and doing both at once shrinks the list every time." - **voice_context_tags:** [newcomer, onboarding] - **linked_corrects:** [AP-01-02] - **linked_depends_on:** [] - **notes:** Light pairing with P-01-01 — they reinforce each other but the directionality is sideways, not vertical. Not encoded as depends_on. --- ## P-01-03 - **title:** Awareness is the lever — most new contacts are already in the user's day - **body:** The difference between an operator who adds two names a day and one who adds zero is almost never the number of people they actually encounter — it is whether they notice the encounter as contact-relevant. Most users walk past several add-able contacts per day; raising the awareness habit is what converts those passive encounters into list growth without requiring the user to enter unnatural social situations. - **source_ref:** `ch.01 p.31 para.18-19 | "Professionals develop a higher level of awareness. They pay attention to the world. They know they will be introduced to new people all the time."` - **kai_voice_draft:** "When you tell me 'I didn't meet anyone today', most of the time that's an awareness gap, not a contact gap. People crossed your path. The work is on noticing — not on engineering more encounters." - **voice_context_tags:** [newcomer, experienced, professional] - **linked_corrects:** [AP-01-05] - **linked_depends_on:** [P-01-01] - **notes:** Operational principle that backs L-01-03 (daily add). The "awareness gap not contact gap" framing is the Kai diagnostic line Maks will likely care about. --- ## P-01-04 - **title:** Connection precedes pitch — earn the hearing before delivering the message - **body:** When meeting a new contact, the first work is the relationship — staying in touch, finding common ground, becoming a known and trusted presence — not delivering the opportunity. Pitching at the moment of introduction signals that the relationship is instrumental — a poor opening for what could become real. - **source_ref:** `ch.01 p.32 para.20 | "Just add them to your list, make friends, develop a connection, and when the time is right you can help them understand what you have to offer."` - **kai_voice_draft:** "The connection is what earns you a hearing later. If the first move on a new contact is a pitch, you're trading a relationship that might have produced something real for a quick no. The order matters." - **voice_context_tags:** [newcomer, experienced, professional, cold-market] - **linked_corrects:** [AP-01-04] - **linked_depends_on:** [] - **notes:** This principle sets up ch.02 (Inviting) — the question of *when* the right time is becomes that chapter's territory. For ch.01 the principle is simply "not now, not at first meeting". --- # anti_patterns ## AP-01-01 - **title:** Mental short-list — the poser mentality - **body:** The operator builds the entire prospecting effort around a handful of names held in their head — three, four, maybe five people they hope will say yes. The business has no surface area beyond that short list. If one of the names signs up, the operator gets a brief stretch of activity; if none do, the operator usually exits. The short list is not a list; it is a wish. - **source_ref:** `ch.01 p.29 para.3 | "the posers make a mental list of three, four, or five people they hope will join their business"` - **kai_voice_draft:** "The mental short-list of three or four people is the most common starting posture. It's not really a list — it's a wager that one of those people will say yes. When they don't, there's nowhere to go." - **voice_context_tags:** [newcomer, onboarding] - **trigger_pattern:** New operator joins, defaults to thinking of the few obvious names without ever writing anything down, and treats those names as the universe of the business. - **cost:** Business has no resilience beyond the short list; user usually exits within weeks of the short list converting at zero. - **notes:** This is the operational form of AP-00-03 (lottery-ticket) inside the prospecting domain. Worre cites this as ~80% of new distributors — the highest-frequency anti-pattern in the early funnel. --- ## AP-01-02 - **title:** Pre-disqualifying contacts at capture time - **body:** During list capture, the operator filters names by their prediction of how the contact would respond — leaving off people they assume are "not a fit", people who said they were not interested in something else years ago, people in age bands they have decided are wrong, people they personally dislike. The filtering feels prudent but it confuses capture with qualification, and the user's predictive accuracy at this stage is poor — the list ends up systematically too small. - **source_ref:** `ch.01 p.30 para.11 | "If they are negative, put them on your list. If you hate them, put them on your list. If they're 98 years old, put them on your list."` - **kai_voice_draft:** "The temptation to leave someone off because you've decided they wouldn't be interested — that's a different job from capturing names. Doing both at once shrinks the list, every time, and the names you leave off are often the ones who would have surprised you." - **voice_context_tags:** [newcomer, onboarding] - **trigger_pattern:** During list-build, the operator pauses on a name and silently decides "they wouldn't be interested" without writing it down — then moves to the next name. - **cost:** Lists end at the dozens or low hundreds when they should be at the high hundreds; the operator's later anxiety about running out of names is structurally locked in by the filter applied at this stage. - **notes:** Direct pair with P-01-02. Catches the impulse Worre explicitly enumerates ("if you hate them...", "if they're 98 years old...", "if they're 18 years old...") — each case in the source is a flag for a different sub-instance of this anti-pattern. --- ## AP-01-03 - **title:** Static-list operation — no inflow habit - **body:** The operator has a written list but treats it as a closed universe. Each prospecting contact subtracts from the list; nothing flows in to replace it. As unworked names dwindle, the operator's anxiety rises and they either avoid prospecting (to preserve remaining names) or rush the remaining contacts (afraid of running out). Either failure mode produces worse outcomes than the list size alone would have predicted. - **source_ref:** `ch.01 p.29 para.5 | "They begin prospecting, and their list begins to diminish. As it grows smaller and smaller, their anxiety level grows higher and higher."` - **kai_voice_draft:** "When the list only shrinks, the pressure on every remaining name goes up — and that pressure is detectable by the people on the receiving end. The fix isn't to be braver with the names you have left. The fix is to make sure new names are coming in." - **voice_context_tags:** [newcomer, experienced, professional] - **trigger_pattern:** The operator focuses entirely on working the existing list and does not have a daily habit for adding to it; as the list shortens, the focus tightens further, locking out the inflow that would relieve the pressure. - **cost:** Self-reinforcing scarcity loop — list shrinks, anxiety rises, quality of contact drops, conversion drops, anxiety rises further. Often ends in operator exit. - **notes:** Operational pair with AP-00-01 (angle-seeking) — the static-list operator under pressure often pivots to angle-seeking as a relief move. Cross-chapter linkage worth noting in pre-flight for ch.04 (Following Up). --- ## AP-01-04 - **title:** Pitch-on-introduction — converting on first contact - **body:** Upon meeting a new person, the operator launches into the opportunity pitch at or near the moment of introduction. The instinct is to be efficient — get the information in front of them while they are in front of you — but the effect is to signal that the relationship is being treated as a transaction rather than a connection, and the source is explicit that this is a mistake. - **source_ref:** `ch.01 p.32 para.20 | "I'm NOT saying you should assault these people with your pitch the moment you are introduced. Some people in Network Marketing make that mistake and it's not good."` - **kai_voice_draft:** "The instinct to deliver the pitch the moment you meet someone is the move that costs you the most contacts. The person reads it the same way you'd read it if a stranger did it to you. Once that signal lands, the door is usually closed." - **voice_context_tags:** [newcomer, cold-market, experienced] - **trigger_pattern:** The operator is under scarcity pressure (often from being in S-running-low-on-names), meets a new person, and reaches for the pitch as a way to maximise the encounter. - **cost:** Contact is burned; relationship that could have produced an invitation later produces a firm no immediately. Repeated instances erode the operator's standing in their own social circle. - **notes:** Worre explicitly flags this as a common mistake. The S-running-low-on-names → AP-01-04 vulnerable_to edge is the single most actionable risk-detection moment in the chapter. --- ## AP-01-05 - **title:** Contact-blindness — feeling there is no one to talk to - **body:** The operator reports having no one to add to their list, not because their social environment is genuinely empty but because they are filtering every person they encounter before the name reaches paper. People who are "too busy", "already in something", "wrong age", "not the type" — all get screened out mentally before the list-capture step ever fires. The result is a user who is surrounded by contacts and perceives a void. - **source_ref:** `ch.01 p.31 para.18 | "Posers and amateurs don't even notice. They just go through their day saying, 'What people? I don't see any people.'"` - **kai_voice_draft:** "When someone tells me they have no one to add, that's almost always a filter problem, not a contact problem. Let's look at what you're filtering out, before we look at who's missing." - **voice_context_tags:** [newcomer, low-awareness, diagnostic] - **trigger_pattern:** User says "I don't have anyone to add" or "I don't know anyone" while in a normal social environment with contactable people passing through their day. - **cost:** Ungrown list means no prospect pipeline; the subjective perception of an empty network is treated as objective reality, blocking the awareness-raising work that would resolve it. - **notes:** Distinct from AP-01-03 (static-list / no inflow habit) which is structural — AP-01-03 is about someone who has a list but adds nothing new; AP-01-05 is about perceptual blindness that prevents the list from even starting. Added per Dmitry ruling on Flag 1. --- # scripts ## Sc-01-01 - **title:** Connection-first move on a new contact (Step 4 — networking on purpose) - **body:** When the user encounters a new person in a networking-on-purpose context (gym, hobby, volunteer, community), the move is not to introduce the opportunity. It is to record the contact and find a single light reason to stay in touch — a shared interest the user actually has, a follow-up on what the person mentioned, a small piece of useful information the user can send later. The voicing below is what the user could naturally say in the moment after the conversation has reached a natural pause; it does not reference the business and does not require a "next step" be agreed. - **source_ref:** `ch.01 p.32 para.20 | "Just add them to your list, make friends, develop a connection, and when the time is right you can help them understand what you have to offer."` - **kai_voice_draft:** "After you've had the conversation, the line is something like: 'It was good talking — what's the best way to stay in touch? I'll send you that article we mentioned.' That's it. No pitch, no setup. The follow-up sends the article. The next conversation happens later." - **voice_context_tags:** [newcomer, cold-market, experienced] - **situation:** User has just had an initial conversation with a new contact in a networking-on-purpose environment; they want a way to leave the door open without pitching the business. - **language:** en - **requires_variants:** [kr, jp, ru, vn] - **linked_backed_by:** [P-01-04] - **linked_implements_step:** [L-01-05.step-2-find-light-stay-in-touch-reason] - **linked_paraphrase_of:** [] - **linked_edifies:** [] - **notes:** Deliberately operational and minimal — Worre does not script this exchange in the book. The structural beats are ours (conversation → ask for contact preference → name a light pretext for follow-up → execute follow-up later). This is the only script ch.01 needs; ch.02 (Inviting) is where dialogue scripts proliferate. --- # dialogues ## D-01-01 - **title:** First list-dump session with a hesitant newcomer (covers AP-01-02 pre-disqualification mid-capture and AP-01-05 contact-blindness opener) - **covers_loop:** L-01-01 - **covers_anti_patterns:** [AP-01-02, AP-01-05] - **voice_context_tags:** [newcomer, warm-market, onboarding] - **uses_scripts:** [] - **source_ref:** `ch.01 p.30 para.11 | "Step one: Make your list as comprehensive as possible. Include every person you can think of. EVERY person."` - **turns:** - speaker: kai text: "OK. Today's job is one thing — write down every name you can think of. Not pitch them, not call them, not decide who would say yes. Just names on paper. Got it?" rationale: "Frame the session breadth-not-quality before any name lands; remove pre-judging instinct at the open. Newcomer shift: one concrete action, imperative, end-turn confirmation beat." tag: "L-01-01.step-1-set-capture-context" - speaker: user text: "Honestly I don't even know who I'd write down. I don't really know anyone." - speaker: kai text: "That feeling is the most common opener in this work — and almost always it's the wrong read. You pass 30+ people in a normal week. The question right now isn't 'who do I know' — it's 'whose name can I put on a page in the next 20 minutes'. Start with family. Write 5 family names. Then we keep going. Понятно?" rationale: "Correct the contact-blindness reframe — perceived emptiness is filtering, not absence. Newcomer shift: imperative ('write 5'), concrete number, end-turn confirmation. References P-01-03 awareness lever." tag: "corrects:AP-01-05" - speaker: user text: "OK, family — my mom, my brother, my cousin, my aunt, my uncle. That's 5. But like, my brother would never go for this kind of thing." - speaker: kai text: "Stop. Don't decide. Your brother goes on the list. Today's job is putting names on paper — deciding who's a fit is a completely different job and it happens later. If you do both at once, the list shrinks every time. Brother stays. Now: 5 friends. Go." rationale: "Hold the no-filter line in real time — user just demonstrated AP-01-02 mid-capture. Newcomer shift: imperative ('stop', 'go'), repetition of the key action ('don't decide'), counter-example ('shrinks every time')." tag: "corrects:AP-01-02" - speaker: user text: "Mike, Sasha, Jen, Pavel, and my buddy from school Dima. 5 friends." - speaker: kai text: "Good. That's 10. Now widen — coworkers, gym, neighbours, parents of your kid's friends, the guy who cuts your hair, anyone you've texted in the past month. No editing. Target tonight is 50 names on the page. Whatever you don't finish today, finish tomorrow. Понятно?" rationale: "Move to second-degree breadth — surface non-obvious contact pools the user typically doesn't associate with the prospecting frame. Newcomer shift: concrete number target (50), imperative ('no editing'), end-turn confirmation." tag: "L-01-01.step-3-surface-second-order-via-each-name" - speaker: user text: "OK 50 tonight. Got it." - speaker: kai text: "One more thing before you start. The list is not a finished thing once you hit 50. It grows every day from now on. Today is just the foundation. Don't treat tonight's list as the universe of the business. Понятно?" rationale: "Pre-empt the static-list trap (AP-01-03) at the close of L-01-01 — frame the artifact as living from minute one. Newcomer shift: concrete (not the universe), imperative reframe, end-turn confirmation." tag: "L-01-01.step-4-record-list-as-living-document" - **notes:** Reviewer-fill (Roma). --- ## D-01-02 - **title:** Second-degree expansion walk — pulling contacts-of-contacts onto the list - **covers_loop:** L-01-02 - **covers_anti_patterns:** [] - **voice_context_tags:** [newcomer, onboarding] - **uses_scripts:** [] - **source_ref:** `ch.01 p.31 para.14 | "Step two is looking at your list and thinking about the people they know—the second degree of separation. Chances are, you'll know most of them also."` - **turns:** - speaker: kai text: "Yesterday you got 62 names on the page. Good. Today we walk the list — one name at a time — and for each one ask 'who do they know'. Most of the people who come up, you already know. The list usually doubles. Ready?" rationale: "Open the expansion pass with concrete framing of yesterday's count and what today produces. Newcomer shift: concrete number, imperative ('we walk', 'one at a time'), expectation set." tag: "L-01-02.step-1-pick-name-from-list" - speaker: user text: "OK. First name on my list is my brother." - speaker: kai text: "Brother. Who's in his circle? His wife, his kids' parents at school, his coworkers, his gym buddies. Name them. One at a time. Don't think about whether they'd be interested. Just names." rationale: "Surface the brother's circle systematically across the natural buckets (family / school / work / hobby) — hold the no-filter rule from L-01-01." tag: "L-01-02.step-2-surface-their-circle" - speaker: user text: "His wife is Anna. Their kid's friends — I know two of the moms, Olya and Katya. He works with Sergei and another guy whose name I forget. Gym I have no idea." - speaker: kai text: "Anna, Olya, Katya, Sergei — 4 more names. Add them to the list right now. The other guy at his work — write '' and you'll fill in the name when your brother mentions him. Don't skip the placeholder. Add the 4, then read me the next name on yesterday's list." rationale: "Land the surfaced names on paper immediately — don't lose them between turns. Newcomer shift: imperative ('add right now'), concrete (placeholder convention), forward-momentum ('then read me the next')." tag: "L-01-02.step-3-add-known-second-degree-to-list" - speaker: user text: "Added. Next name is Mike." - speaker: kai text: "Mike. Same drill. His wife, his work, his hobbies, his family. Who do you already know in his circle? Don't think who would be a fit. Just names." rationale: "Iterate the same pass on the next name — the discipline is the loop. Newcomer shift: repetition of the key action ('don't think who'd be a fit, just names')." tag: "L-01-02.step-4-iterate-through-list" - speaker: user text: "His wife Lena. His mom — I've met her. His brother who works at the bank. That's 3." - speaker: kai text: "Good. Add them. We keep going one name at a time until the whole list is walked. Don't try to do this in one sitting — break it into two evenings if it's 60+ names. Target end of week: list at 120. Понятно?" rationale: "Close the dialogue with the operational rhythm — sustainable pace + concrete weekly target. Newcomer shift: concrete number (120), imperative ('break it into two'), end-turn confirmation." tag: "L-01-02.step-4-iterate-through-list" - **notes:** Reviewer-fill (Roma). --- ## D-01-03 - **title:** Daily check-in — user reports zero new names yesterday (covers AP-01-03 no-inflow habit) - **covers_loop:** L-01-03 - **covers_anti_patterns:** [AP-01-03] - **voice_context_tags:** [newcomer, onboarding] - **uses_scripts:** [] - **source_ref:** `ch.01 p.31 para.16 | "Step three: Constantly expand your list. This is why the professionals call this an 'Active Candidate List.' It never stops growing."` - **turns:** - speaker: kai text: "Check-in time. Two names a day, six days a week. Who landed on your list yesterday?" rationale: "Open the daily cadence check — anchor the user on the concrete count target before they explain. Newcomer shift: imperative open, concrete numbers (2/day, 6/week)." tag: "L-01-03.step-1-prompt-yesterday-recall" - speaker: user text: "Nobody. Yesterday was just gym, work, home. Nothing happened." - speaker: kai text: "Hold on. Walk me through yesterday. You went to the gym — who was there? Same trainer? Same people on the floor? Anyone you exchanged words with at the counter?" rationale: "Push back on the zero-add report — treat it as an awareness gap to diagnose, not a fact. References P-01-03. Newcomer shift: imperative ('walk me through'), concrete probe (which venue, what specifically)." tag: "L-01-03.step-2-name-two-new-contacts" - speaker: user text: "Trainer is the same guy. There was someone new on the floor — guy maybe my age, we said hi at the water cooler. I don't know his name." - speaker: kai text: "There's one. Write 'gym guy, ~my age, water cooler hi, [day]'. That's a name on the list — the actual name fills in next time you see him. Don't skip it because you don't know his name yet. Now: at work yesterday, who came through that wasn't your daily crew?" rationale: "Land the gym contact immediately with placeholder convention; reinforce that the perceived 'nobody' is filtering. Newcomer shift: imperative ('write', 'don't skip'), concrete (the exact line to write), repetition of the key action ('on the list')." tag: "L-01-03.step-3-record-with-light-context" - speaker: user text: "Actually there was a new contractor in our open-plan area, I said hi but that's it. And a courier guy." - speaker: kai text: "Two more. Add both. 'contractor, [team], [day], said hi' and 'courier from [company], [day]'. That's three names from a day you called 'nothing'. The job isn't to remember encounters at the end of the day — the job is to notice them as they happen. Pull out your phone, log the name. Понятно?" rationale: "Reinforce P-01-03 with the diagnostic outcome — 3 names recovered from a 'nothing' day. Anti-pattern correction is in the surfacing itself. Newcomer shift: concrete (the exact line format), imperative ('pull out your phone, log'), counter-example ('a day you called nothing' produced 3)." tag: "corrects:AP-01-03" - speaker: user text: "OK I get it. So I should be logging during the day not at night." - speaker: kai text: "Exactly. Log on the spot, even if it's just a placeholder. Tonight before bed — read back today's adds. If it's under 2, walk the day again with me tomorrow. Streak so far: yesterday counts as a 3, day before that was a 2. Two days in a row. Keep it going." rationale: "Close with the cadence habit (log on the spot) + streak naming — the consistency is the mechanism, not any single day. Newcomer shift: imperative ('log on the spot'), concrete (counts as 3, two in a row), end-turn forward-momentum." tag: "L-01-03.step-4-confirm-cadence-streak" - **notes:** Reviewer-fill (Roma). --- ## D-01-04 - **title:** Picking a network-on-purpose context for a work-from-home user - **covers_loop:** L-01-04 - **covers_anti_patterns:** [] - **voice_context_tags:** [newcomer, experienced, professional] - **uses_scripts:** [] - **source_ref:** `ch.01 p.32 para.21 | "Step four: Network on purpose. Professionals network on purpose. It's hard to meet new people if you're hiding from the world."` - **turns:** - speaker: kai text: "Daily-add cadence is holding for two weeks. Good. The 2/day target is being hit but only just — you're scraping. Time to add an environment where new people show up naturally. Walk me through your week. Where do you spend recurring time outside the house?" rationale: "Diagnose before prescribing — map current environments before assigning a new one. Newcomer shift: concrete framing of where they are now (scraping), imperative ('walk me through')." tag: "L-01-04.step-1-assess-current-environments" - speaker: user text: "Honestly not much. I work from home. Gym 3 times a week, school pickup for the kids, grocery store. That's it." - speaker: kai text: "OK. Gym and school pickup already feed the list — they're producing the scrape-by names. We need one more context. Question: what did you used to do for fun before this got busy? A hobby you stopped, a class you wanted to take. Don't say 'networking' — say something you actually want to do." rationale: "Surface a context grounded in genuine interest — the engine is the interest, not the strategic value of the venue. Newcomer shift: imperative ('don't say networking'), concrete ('something you actually want to do')." tag: "L-01-04.step-2-identify-one-genuine-interest-context" - speaker: user text: "I always wanted to do something with my hands. Woodworking maybe. There's a community workshop near me that does evening classes." - speaker: kai text: "Woodworking class — real interest, recurring time, room full of strangers. That's the lever. Sign up for the next session this week. Not 'think about it' — sign up. Block the evening on your calendar so it's not negotiable. Once you're going every week, the list-add naturally produces 1-2 names from that context alone. Понятно?" rationale: "Lock in the recurring commitment — one-time visits don't produce a contact pipeline. Newcomer shift: imperative ('sign up', 'block the evening'), repetition of the key action ('not think about it — sign up'), concrete ('this week'), end-turn confirmation." tag: "L-01-04.step-3-commit-to-recurring-attendance" - speaker: user text: "OK I'll sign up tonight." - speaker: kai text: "Good. One more piece — when you're at class, no pitch, no business talk. You're there to learn woodworking and meet people. Names go on the list at home that night with one line of context. The class person becomes a connection over weeks, not in week one. If you go in pitching, the room closes within a session. Понятно?" rationale: "Pre-empt AP-01-04 (pitch-on-introduction) in advance — the class is a connection context, not a venue to convert. Newcomer shift: imperative ('no pitch'), concrete ('one line of context'), counter-example ('the room closes'), end-turn confirmation." tag: "L-01-04.step-4-feed-encounters-into-list-loop" - **notes:** Reviewer-fill (Roma). --- ## D-01-05 - **title:** Stopping a user from pitching at the moment of introduction (covers AP-01-04 pitch-on-introduction) - **covers_loop:** L-01-05 - **covers_anti_patterns:** [AP-01-04] - **voice_context_tags:** [newcomer, cold-market] - **uses_scripts:** [Sc-01-01] - **source_ref:** `ch.01 p.32 para.20 | "Just add them to your list, make friends, develop a connection, and when the time is right you can help them understand what you have to offer."` - **turns:** - speaker: user text: "I met someone at the woodworking class yesterday. Really interesting guy, runs his own business, would be perfect for this. How do I bring it up next class?" - speaker: kai text: "Stop. Next class you don't bring it up. The first move on a new contact is the connection — not the pitch. Pitching at week one closes the door, almost every time. Add him to the list with one line of context — 'woodworking class, [his name], runs [his business], [day we talked]'. That's the move this week. Понятно?" rationale: "Head off AP-01-04 directly — the user just signalled the instinct, the correction lands immediately. References P-01-04. Newcomer shift: imperative ('stop', 'don't bring it up'), counter-example ('closes the door, almost every time'), concrete (the exact line format), end-turn confirmation." tag: "corrects:AP-01-04" - speaker: user text: "But what do I even say to him next week then? Just 'hi' again?" - speaker: kai text: "No. You ask him about something real from your last conversation. He mentioned his business — ask how it's going. He mentioned a project — ask how it landed. The opening question references something he actually said. That's how a connection starts. Two or three classes of real conversation and he'll know you're a person, not a pitch." rationale: "Give the user a concrete conversational anchor — 'reference what he actually said' is the operational version of the connection-first move. Newcomer shift: imperative ('you ask'), concrete (specific examples — business, project), counter-example ('not a pitch')." tag: "L-01-05.step-2-find-light-stay-in-touch-reason" - speaker: user text: "OK. And how do I get his number or something so I can stay in touch outside class?" - speaker: kai text: "End of next class, when the conversation's at a natural pause, line is something like: 'It was good talking — what's the best way to stay in touch? I'll send you that article we mentioned.' That's it. No pitch, no setup. Then you actually send the article that week. The follow-up sends the article. The next conversation happens later." rationale: "Deliver Sc-01-01 verbatim — embed the canon script into the dialogue. Newcomer shift: concrete (exact line), imperative ('then you actually send'), repetition of the action sequence." tag: "applies-script:Sc-01-01" - speaker: user text: "And when do I actually bring up the business?" - speaker: kai text: "Not for at least a month. Maybe longer. You're building a real relationship — the business comes up when there's enough connection that it's a natural thing to mention, not a sales move. We'll know when the time is right by what he's saying — and we'll cover that in the next skill. For now: connection, follow-up, repeat. Понятно?" rationale: "Hold the connection-first line over the timeline horizon — explicitly defer the invitation question to ch.02. Newcomer shift: concrete time ('at least a month'), imperative summary ('connection, follow-up, repeat'), end-turn confirmation. Forward-reference to ch.02 is intentional." tag: "L-01-05.step-4-revisit-at-right-time" - **notes:** Reviewer-fill (Roma). This dialogue forward-references ch.02 (the 'when is the right time' question) — that handoff is the chapter's intended close. --- # gap_list - [ch.01 p.29 para.1] restatement-of-P-01-01: Opening "Do I know anybody?" framing — source-illustration for the principle that the network is a built skill, not a fixed asset. - [ch.01 p.29 para.2] restatement-of-AP-01-01: Recalls the poser/amateur/professional taxonomy (from ch.02/03 in the book); the poser taxon is the primary content recalled and AP-01-01 is its in-domain operationalisation. - [ch.01 p.29 para.3] restatement-of-AP-01-01: Source-illustration for the mental short-list anti-pattern. - [ch.01 p.29 para.4] restatement-of-AP-01-01: The 80% figure — operational statistic emphasising AP-01-01 frequency. Treated as restatement because the substantive framework content is AP-01-01 itself; the figure is illustration. - [ch.01 p.29 para.5] restatement-of-S-running-low-on-names: Source-illustration for the amateur-state shrinking-list anxiety dynamic. - [ch.01 p.29 para.6] anecdote: Worre's early-20s personal story about running out of his parents' contacts. Pure personal narrative. - [ch.01 p.29 para.7] restatement-of-P-01-01: Worre's "defining moment" reframe — source-illustration for the prospecting-is-a-skill principle (also tagged as source_ref on S-skill-committed carry-through). - [ch.01 p.30 para.8] restatement-of-P-01-01: Description of how professionals approached prospecting differently — restates the skill-not-luck framing in the operational domain. - [ch.01 p.30 para.9] restatement-of-S-list-builder: Introduces the "Active Candidate List" concept — source-illustration for the target state. - [ch.01 p.30 para.10] restatement-of-L-01-03: The "never stop adding" commitment — source-illustration for the daily-add loop. - [ch.01 p.30 para.10b] anecdote: Harvey Mackay personal story (father's advice at 18; 12,000 friends over 60 years). Illustrative example, no new framework content beyond what L-01-03 / P-01-03 already capture. - [ch.01 p.30 para.11] restatement-of-L-01-01: Step one instruction — source-illustration for the comprehensive-dump loop. - [ch.01 p.30 para.11b] restatement-of-AP-01-02: The enumerated cases ("if you hate them", "if they're 98 years old") — source-illustration for the pre-disqualifying anti-pattern. - [ch.01 p.30 para.12] restatement-of-L-01-01: "Empty your mind out on paper" — source-illustration for L-01-01.step-3 (surface second-order via each name). - [ch.01 p.30 para.13] restatement-of-P-01-02: "You're not required to prospect everyone on your list" — author clarifies that list-capture and prospecting work are separate jobs; the closing sentence ("it's extremely important to do the work to truly capture your network on paper") restates the P-01-02 scope. - [ch.01 p.31 para.14] restatement-of-L-01-02: Step two instruction — source-illustration for the second-degree expansion loop. - [ch.01 p.31 para.15] restatement-of-L-01-02: Concrete iteration ("think about family", "think about friends") — source-illustration for L-01-02.step-2 / step-3. - [ch.01 p.31 para.16] restatement-of-L-01-03: Step three instruction — source-illustration for the daily-add loop. - [ch.01 p.31 para.17] anecdote: Jordan Adler personal story (master of step three, seven-figure earner). Illustrative example, no new framework content. - [ch.01 p.31 para.18] restatement-of-P-01-03: "Professionals develop a higher level of awareness" — source-illustration for the awareness principle. - [ch.01 p.31 para.19] restatement-of-L-01-03: The 2/day × 6 days × 5 years = 3000 math — source-illustration for why the daily-add cadence compounds (operational reinforcement of L-01-03's design intent). - [ch.01 p.32 para.20] restatement-of-AP-01-04: The "assault" warning — source-illustration for the pitch-on-introduction anti-pattern. (Also source_ref for P-01-04 and Sc-01-01; same paragraph carries both principle and counter-pattern, which is consistent with the IP-clean rule — different artifacts can legitimately share a source paragraph.) - [ch.01 p.32 para.21] restatement-of-L-01-04: Step four instruction — source-illustration for the network-on-purpose loop. --- # validation_scenarios ### Scenario 1: Newly committed user starts the list from scratch 1. User in state `S-skill-committed`. Reports they have made the decision to treat the business as a profession and asks Kai what to do first. 2. Kai opens by routing the user into `L-01-01` (comprehensive list dump), naming today's job as breadth not quality. 3. User reports: "OK — but a lot of the people I'm thinking of would never go for something like this." 4. Kai surfaces `AP-01-02` (pre-disqualifying at capture time) and grounds the reframe in `P-01-02` — every name goes on the list, the qualifying job is separate and comes later. 5. User commits to dumping every name they can think of onto paper without filter. State transitions to `S-has-static-list` after the first sitting. ### Scenario 2: User with a 100-name list reports anxiety as the list shrinks 1. User in state `S-has-static-list` and approaching `S-running-low-on-names`. Reports they have worked through most of their list and are feeling pressure as fewer unworked names remain. 2. Kai diagnoses the symptom as structural, not motivational, and grounds in `P-01-01` (prospecting is a skill not a fixed asset). 3. User reports: "I just feel like if these last names don't work, I'm done." 4. Kai surfaces `AP-01-03` (static-list operation) and routes the user into `L-01-03` (daily add-to-list) — the fix is on the inflow side, not on talking themselves out of the worry. 5. User commits to a 2/day, 6-days/week cadence. State transitions toward `S-list-builder` once the cadence holds for at least a week. ### Scenario 3: User reports zero new names in the past three days 1. User in state `S-list-builder` (early-stage — habit not yet stable). Reports they have not added any new names in three days because "no one new has shown up." 2. Kai grounds in `P-01-03` (awareness is the lever) — the gap is usually on the noticing side, not on the encounter side. 3. User reports: "I went to the gym, picked up the kids, went to the office. Nothing happened." 4. Kai walks back through the user's last 24 hours one venue at a time, surfacing the people who were present but not noticed as add-able. 5. User identifies 3-4 names that fit. They go on the list. The user's awareness habit is calibrated against today's actual encounters. State stays `S-list-builder`. ### Scenario 4: User asks where to find new contacts when their existing circles are tapped 1. User in state `S-list-builder` (or `S-running-low-on-names` with established daily habit). Reports that even with awareness raised, passive encounters are not producing two names a day. 2. Kai routes the user into `L-01-04` (network on purpose) and grounds in `P-01-03` — when passive doesn't produce enough, the next lever is the environment. 3. User reports: "I work from home and I don't really have hobbies right now." 4. Kai asks the user to name one genuine interest they have stopped acting on, and helps them identify a recurring environment (a class, a meetup, a volunteer cause) that matches the interest. 5. User commits to attending one such environment in the next two weeks. Loop returns to L-01-03 with new encounter sources flowing in. ### Scenario 5: User meets someone new and asks Kai how to introduce the business 1. User in state `S-list-builder`. Reports they met someone interesting at a community event and want to know how to bring up the business. 2. Kai surfaces `AP-01-04` (pitch-on-introduction) and grounds the reframe in `P-01-04` — the first move is connection, not pitch. 3. User reports: "But I'll lose the moment if I don't say something now." 4. Kai walks the user through `L-01-05` (connection-first encounter) and uses `Sc-01-01` to give a concrete line for ending the conversation without pitching — record the contact, name a light reason to stay in touch, execute that follow-up before the business comes up. 5. User commits to using the connection-first move. State stays `S-list-builder`; the prospect enters the list for ch.02 invitation work at the right time. ### Scenario 6: Experienced operator (mid-rank) returns after a quiet stretch 1. User in state somewhere between `S-list-builder` and a still-undefined experienced-state. Reports activity has slowed and they have not added to the list for several weeks. 2. Kai grounds the diagnostic in `P-00-03` (internal locus of control — carry-through from ch.00) and `P-01-01` — the lever is the operator's practice, not external conditions. 3. User reports: "I think my market is just saturated — everyone I know already knows." 4. Kai surfaces `AP-01-03` (static-list operation) and `AP-00-01` (angle-seeking) as the likely twin failure modes when activity slows. The reframe is to restart `L-01-03` and `L-01-04` from current actual encounters. 5. User commits to resuming the daily-add cadence and naming one networking-on-purpose context to re-enter this month. State remains pre-S-list-builder until the cadence holds again. --- # cross_chapter_links - `P-01-01` --[depends_on]--> `P-00-01` - `P-01-01` --[depends_on]--> `P-00-02` - `L-01-03` --[backed_by]--> `P-00-02` - `S-skill-committed` --[triggers]--> `L-01-01` - `S-skill-committed` --[triggers]--> `L-01-04` - `L-01-05` --[precedes]--> `L-02-XX` - `S-luck-seeker` --[vulnerable_to]--> `AP-01-01` --- # review_state **Dmitry editorial pass:** `pending` **Adversarial reviewer flags:** pending — adversarial review dispatched by controller in Phase 4. **Roma signoff (operational truth):** `pending` **Maks signoff (brand / voice):** `pending` **Locked:** `false` --- # extractor_notes 1. **Source-paragraph numbering ambiguity at sub-paragraph level.** Worre's prose occasionally runs two distinct framework beats in a single visual paragraph (e.g., p.30 para.11 contains both "make your list comprehensive" (step instruction → L-01-01) and the enumerated anti-filter examples ("if you hate them...") → AP-01-02). The protocol's paragraph identifier format `p.NN para.N` doesn't have a clean way to express sub-paragraph beats. I used `para.11` for the step instruction and `para.11b` for the enumerated cases in the gap list, but this convention isn't in `extraction.md §3` or §5. Suggested amendment: add `para.Nb`, `para.Nc` etc. as the convention for sub-paragraph beats, OR allow the same `para.N` to appear multiple times in the gap list with different `restatement-of-` tags (which is what would happen if the convention were "one entry per artifact, paragraphs can produce more than one"). For ch.01 the `para.Nb` convention reads cleanly. 2. **One paragraph as `source_ref` for multiple artifacts.** Paragraph p.32 para.20 ("Just add them to your list, make friends, develop a connection...") is the source paragraph for P-01-04 (principle), AP-01-04 (anti-pattern — the paired "assault" framing in the same paragraph), Sc-01-01 (script), and L-01-05 (loop). Four artifacts share the same source paragraph, which is permissible under the IP-clean rule (each artifact's `source_ref` quotes a different ≤30-word slice of the paragraph) but the gap list entry resolution chose `restatement-of-AP-01-04` somewhat arbitrarily — could equally have been any of the four. The precedence rule in `extraction.md §5` doesn't address this case (it addresses single-artifact restatement vs recap, not multi-artifact restatement). Suggested amendment: when a paragraph is source for multiple artifacts of different types, prefer the anti-pattern over the principle in the gap-list tag (because the anti-pattern is the action-relevant artifact for the audit reader). For ch.01 I followed that heuristic; flagging as a candidate codification. 3. **The "step" naming inside loops became its own micro-decision.** The loop `steps:` list serves two jobs: (a) make the loop's behavioural structure auditable, (b) provide step-id targets for `script.linked_implements_step` edges. For loops with no scripts attached (L-01-01 through L-01-04 in ch.01), the steps are pure structural skeleton — they don't have to be highly resolved. For L-01-05 which has Sc-01-01 attached, step-2 had to be named precisely enough that the script's `linked_implements_step` could point cleanly. The template doesn't say which job is primary. For ch.01 I treated the steps as auditable structure first and named them clearly enough for any future script to attach. Suggested amendment to template: a sentence noting "steps double as audit structure and script attachment points — name them at the resolution required by whichever role is active". 4. **Validation-scenario node-id density.** The spec asks for 5-10 scenarios per chapter. Each scenario tends to reference 3-5 node ids. Across 6 scenarios the chapter's nodes get referenced multiple times each, which is good for validator walkthrough — but it also means an unresolved schema-error in one node id propagates to every scenario it touches. Post-flight (Phase 6) should explicitly run a "every node id referenced in `# validation_scenarios` exists in this chapter or in a locked prior chapter" check. The current Phase 6 checklist item 2 (edges reference existing nodes) covers `linked_*` fields but not free-text node references in scenarios. Suggested amendment: extend Phase 6 item 2 to include scenario-text id references.