Review — ignaciocarcavallo

All 7 required sections (Identity, Voice, Flow, Calibration, Principles, Tools, NO_RESPONSE) are present in system.md and match the principles template specification. Content fits the template's intent.

examples.md covers all 7 base scenarios (happy path, resource/link delivery, objection handling, disqualification, emotional lead, re-engagement, off-topic) plus two conditional scenarios (keyword trigger in Example 4, price objection in Example 5). Total count is 14 examples, well under the 20-example cap.

Every example in examples.md walks the flow steps in order (qualify → pain → context → position → close → post-booking or terminal state) and reaches a terminal state (link sent, NO_RESPONSE, or course offered). No examples skip required steps or end mid-flow.

system.md contains one explicit exception that resolves potential ambiguity: the Flow section states 'Solo si la respuesta es genuinamente ambigua (un "ok"/"dale" suelto, sin contexto que indique reserva), preguntá UNA vez "pudiste agendar?"' This carve-out is documented and Example 1 demonstrates it correctly. No shared precondition produces conflicting outputs.

All SDK files agree on behavior and parameters. keywords.json declares two conditions: 'resource_with_flow' (roadmap, equipo, ceo, ops, fire, foco, testing) with send_without_permission=true, and 'contextual' (guia, aceleradora, link) with send_without_permission=false. system.md's Flow step 5 states 'Si el lead pregunta por un keyword (roadmap, guia, costos), entregá el recurso primero y después arrancá la calificación.' Example 4 (roadmap) and Example 6 (guia) both demonstrate the correct behavior: roadmap is sent immediately, guia is sent only after qualification begins. The two keyword conditions apply to different preconditions (different keywords) and coexist correctly.

All examples use the same persona, vocabulary, formality level, and rioplatense dialect. Tone is consistently sharp, direct, and professional. Message length, punctuation, and emoji usage (none) are uniform across all examples.

All risky actions in system.md's Flow are paired with inline guards. Step 4 (Posicionar) includes 'La explicación va siempre, independientemente de cómo respondió el lead' (guard: always explain). Step 5 (Cerrar) includes 'SOLO una vez que el lead aceptó la call' (guard: explicit acceptance required). Step 6 (Post-booking) includes 'Solo si la respuesta es genuinamente ambigua... preguntá UNA vez' (guard: ambiguity condition). Examples 1, 1B, 1C, 2, 4, 5, 6 all demonstrate these guards firing correctly.

All example CTAs and closing language match the current flow definition in system.md. Post-booking messages ('bárbaro, te llega ahí el material'), link delivery format ('va [URL] cuando reserves avisame'), and NO_RESPONSE usage are all consistent with system.md's current language.

Each behavioral instruction has a single canonical location. The 25-word limit is stated once in Voice. The NO_RESPONSE rule is stated once in Principles (item 7). The keyword handling rule is stated once in Flow. No instruction is restated in multiple places; cross-references are minimal and appropriate.

Behavioral guidance (tone, flow, conversational style) is expressed via Voice section and examples. Hard rules are reserved for factual constraints (revenue thresholds, pricing rules, eligibility) and safety boundaries (never invent data, no diagnosis, minor disengagement). The balance is appropriate for the principles template.