| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 571 | 566 | +0.9% |
| Nuevas | 199 | 278 | -28.4% |
| Link sent | 23 | 22 | +4.5% |
| Calls booked | 4 | 7 | -42.9% |
| Booked/Link % | 17.4% | 31.8% | -14.4pp |
| Booked/Activas % | 0.7% | 1.2% | -0.5pp |
| Booked/Nuevas % | 2.0% | 2.5% | -0.5pp |
| Revenue variable | $27.55 | $31.33 | -12.1% |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 571 | 199 | 23 | 4 | 17.4% | 0.7% | 2.0% |
| Semana anterior (7d) | 566 | 278 | 22 | 7 | 31.8% | 1.2% | 2.5% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 06-02 | 147 | 17 | 4 | 0 | 0.0% | 0.0% | 0.0% |
| 06-01 | 52 | 23 | 6 | 2 | 33.3% | 3.8% | 8.7% |
| 05-31 | 40 | 32 | 3 | 0 | 0.0% | 0.0% | 0.0% |
| 05-30 | 32 | 17 | 6 | 1 | 16.7% | 3.1% | 5.9% |
| 05-29 | 134 | 27 | 2 | 0 | 0.0% | 0.0% | 0.0% |
| 05-28 | 75 | 30 | 1 | 1 | 100.0% | 1.3% | 3.3% |
| 05-27 | 91 | 53 | 1 | 0 | 0.0% | 0.0% | 0.0% |
| 05-26 | 128 | 88 | 5 | 2 | 40.0% | 1.6% | 2.3% |
| 05-25 | 113 | 53 | 6 | 2 | 33.3% | 1.8% | 3.8% |
| 05-24 | 43 | 29 | 0 | 0 | — | 0.0% | 0.0% |
| 05-23 | 38 | 26 | 1 | 0 | 0.0% | 0.0% | 0.0% |
| 05-22 | 61 | 20 | 2 | 0 | 0.0% | 0.0% | 0.0% |
| 05-21 | 75 | 26 | 3 | 3 | 100.0% | 4.0% | 11.5% |
| 05-20 | 108 | 36 | 5 | 0 | 0.0% | 0.0% | 0.0% |
| 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. Content matches template intent. |
| BP-2 | MEDIUM | FAIL | Example coverage and cap (7 base scenarios + conditional, ≤20 total) Agent has 22 examples, exceeding the 20-example cap. While coverage of base scenarios is strong, the count violates the rule. Candidates for retirement: Examples 15–16 (student/resident disqualification) are redundant; Examples 7 and 17 (lead magnet delivery) overlap; Examples 12 and 20 (evasive lead handling) are similar. evidence (2)
|
| BP-3 | HIGH | PASS | Examples align with the flow All examples follow the documented flow (Discovery → Fit → Contexto → Nutrir → Ofrecer llamada → Cerrar → NO_RESPONSE). Each example reaches a terminal state (link sent, NO_RESPONSE, or confirmed booking). |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md The PROMPT keyword exception is explicitly documented in the Flow section ('Excepcion: Si el lead escribe "prompt"...'), creating a stated carve-out from the general discovery-first rule. This is a single rule with an explicit exception, not a contradiction. No shared precondition produces conflicting outputs. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files are consistent. Keywords.json declares PROMPT as an exception with send_without_permission=true and literal_response pointing to get_resources. system.md documents this exception inline. Examples 1–22 demonstrate the flow and keyword handling without contradiction. Resources.json, program.json, and objections.md align with system.md behavior and pricing rules. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All examples use consistent voice: short messages (max 3 lines), rioplatense voseo, strategic/consultive tone, minimal emojis, no filler greetings after the first message. Tone is uniform across all 22 examples. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions (sending links, closing, NO_RESPONSE) are guarded. Discovery step requires context before Nutrir. Nutrir requires affirmative signal ('es lo que buscabas?') before Ofrecer llamada. Cerrar requires confirmation before sending booking link. NO_RESPONSE triggers are named in Calibration and Principles. Examples demonstrate guards firing correctly. |
| BP-8 | HIGH | PASS | No stale version language in examples All examples use current flow language and CTAs. Closing language matches system.md ('cuando agendas, responde las preguntas...', 'me confirmas cuando la agendaste?'). No outdated phrasing detected. |
| BP-9 | MEDIUM | FAIL | No duplicated instructions The instruction 'no listar pilares, modulos ni detalles del programa en el chat' appears in three places: Voice section ('No listar pilares, modulos ni detalles del programa en el chat'), Flujo step 1 ('NUNCA listar pilares, modulos ni detalles del programa en el chat'), and Principios item 1 ('nunca mencionar Elite MED hasta entender que busca el lead'). This is duplication across Voice, Flow, and Principles. evidence (3)
|
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, discovery-first, no program details in chat) is expressed via Voice section + examples + Principles. Hard rules are reserved for factual constraints (pricing template, NO_RESPONSE triggers, eligibility). The balance is appropriate for the principles template. |
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | PASS | 120 lines |
| 6d | 1.2 | PASS | 22 examples |
| 6e | 1.3 | PASS | 6 principles |
| 6g | PAT-006 | WARN | non-STEP-0 keyword handling |
| 6h | Anti-pat | WARN | 1 'burbuja' mentions |
| 6i | Anti-pat | PASS | no HTML comments |
| 6j | Anti-pat | FAIL | 7 em-dashes across 1 file(s); first: objections.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 | WARN | 1 URL(s) appear with different tracking params or formats across SDK files |
| 6q | PAT-001 | PASS | no instruction duplication into examples.md, keywords.json, program.json, resources.json |
| 6r | Keyword-drift | WARN | 3 keywords.json entr(ies) not named in system.md (no recent operator ask): ['REFERENTE', '10X', 'PROTOCOLO'] — likely legacy, review or remove |
| 6s | Hygiene | PASS | no expired dates in live SDK |
| 6t | Coverage | WARN | 3/6 principle(s) without example: #2 No dar precios completos, #4 Si el lead llega, #5 Si no tienes la; 6/9 flow step(s) without example: #2 Fit, #3 Contexto, #5 Cerrar, #1 Saludar y preguntar su, #2 Si confirma ser profesional |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-06-03 | daily lead summary june 3 | leads, sales, priority, followup, urgent |
| 2026-06-02 | database query optimization completed | technical, database, operations |
| 2026-06-02 | daily lead summary june 1 data extraction | reporting, leads, data-extraction, sales-pipeline |
| 2026-06-02 | daily lead pipeline 24 leads processed | leads, pipeline, operations |
| 2026-06-02 | daily lead summary june 2 | leads, sales, priority, followup |
| 2026-06-02 | database query optimization lead export | database, performance, leads, automation |
| 2026-06-01 | daily lead report lopez coronado luis | lead-tracking, daily-report, follow-up |
| 2026-06-01 | weekly metrics high traffic low conversions | metrics, alert, funnel, sales |
| 2026-06-01 | keyword performance recurso highest conversion | content-strategy, conversion, growth, data |
| 2026-06-01 | weekly cortex metrics report week 6 | metrics, weekly-report, funnel-analysis |
| 2026-06-01 | previous day lead summary 1 prospect | leads, operations |
| 2026-06-01 | agent performance week 3 sebariera 490 convs | agent-performance, keyword-analysis, content-strategy, lead-scoring |
| 2026-06-01 | weekly cortex metrics traffic spike no sales | metrics, reporting, funnel-analysis, alert |
| 2026-05-31 | daily lead sync may 30 31 nine plus one leads | lead-tracking, daily-summary, action-items |
| 2026-05-30 | lead batch processing may 29 30 | leads, outreach, automation, google-sheet-sync |
| 2026-05-30 | leads batch processing may 29 35 leads | leads, automation, reporting, webhook, bug-fix |
| 2026-05-29 | leads batch processing may 28 29 | leads, automation, reporting, webhook |
| 2026-05-29 | daily leads report may 28 22 conversions | leads, daily-report, automation, google-sheets |
| 2026-05-29 | daily leads processing 2026 05 28 | reporting, leads, follow-up-required |
| 2026-05-28 | daily leads processing 2026 05 27 | reporting, leads, follow-up-required |
Sin pendientes en el checklist ✅
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | no | — |
| Es queja | no | — |
| Queja constructiva (accionable) | no | — |
Sin cambios pendientes en el checklist ✅