| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 289 | 233 | +24.0% |
| Nuevas | 139 | 114 | +21.9% |
| Link sent | 0 | 0 | — |
| Calls booked | 0 | 0 | — |
| Booked/Link % | — | — | — |
| Booked/Activas % | 0.0% | 0.0% | +0.0pp |
| Booked/Nuevas % | 0.0% | 0.0% | +0.0pp |
| Revenue variable | $0.00 | $0.00 | — |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 289 | 139 | 0 | 0 | — | 0.0% | 0.0% |
| Semana anterior (7d) | 233 | 114 | 0 | 0 | — | 0.0% | 0.0% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 07-30 | 35 | 15 | 0 | 0 | — | 0.0% | 0.0% |
| 07-29 | 47 | 17 | 0 | 0 | — | 0.0% | 0.0% |
| 07-28 | 59 | 33 | 0 | 0 | — | 0.0% | 0.0% |
| 07-27 | 43 | 24 | 0 | 0 | — | 0.0% | 0.0% |
| 07-26 | 22 | 16 | 0 | 0 | — | 0.0% | 0.0% |
| 07-25 | 41 | 14 | 0 | 0 | — | 0.0% | 0.0% |
| 07-24 | 42 | 20 | 0 | 0 | — | 0.0% | 0.0% |
| 07-23 | 54 | 25 | 0 | 0 | — | 0.0% | 0.0% |
| 07-22 | 56 | 24 | 0 | 0 | — | 0.0% | 0.0% |
| 07-21 | 18 | 9 | 0 | 0 | — | 0.0% | 0.0% |
| 07-20 | 33 | 17 | 0 | 0 | — | 0.0% | 0.0% |
| 07-19 | 14 | 11 | 0 | 0 | — | 0.0% | 0.0% |
| 07-18 | 23 | 11 | 0 | 0 | — | 0.0% | 0.0% |
| 07-17 | 35 | 17 | 0 | 0 | — | 0.0% | 0.0% |
| BP | Sev | Estado | Detalle |
|---|---|---|---|
| BP-1 | HIGH | PASS | Template compliance All 7 required sections for the principles template are present in system.md: Identity (Identidad y Misión), Voice (Voz), Flow (Flujo de Conversación with 4 stages), Calibration (embedded in Flow via energy-state routing), Principles (5 principles listed), Tools (3 tools with explicit triggers), and NO_RESPONSE (mandatory section present). Content fits template intent. |
| BP-2 | MEDIUM | PASS | Example coverage and cap (7 base scenarios + conditional, ≤20 total) examples.md contains 18 examples covering all 7 base scenarios (happy path Ex1/5/6, resource/link delivery Ex3/8, objection handling Ex4/7, disqualification Ex9/10, emotional/sensitive Ex7, re-engagement N/A, off-topic N/A) plus conditional keyword-trigger examples (Ex1/14/15 show keyword 'info' + audio path). Total count is 18, within the ≤20 cap. evidence (2)
|
| BP-3 | HIGH | PASS | Examples align with the flow Every example in examples.md follows the 4-stage flow from system.md (Stage 1 Apertura → Stage 2 Welcome → Stage 3 Branching → Stage 4 Post-link/NO_RESPONSE). All examples reach a terminal state (link sent, soft close, NO_RESPONSE, or derivation to Tami/Daiana). No example ends mid-flow. evidence (1)
|
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md system.md contains no self-contradictions. The Flow section explicitly documents exception paths (Path A for audio history, gym presencial derivation, keyword intent) as named carve-outs, not contradictions. All behavioral parameters (welcome content, pricing, NO_RESPONSE triggers) are stated once and consistently applied across all stages. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files agree on behavior and data. keywords.json literal_responses (e.g., 'info' → landing link) are pre-agent auto-replies (different precondition than agent's conversational flow per dismissed false positive BP-5). system.md's Stage 1 Apertura and Stage 2 Welcome are the agent's own dialogue turns. program.json pricing ($50k ARS transfer / $60k tarjeta / $40 USD) matches examples.md and system.md. resources.json URLs match inline links in system.md and examples.md. No file contradicts another under the same precondition. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All 18 examples use consistent voice: warm, direct, voseo rioplatense, minimal punctuation (commas/periods, no em-dashes), emoji usage (🔥✨🌿🙌), and message length (short, conversational). No jarring tonal shifts. A reader would believe all examples are the same agent (Tami's voice) talking to different leads. evidence (2)
|
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions in system.md's flow are guarded. Stage 2 Welcome is sent after Stage 1 Apertura (universal, not risky). Stage 3 branching is explicitly guarded: 'SÍ' → payment link, 'NO / lo pienso' → soft close, 'pregunta nueva' → derivation. Stage 4 post-link is guarded: 'cualquier respuesta' → NO_RESPONSE. Gym presencial derivation is guarded by keyword detection ('gym', 'gimnasio', 'ballester', 'presencial'). Examples demonstrate all guards firing correctly (Ex1 SÍ → link, Ex2 duda → soft close, Ex9 minor → NO_RESPONSE after one response). evidence (2)
|
| BP-8 | HIGH | PASS | No stale version language in examples All examples use current flow language from system.md. Welcome block in examples matches system.md verbatim (🔥 Plan online MENTALIDAD 🔥, ✅ bullets, pricing, ¿Te gustaría arrancar?). Closing CTAs match current system.md (link + alias + Tami WhatsApp). No stale phrases from prior flow versions detected. evidence (2)
|
| BP-9 | MEDIUM | FAIL | No duplicated instructions Principle 1 ('Welcome en un solo mensaje. Apertura + welcome + pregunta cierre van JUNTOS en el mismo turno. No partes.') is restated in system.md's Stage 2 section ('El welcome se manda en el mismo turno que la apertura (un solo mensaje, no dos). Nunca lo dividas.'). This is a duplicated instruction — the same rule appears in two canonical locations (Principles and Flow). One copy should be removed; the other should cross-reference. evidence (2)
|
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, flow, conversational style) is expressed via Voice section (5-6 real message samples) and Principles (5 principles + examples demonstrating them). Hard rules remain for factual constraints (pricing, eligibility age 18+, gym presencial contact). Principles 2, 7, 8, 9 are behavioral and are reinforced by worked examples (Ex6 objective, Ex7 pain reframe, Ex1/14/15 audio path, Ex16/17/18 gym derivation). No behavioral rule is stated without example support. |
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | PASS | 106 lines |
| 6d | 1.2 | PASS | 18 examples |
| 6e | 1.3 | WARN | 9 principles (target ≤7) |
| 6g | PAT-006 | WARN | non-STEP-0 keyword handling |
| 6h | Anti-pat | PASS | no 'burbuja' |
| 6i | Anti-pat | PASS | no HTML comments |
| 6j | Anti-pat | FAIL | 49 em-dashes across 1 file(s); first: system.md:1 |
| 6k | PAT-006 | PASS | no tool syntax leak |
| 6l | Resources | PASS | no placeholder URLs |
| 6m | Hygiene | PASS | no audit metadata in prompt files |
| 6n | PAT-008 | PASS | URL forms consistent across files |
| 6q | PAT-001 | PASS | no instruction duplication into examples.md, keywords.json, program.json, resources.json |
| 6r | Keyword-drift | PASS | all 9 keyword(s) consistent across keywords.json + system.md (no DB) |
| 6s | Hygiene | PASS | no expired dates in live SDK |
| 6t | Coverage | WARN | 6/9 principle(s) without example: #2 Nunca preguntes "bajar o masa" como pregunta inicial., #3 No inventés información., #4 No prometás resultados específicos., #6 El plan arranca cuando se abona., #7 Reframe pain antes del welcome. |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-07-20 | weekly funnel report jul13 19 volume drop | metrics, funnel, keywords, content-strategy |
| 2026-07-20 | weekly funnel report jul13 jul19 volume decline | metrics, funnel, keyword-analysis, automation |
| 2026-07-13 | weekly funnel report jul 06 12 keyword performance | analytics, keyword-performance, content-strategy |
| 2026-07-06 | weekly funnel report jun29 jul05 volume decline | metrics, reporting, keyword-analysis, content-strategy |
| 2026-07-02 | gym presencial ballester derivacion daiana | keyword, routing, gym-presencial, daiana, deploy |
| 2026-07-02 | gym presencial ballester routing daiana | routing, gym-presencial, product-differentiation, keyword-triggers |
| 2026-06-29 | weekly funnel report jun 22 28 | automation, metrics, weekly-report |
| 2026-06-29 | weekly funnel report jun22 jun28 | reporting, metrics, funnel |
| 2026-06-22 | weekly funnel report jun15 21 269 convos | reporting, metrics, funnel-analysis, keywords, actionable |
| 2026-06-22 | weekly funnel report jun15 21 keywords conversions | metrics, keywords, conversion-optimization, actionable |
| 2026-06-19 | price thread echo diagnosis | |
| 2026-06-16 | weekly plan enrollments 40 signups jun 08 14 | enrollment, sales-result, weekly-metric |
| 2026-06-16 | weekly signups 40 enrollments june 8 14 | metrics, sales, data-request |
| 2026-06-15 | weekly funnel report jun 08 14 keyword performance | reporting, metrics, keyword-performance, conversion-funnel |
| 2026-06-15 | weekly funnel report jun 08 14 conversion metrics | reporting, funnel-metrics, keyword-analysis, conversion |
| 2026-06-09 | agent conversation capture fix redelivery | agent-behavior, bug-fix, handoff-workflow |
| 2026-06-08 | weekly funnel report jun 01 07 510 convos | reporting, metrics, keywords, content-strategy |
| 2026-06-05 | instagram comments audio handling fix | instagram, audio, technical-fix, bot-behavior |
| 2026-06-04 | payment flow confirmation dual pricing live | payment, pricing, agent-config, confirmed |
| 2026-06-04 | comment responses not opening dm bug investigation | bug, ad-comments, dm-routing, in-progress |
Sin pendientes en el checklist ✅
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | no | — |
| Es queja | no | — |
| Queja constructiva (accionable) | no | — |
| Señal | Cita textual | Fecha |
|---|---|---|
| Tami define activamente el flujo de pago y links, señal de apropiación del agente como herramienta propia | “None” | 2026-05-23 |
| Tami provee imagen con flujo nuevo para implementar en el agente, participación activa en la configuración | “None” | 2026-05-26 |
| Tami gestiona el handoff y define routing (Daiana para gym presencial, ella para online), co-diseñando la operación con Ninjo | “None” | 2026-07-02 |
| Pedido recurrente de atribución (lista de compradoras para cruzar con utm_term), señal de que el cliente quiere optimizar y escalar, no abandonar | “None” | — |
Sin cambios pendientes en el checklist ✅