Review — davegoldevolve

system.md contains all 7 required sections for principles template: Identity (opening paragraphs), Voice (message patterns + philosophy), Flow (5 phases: Genuine Open, Connect First, Read the Room, Natural Invite, Let It Breathe), Calibration (5 energy states with prescribed actions), Principles (5 stated principles), Tools (4 tools with triggers), and NO_RESPONSE (mandatory section with literal token). All sections match template intent.

examples.md contains 19 examples covering all 7 base scenarios (happy path: Ex 1,2,4,7,11,12,14,15; resource/link: Ex 1,2,3,4,6,7,8,9,11,12,13,14,15; objection: Ex 3; disqualification: Ex 5; emotional/sensitive: Ex 10,16; re-engagement: Ex 6; off-topic: Ex 18,19) plus two conditional scenarios (keyword trigger: Ex 1,2,4 for BLUEPRINT/EVOLVE/SCALE; price objection: Ex 3). Total count is 19, within the ≤20 cap.

Every example in examples.md follows the 5-phase flow from system.md (Genuine Open → Connect First → Read the Room → Natural Invite → Let It Breathe/Send Link) in order, and each reaches a terminal state: booking link sent, warm close with NO_RESPONSE, or conversation ends naturally. No example skips required steps or ends mid-flow.

system.md contains no self-contradictions. The 5% emoji-only rule (stated in Voice section: 'About 5% of the time, instead of a text reply, just react with an emoji') is an explicit exception with its own precondition (low-frequency, non-chasing context), not a conflicting output under the same precondition as the general voice rules. Principle 0 (never chase) and the emoji exception coexist because the exception is framed as a *response* to a lead message, not an unprompted follow-up after silence.

All SDK files agree on behavior and data. Keywords in keywords.json (BLUEPRINT, EVOLVE, SCALE, CBM, BROTHERHOOD) declare literal_response openers that align with examples.md (Ex 1, 2, 4 show keyword triggers followed by normal flow). resources.json URLs match those sent in examples.md. program.json pricing rule ('Do not quote specific prices before a call') is honored in examples.md (Ex 3 redirects price question to the call). No file contradicts another under the same precondition.

All 19 examples in examples.md use the same persona, vocabulary, and tone: casual lowercase, short messages (1-2 lines), direct questions (WDYM, what does that look like), peer energy, no corporate language, consistent use of reflective questioning (NEPQ style). No jarring tonal shifts; a reader would believe all examples are the same agent.

All risky actions in system.md's flow are guarded. Phase 4 (Natural Invite) states 'once they've had roughly 3 rapport exchanges AND you've got 3 qualifying data points, look for the first natural opening' — explicit guard. Phase 5 (Let It Breathe or Send the Link) states 'If they're warm, get a yes and send the link' — conditional guard. Calibration section provides energy-state guards (Engaged → advance; Lukewarm → one more probe; Disengaged → end warm). Multiple examples (1, 2, 4, 7, 8, 9, 11, 12, 14, 15) demonstrate the guard firing correctly before links are sent. Generic phrasing ('once they've had roughly 3 exchanges') is resolved by worked examples showing the pattern in action.

All examples in examples.md use current flow language and CTAs from system.md. Closing language ('want me to send the link?', 'want to jump on a call?', 'want to get on a Connection Call?') matches the current flow definition. No examples reference outdated flow steps or deprecated CTAs.

Each behavioral instruction has a single canonical home. The 'never chase' rule appears once in Principle 0. The NEPQ questioning style is described once in Voice section and demonstrated across examples (not restated in multiple places). The 'read the zone' guidance appears once in Principle 5 and is reinforced by Example 10 (emotional lead handling), not duplicated. No instruction is stated in two locations.

Behavioral guidance (tone, pacing, questioning style, warmth) is expressed via Voice section + 19 worked examples, not as hard rules. Hard rules are reserved for factual constraints (pricing: 'Do not quote specific prices before a call'; disqualifiers: 'Under 18'; tool usage: 'Never modify booking links'). The 5 Principles address genuine judgment calls (never chase, assume attraction, value before pressure, low-pressure CTA, read the zone) that examples alone might not fully teach. Balance is appropriate.