| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 799 | 647 | +23.5% |
| Nuevas | 442 | 375 | +17.9% |
| Link sent | 3 | 0 | — |
| Calls booked | 0 | 0 | — |
| Booked/Link % | 0.0% | — | — |
| 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) | 799 | 442 | 3 | 0 | 0.0% | 0.0% | 0.0% |
| Semana anterior (7d) | 647 | 375 | 0 | 0 | — | 0.0% | 0.0% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 07-30 | 122 | 55 | 1 | 0 | 0.0% | 0.0% | 0.0% |
| 07-29 | 131 | 69 | 1 | 0 | 0.0% | 0.0% | 0.0% |
| 07-28 | 162 | 91 | 0 | 0 | — | 0.0% | 0.0% |
| 07-27 | 193 | 89 | 1 | 0 | 0.0% | 0.0% | 0.0% |
| 07-26 | 46 | 40 | 0 | 0 | — | 0.0% | 0.0% |
| 07-25 | 45 | 43 | 0 | 0 | — | 0.0% | 0.0% |
| 07-24 | 100 | 55 | 0 | 0 | — | 0.0% | 0.0% |
| 07-23 | 136 | 70 | 0 | 0 | — | 0.0% | 0.0% |
| 07-22 | 124 | 75 | 0 | 0 | — | 0.0% | 0.0% |
| 07-21 | 127 | 71 | 0 | 0 | — | 0.0% | 0.0% |
| 07-20 | 102 | 46 | 0 | 0 | — | 0.0% | 0.0% |
| 07-19 | 19 | 15 | 0 | 0 | — | 0.0% | 0.0% |
| 07-18 | 57 | 50 | 0 | 0 | — | 0.0% | 0.0% |
| 07-17 | 82 | 48 | 0 | 0 | — | 0.0% | 0.0% |
| BP | Sev | Estado | Detalle |
|---|---|---|---|
| BP-1 | HIGH | PASS | Template compliance The agent declares template 'membership-sales' in meta.md, but no matching template file exists in the repository. However, system.md contains all required sections for a principles-based agent: Identity (Identidad), Voice (Voz), Flow (Flujo), Calibration (Calibración), Principles (Principios), Tools (Herramientas), and NO_RESPONSE behaviors. The content structure and intent align with the principles template specification. |
| BP-2 | MEDIUM | PASS | Example coverage and cap (7 base scenarios + conditional, ≤20 total) examples.md contains 20 examples covering all 7 base scenarios (happy path, resource/link delivery, objection handling, graceful disqualification, emotional lead, re-engagement, off-topic) plus two conditional scenarios (keyword trigger for JCR/Jockey Club in Example 7, price objection in Example 5). Total count is exactly 20, meeting the cap requirement. |
| BP-3 | HIGH | PASS | Examples align with the flow All 20 examples in examples.md follow the flow steps defined in system.md (Conocer → Motivación → Sede → Valor → Precios → Objeciones → Pago/Datos → Cierre) in order, without skipping required steps. Each example reaches a terminal state: link sent, fallback resource, NO_RESPONSE, or objection handled with CTA. |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md system.md contains no self-contradictions. All stated rules are either defaults with explicitly named exceptions (e.g., 'Tarjeta: link directo... Única excepción, débito automático: ahí SÍ los datos van primero') or apply to different preconditions (different steps, different lead types). The flow and calibration sections coexist without conflicting outputs under any shared precondition. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files (system.md, examples.md, objections.md, keywords.json, program.json, resources.json, knowledge_base.md, personal_story.md) agree on behavior, parameters, and data. Examples demonstrate rules from system.md operating correctly (e.g., Example 7 shows JCR flow with cuota local $41.040 matching knowledge_base.md; Example 8 shows débito automático with data-first matching system.md Step 7). No file declares behavior or data that contradicts another file under the same precondition. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All 20 examples in examples.md use the same persona (Sofi, casual, energetic, rioplatense), vocabulary (voseo, informal tone), and formality level. No jarring tonal shifts; a reader could believe all examples are the same agent talking to different leads. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions in system.md's flow include inline guard clauses. Sending links is guarded by 'Confirmá la compra antes de mandar link o CBU' (Step 7). Sending CBU is guarded by the same. Qualifying/booking is guarded by lead confirmation. The 'También tenemos Estación Club Dúo' mention (previously dismissed as passive informational add-on) is not a targeted offer requiring a guard. Multiple worked examples (1, 7, 8, 14, 15) demonstrate guards firing correctly. |
| BP-8 | HIGH | PASS | No stale version language in examples All closing/CTA language in examples.md matches the current flow definition in system.md. Examples use current phrasing ('ya te cargué', 'te esperamos', 'éxitos', 'NO_RESPONSE') consistent with the Flujo and NO_RESPONSE sections. No stale or outdated CTAs detected. |
| BP-9 | MEDIUM | PASS | No duplicated instructions Each behavioral instruction appears in exactly one canonical location. For example, the rule 'Pedir nombre Y apellido por separado, nunca nombre completo' is stated once in system.md Step 7 and cross-referenced in program.json data_collection (not duplicated). The rule 'Confirmá la compra antes de mandar link' appears once in system.md Step 7 and is demonstrated in examples (not duplicated). No instruction is restated in two locations. |
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, flow, conversational style) is expressed via Voz section + 11 worked examples showing the voice in action, and via Principios section. Hard rules remain for factual constraints (prices, phone numbers, CBU, sedes) and safety boundaries (no razonamientos internos, no inventar). The balance is appropriate: principles + examples govern behavior; rules govern facts. |
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | PASS | 141 lines |
| 6d | 1.2 | PASS | 20 examples |
| 6e | 1.3 | PASS | 7 principles |
| 6g | PAT-006 | FAIL | keywords defined but no handling in system.md |
| 6h | Anti-pat | PASS | no 'burbuja' |
| 6i | Anti-pat | PASS | no HTML comments |
| 6j | Anti-pat | FAIL | 68 em-dashes across 1 file(s); first: system.md:3 |
| 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 | WARN | 2 keywords.json entr(ies) not named in system.md (no recent operator ask): ['amigo', 'personal trainer'] — likely legacy, review or remove |
| 6s | Hygiene | WARN | 3 expired date reference(s) in SDK files |
| 6t | Coverage | WARN | 3/7 principle(s) without example: #3 El nombre es solo lo que el lead responde a "cómo te llamás?"., #4 Confirmá la compra antes de mandar link o CBU., #7 `NO_RESPONSE` es tu único stop.; 3/7 flow step(s) without example: #2 Motivación, #4 Valor, #6 Objeciones |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-07-30 | sede sur local plans proactive detection | deployment, pricing, local-plans, detection-logic |
| 2026-07-30 | sede 3 febrero local plans proactive | deployment, pricing, local-plans, detection-logic |
| 2026-07-30 | local plans payment links closure flow | deployment, payment, closure-flow, local-plans |
| 2026-07-28 | minimum permanence da rule deployment | configuration, debito-automatico, knowledge-base, deployment |
| 2026-07-27 | weekly funnel report jul 20 26 | analytics, funnel, performance, content-strategy |
| 2026-07-23 | v92 deploy hide internal reasoning | deployment, prompt-rule, voice-tone, critical |
| 2026-07-23 | v92 deploy no internal reasoning exposed | deployment, prompt-rule, critical-fix |
| 2026-07-21 | jcr knowledge base update phone and pairing discounts | jcr, knowledge-base, deployment, pricing-rules |
| 2026-07-20 | weekly funnel report jul 13 19 | metrics, funnel, content-strategy |
| 2026-07-20 | weekly funnel report jul13 19 | metrics, performance, content-strategy |
| 2026-07-20 | weekly funnel report jul13 jul19 | metrics, performance, content-strategy |
| 2026-07-20 | pase diario price update 18k to 23k | pricing, deployment, critical-update |
| 2026-07-14 | gympass wellhub access jcr restriction rule | jcr, gympass, wellhub, access-rules, v91-deployment |
| 2026-07-14 | gympass wellhub jcr access rule | jcr, gympass, wellhub, knowledge-base |
| 2026-07-14 | jcr keywords expansion and multisede options | jcr, keywords, multisede-plans, v90-deployment |
| 2026-07-14 | jcr keyword expansion multisede plans | jcr, keywords, multisede, deployment |
| 2026-07-14 | jcr jockey club rosario sales flow deployment | jcr, sales-flow, deployment, prompt-update |
| 2026-07-14 | jcr sales flow activation | jcr, sales-flow, deployment, prompt-update |
| 2026-07-13 | weekly funnel report jul 6 12 volume up 106 | metrics, funnel, performance, content-strategy |
| 2026-07-13 | weekly funnel report july 6 12 | metrics, performance, content-strategy |
| ID | Estado | Cambio pedido |
|---|---|---|
| ⚠️ | ⚠️ | Parcialmente cubierto o depende de plataforma |
| 23 | pendiente | Bug duplicación de mensajes |
| 63 | pendiente | Agente no responde mensajes de primer contacto cortos ("Hola", "consulta") — evaluator posiblemente demasiado restrictivo |
| 64 | pendiente | Doble saludo: fix = First Contact Message a nivel plataforma (2 mensajes fijos) |
| 69 | pendiente | Follow-ups automáticos: 3 workflows (lo-pienso 23h, gracias-muerta 23h, post-precios 23h) |
| X2 | pendiente | Doble saludo (fraccionamiento) |
| Y1 | pendiente | Conv muerta ante "gracias" suelto |
| Y2 | pendiente | Follow-ups pendientes (Julian pedía desde 17/03) |
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | sí | “Julian reporta repetidamente que la IA se queda atorada o se corta sin completar la información. Es su preocupación principal post-launch.” |
| Es queja | sí | “IA en loop / cortes: Julian reporta repetidamente que la IA se queda atorada o se corta sin completar la información.” |
| Queja constructiva (accionable) | sí | “el cliente (Julian/Santiago) manda feedback directo por Slack y se aplica en el momento — múltiples versiones en un día” |
| Señal | Cita textual | Fecha |
|---|---|---|
| Alta cadencia de iteraciones: cliente muy activo y con ownership del producto | “el cliente (Julian/Santiago) manda feedback directo por Slack y se aplica en el momento — múltiples versiones en un día” | — |
| Frustración recurrente con bugs de plataforma (IA en loop / cortes): preocupación principal post-launch | “Julian reporta repetidamente que la IA se queda atorada o se corta sin completar la información. Es su preocupación principal post-launch.” | — |
| Fricción con comportamiento del agente: preguntas repetitivas sin variación | “el agente repregunta lo mismo de la misma manera, necesita más variación” | — |
| Bugs de plataforma no resolubles desde el prompt generan dependencia de soporte técnico | “varios issues son de configuración de plataforma (doble saludo, evaluator, follow-ups, IA se corta) y no se resuelven solo editando el prompt” | — |
| El cliente corrige sus propias decisiones sin fricción: señal de confianza operativa en Ninjo | “error mío, mantengámoslo así como está” | 2026-07-02 |
| Solicitud de UX diferente al flujo estándar (datos + link simultáneos): cliente con criterio propio sobre el producto | “admin requested simultaneous data+link send, but Ninjo aligned with existing multisede flow (payment-first) for consistency” | 2026-07-30 |
Un creador que pide cambios concretos está enganchado (mejor señal que el silencio).
| ID | Estado | Cambio pedido |
|---|---|---|
| ⚠️ | ⚠️ | Parcialmente cubierto o depende de plataforma |
| 23 | pendiente | Bug duplicación de mensajes |
| 63 | pendiente | Agente no responde mensajes de primer contacto cortos ("Hola", "consulta") — evaluator posiblemente demasiado restrictivo |
| 64 | pendiente | Doble saludo: fix = First Contact Message a nivel plataforma (2 mensajes fijos) |
| 69 | pendiente | Follow-ups automáticos: 3 workflows (lo-pienso 23h, gracias-muerta 23h, post-precios 23h) |
| X2 | pendiente | Doble saludo (fraccionamiento) |
| Y1 | pendiente | Conv muerta ante "gracias" suelto |
| Y2 | pendiente | Follow-ups pendientes (Julian pedía desde 17/03) |