| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 12 | 6 | +100.0% |
| Nuevas | 0 | 0 | — |
| Link sent | 0 | 0 | — |
| Calls booked | 0 | 0 | — |
| Booked/Link % | — | — | — |
| Booked/Activas % | 0.0% | 0.0% | +0.0pp |
| Booked/Nuevas % | — | — | — |
| Revenue variable | $0.00 | $0.00 | — |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 12 | 0 | 0 | 0 | — | 0.0% | — |
| Semana anterior (7d) | 6 | 0 | 0 | 0 | — | 0.0% | — |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 09-27 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| 09-26 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 09-25 | 3 | 0 | 0 | 0 | — | 0.0% | — |
| 09-24 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| 09-23 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 09-22 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 09-21 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| 09-20 | 0 | 0 | 0 | 0 | — | — | — |
| 09-19 | 0 | 0 | 0 | 0 | — | — | — |
| 09-18 | 3 | 0 | 0 | 0 | — | 0.0% | — |
| 09-17 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| 09-16 | 0 | 0 | 0 | 0 | — | — | — |
| 09-15 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| 09-14 | 1 | 0 | 0 | 0 | — | 0.0% | — |
⏳ Sin re-auditar hoy (sin cambios de prompt) — mostrando la última auditoría disponible. Estado vigente hasta nueva corrida.
| BP | Sev | Estado | Detalle |
|---|---|---|---|
| BP-1 | HIGH | PASS | Template compliance 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. |
| BP-2 | MEDIUM | PASS | Example coverage and cap (7 base scenarios + conditional, ≤20 total) examples.md contains 19 examples covering all 7 base scenarios (happy path, resource delivery, objection handling, disqualification, emotional lead, re-engagement, off-topic) plus keyword-trigger examples. Total count is 19, within the ≤20 cap. evidence (1)
|
| BP-3 | HIGH | PASS | Examples align with the flow Every example in examples.md follows the flow steps defined in system.md (Apertura → Explorar → Profundizar → Diagnóstico → Cierre/NO_RESPONSE) in order, and each reaches a terminal state (link sent, NO_RESPONSE, or graceful close). |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md system.md is internally consistent. The Calibration table and Flow section work together without contradiction. The 'no sé qué hacer' case is explicitly documented as an exception in the Profundizar step with a named action (labeling + advance to Diagnóstico), not a contradiction. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files are consistent. Keywords.json delivers the unifying greeting; system.md governs the agent's generated responses. resources.json URLs match those referenced in system.md and examples.md. program.json pricing rules align with objections.md and system.md (never mention price in DMs). Examples demonstrate the flow and calibration rules working together correctly. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All examples use consistent voice: direct, calm, rioplatense (voseo), short messages, labeling before confrontation, no opening ¿ or ¡. Tone and vocabulary remain uniform across all 19 examples. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions in system.md have inline guards. get_resource calls are guarded by Calibration conditions (dolor concreto, patrón propio, etc.). Calendly link is guarded by the 4-signal NIVEL 4 condition. NO_RESPONSE is guarded by explicit triggers (post-link without objection, emoji-only, off-topic, etc.). Examples demonstrate guards firing correctly. |
| BP-8 | HIGH | PASS | No stale version language in examples All examples use current flow language and CTAs matching system.md. Closing phrases, product recommendations, and NO_RESPONSE triggers align with the current system.md definitions. |
| BP-9 | MEDIUM | PASS | No duplicated instructions Each behavioral instruction has a single canonical home. The 'no sé qué hacer' rule appears once in Profundizar step; the labeling principle is stated once in Voz and demonstrated in examples. No instruction is restated in multiple locations. |
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, labeling, message length, rhythm adaptation) is expressed via Voice section and demonstrated in examples. Hard rules are reserved for factual constraints (price never in DMs, Calendly URL format, NO_RESPONSE literal token) and safety boundaries (never invent info, never diagnose). The balance is appropriate. |
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | PASS | 129 lines |
| 6d | 1.2 | PASS | 18 examples |
| 6e | 1.3 | PASS | 7 principles |
| 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 | PASS | no em-dashes |
| 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 6 keyword(s) consistent across keywords.json + system.md (no DB) |
| 6s | Hygiene | PASS | no expired dates in live SDK |
| 6t | Coverage | WARN | 7/7 principle(s) without example: #1 Liderás, no contenés., #2 Diagnosticá antes de ofrecer., #3 Entrega inmediata., #4 No contenido gratuito., #5 No precio en DMs.; 4/5 flow step(s) without example: #1 Apertura., #2 Explorar., #3 Profundizar., #4 Diagnóstico y entrega. |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-06-01 | weekly activation report volume recovery | reporting, volume, activation, cta-strategy |
| 2026-06-01 | weekly activation report lead volume systemization | metrics, lead-generation, cta-strategy, action-item |
| 2026-05-25 | weekly funnel report may 18 24 | metrics, funnel, volume-alert |
| 2026-05-25 | weekly volume report may 18 24 | metrics, weekly-report, volume-alert |
| 2026-05-20 | biblioteca premium 5 conversation examples | ejemplos-conversacion, nivel-3, biblioteca-premium, escalera-valor |
| 2026-05-20 | prompt simplification and logic conflict resolution | prompt-refinement, conflicting-instructions, escalera-logica, deployment-pending |
| 2026-05-19 | escalera de valor 4 niveles deployment | escalera-de-valor, product-strategy, deployment, diagnostic-framework |
| 2026-05-19 | escalera de valor 4 levels deployed | escalera-de-valor, routing-logic, v73, v74, structural-change |
| 2026-05-19 | escalera program update v79 | v79, escalera-de-valor, program-update, examples-masterclass, nivel-1-fix, diagnose-before-offer |
| 2026-05-19 | masterclass freebie removed v77 | masterclass, v77, resources-cleanup, escalera-clarification, paid-masterclass-link |
| 2026-05-19 | no free content rule v75 | no-free-content, v75, principio-14, hard-rule |
| 2026-05-19 | no free content mandate strict policy | free-content-ban, policy-enforcement, resource-delivery, anti-freebie |
| 2026-05-19 | resources json update technical challenge | technical-issue, resources-config, api-gateway |
| 2026-05-18 | eliminate keyword triggers in deep conversations | conversation-flow, keyword-strategy, naturalism |
| 2026-05-18 | keywords only cold entry deep convos natural | prompt-iteration, conversion-logic, product-routing |
| 2026-05-18 | weekly metrics ay 11 17 volume drop | metrics, monitoring |
| 2026-05-18 | product first hierarchy call exception only | conversion-hierarchy, routing-logic, critical-structural-change |
| 2026-05-18 | immediate delivery principle no delays | authority, delivery, trust-erosion |
| 2026-05-18 | immediate product delivery no delay language | authority, conversion, prompt-iteration |
| 2026-05-17 | block automatic call routing product first | agent-prompt, call-routing, product-strategy, critical-fix |
| ID | Estado | Cambio pedido |
|---|---|---|
| X4 | pendiente | Flujo de calificación no es bloqueante: el agente avanza etapas sin validar condiciones. Pato deployó cambios 22:35 UTC 2026-04-22 — pendiente confirmación de Gastón |
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | no | — |
| Es queja | sí | “Detección de estado emocional para diferenciar curiosa / dolida / lista — no solo preguntar explícito, leer señales” |
| Queja constructiva (accionable) | sí | “Micro-compromiso explícito antes del link ('sí, quiero cambiar esto')” |
| Señal | Cita textual | Fecha |
|---|---|---|
| Frustración recurrente con calificación de leads: el problema no se resolvió en múltiples iteraciones | “Gastón tiene foco muy fuerte en no llevar leads tibias a la llamada. Es el tema recurrente #1 — ya hubo dos rounds de overhaul (21/04 y 22/04) y sigue viendo el problema.” | 2026-04-22 |
| Cliente reescribe copy personalmente: señal de insatisfacción con el output del agente | “Gastón reescribe el copy de primer mensaje cuando ve que no está generando la emoción/profundidad que busca” | 2026-04-22 |
| Propuesta propia del cliente sobre mejora del flujo: síntoma preciso y accionable | “Detección de estado emocional para diferenciar curiosa / dolida / lista — no solo preguntar explícito, leer señales (Gastón, 2026-04-22, abierta)” | 2026-04-22 |
| Propuesta propia del cliente: micro-compromiso antes del link como fix al ghosting | “Micro-compromiso explícito antes del link ('sí, quiero cambiar esto') (Gastón, 2026-04-22, abierta)” | 2026-04-22 |
| Pausa acordada por razones de negocio propias, no por insatisfacción con Ninjo — señal de retención activa | “Root cause = client's business in transition (prior high-ticket mentorship/system dissolved), NOT the agent. Client reorganizing offer + traffic source before resuming volume.” | 2026-06-03 |
| Alta implicación iterativa: cliente aprueba cambios de prompt y participa en decisiones de producto | “Yamila approved surgical prompt iteration to address urgency bottleneck; Ninjo to deploy after synthetic test” | 2026-05-11 |
| Cliente mantiene compromisos futuros con el servicio: acuerda retomar ~Jun 15 | “Service pause ~15 days agreed (resume ~Jun 15, third Monday). Follow-up Jun 15 to decide low-ticket+ads vs resume high-ticket.” | 2026-06-03 |
Un creador que pide cambios concretos está enganchado (mejor señal que el silencio).
| ID | Estado | Cambio pedido |
|---|---|---|
| X4 | pendiente | Flujo de calificación no es bloqueante: el agente avanza etapas sin validar condiciones. Pato deployó cambios 22:35 UTC 2026-04-22 — pendiente confirmación de Gastón |