Review — ignaciocarcavallo

All 7 required sections present in system.md: Identity, Voice, Flow, Calibration, Principles, Tools, NO_RESPONSE. Content matches principles template specification.

15 examples provided. All 7 base scenarios covered: happy path (Ex 1), resource delivery (Ex 4, 6), objection handling (Ex 5), disqualification (Ex 7), emotional lead (Ex 13), re-engagement (Ex 8), off-topic (Ex 10). Both conditionals met: keyword trigger (Ex 4, 6) and price objection (Ex 5). Count is within cap.

Every example follows the 6-step flow (Calificar → Dolor → Contexto → Posicionar → Cerrar → Post-booking) in order. All examples reach terminal states (link sent, NO_RESPONSE, or booking confirmed).

System.md is internally consistent. The 25-word limit on Voice is stated once and applies uniformly. Flow steps are ordered and non-contradictory. The post-booking rule ('Solo si la respuesta es genuinamente ambigua... preguntá UNA vez') is an explicit exception to the NO_RESPONSE rule, not a contradiction. Example 1 demonstrates this carve-out correctly.

All SDK files align. Keywords.json declares send_without_permission flags that govern delivery timing; system.md's Flow step 1 ('Si el lead pregunta por un keyword... entregá el recurso primero') is consistent with keyword conditions. Examples.md demonstrates both rules coexisting (Ex 4, 6 show keyword delivery then qualification). Program.json pricing rules match system.md's Principles (no Elite/Group prices in chat; AI Brain and Hiring Course allowed). No factual contradictions on revenue bands, URLs, or program details.

All examples use consistent voice: sharp, direct, no BS, rioplatense voseo, max 25 words per message (except intro), no emojis, no em dashes. Tone is uniform across scenarios (happy path, objections, disqualification, emotional). A reader would recognize the same agent throughout.

All risky actions are guarded. Sending links is guarded by revenue band (Step 4 posicioning) and explicit lead acceptance ('dale', 'sí', 'me interesa'). NO_RESPONSE is guarded by 7 explicit conditions in Principles §7. Keyword delivery is guarded by send_without_permission flags in keywords.json. Example 1 demonstrates the guard on post-booking ambiguity ('pudiste agendar?'). No unguarded actions exist.

All examples use current flow language and CTAs. Closing language ('va + URL + cuando reserves avisame', 'bárbaro, te llega ahí el material', 'NO_RESPONSE') matches system.md's Flow and Principles. No outdated phrasing detected.

Each behavioral instruction has a single canonical home. Revenue routing lives in knowledge_base.md (not repeated in system.md). NO_RESPONSE triggers are stated once in Principles §7. Post-booking sequence is in knowledge_base.md. Keywords.json notes cross-reference the flow ('resume normal qualification flow') rather than duplicating. No instruction appears in two places.

Behavioral guidance (tone, flow, conversational style) is expressed via Voice examples and Principles. Hard rules are reserved for facts (revenue bands, pricing, URLs, eligibility). The 25-word limit is stated as a rule but is taught by Voice examples. Examples demonstrate all key behaviors (objection handling, disqualification, emotional leads) rather than prescribing them as rules.