Review — elartedevivir.ar

All 7 required sections for principles template are present in system.md: Identity, Voice, Flow, Calibration, Principles, Tools, and NO_RESPONSE. Each section matches the template's specification and intent.

examples.md contains 14 examples covering all 7 base scenarios (happy path, resource/link delivery, objection handling, disqualification, emotional/sensitive, re-engagement, off-topic) plus 2 conditional scenarios (keyword trigger: Example 7 'regalo'; price objection: Example 4). Total count is 14, within the ≤20 cap.

Every example in examples.md maps to the flow steps in system.md (Paso 0–4) in order and reaches a terminal state (link sent, NO_RESPONSE, or confirmed booking). No example ends mid-flow.

Paso 4 states 'Enviar link de pago en el mismo mensaje o inmediatamente despues del precio, no esperar otro turno' (timing rule for when to send the link). Principle 5 states 'Cuando el lead ya eligio modalidad y fecha, enviar el link de pago directo sin pedir permiso extra' (consent rule). These are layered policies on the same action under the same precondition (lead has chosen modalidad and fecha), but they do not produce conflicting outputs: Paso 4 governs *when* to send (immediately after price), Principle 5 governs *whether* to ask permission (no). Example 1 demonstrates both rules operating together correctly (price stated, link sent immediately after in same/next message, no extra permission requested). No shared precondition produces conflicting outputs.

All SDK files (system.md, examples.md, objections.md, keywords.json, program.json, resources.json) are internally consistent. Keywords declare their flow routing (info → router, regalo → resource_with_flow, taller → literal_response, etc.); examples demonstrate each keyword's behavior correctly. Prices in program.json match prices cited in examples.md and objections.md. No file demonstrates behavior that contradicts another file under the same precondition.

All examples use the same persona, vocabulary, formality level, and dialect. Voice is consistently casual, direct, voseo-based, minimal emojis, no periods at end of messages, max 2 sentences per message. A reader would believe all examples are the same agent.

Paso 0 explicitly states the condition ('al inicio, antes de avanzar el flujo') and the guard ('No bloqueante. Si lo da... Si no lo da, seguir el flujo normal'), making this a universal opener with a clear conditional branch. Paso 4 (send link) is guarded by 'Presentar precio segun modalidad' and 'Enviar link de pago en el mismo mensaje o inmediatamente despues del precio' — the precondition is price presentation. Principle 5 adds a guard: 'Cuando el lead ya eligio modalidad y fecha, enviar el link de pago directo sin pedir permiso extra.' Examples 1, 3, 4, 11, and 14 all demonstrate the guards firing correctly. No unguarded actions exist.

All examples use current flow language and CTAs that match system.md. Closing language ('cuando estes listo, escribime por aca', 'cuando termines, avisame') aligns with Paso 4 and Principle 4. No stale phrases from prior flow definitions detected.

Each behavioral instruction has a single canonical home. Principle 2 (no access to taller dates) is stated once in Principles and reinforced in keywords.json notes for 'taller' — the notes are a cross-reference, not a duplicate. Principle 3 (taller ≠ Parte 1) is stated once. No instruction is restated in two locations with similar prose.

Behavioral guidance (tone, flow, conversational style) is expressed via Voice section + examples. Hard rules remain for factual constraints (prices, links, eligibility, tool fallbacks). Principles focus on judgment calls (never invent info, no diagnosis, no future contact promises) rather than micro-rules. The balance is appropriate for the template.