| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 11 | 7 | +57.1% |
| Nuevas | 0 | 1 | -100.0% |
| Link sent | 0 | 0 | — |
| Calls booked | 0 | 0 | — |
| Booked/Link % | — | — | — |
| Booked/Activas % | 0.0% | 0.0% | +0.0pp |
| Booked/Nuevas % | — | 0.0% | — |
| Revenue variable | $0.00 | $0.00 | — |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 11 | 0 | 0 | 0 | — | 0.0% | — |
| Semana anterior (7d) | 7 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 07-30 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 07-29 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 07-28 | 3 | 0 | 0 | 0 | — | 0.0% | — |
| 07-27 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| 07-26 | 3 | 0 | 0 | 0 | — | 0.0% | — |
| 07-25 | 0 | 0 | 0 | 0 | — | — | — |
| 07-24 | 0 | 0 | 0 | 0 | — | — | — |
| 07-23 | 0 | 0 | 0 | 0 | — | — | — |
| 07-22 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 07-21 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| 07-20 | 0 | 0 | 0 | 0 | — | — | — |
| 07-19 | 2 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 07-18 | 0 | 0 | 0 | 0 | — | — | — |
| 07-17 | 2 | 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 required sections for the principles template are present in system.md: Identity (Identidad + Misión), Voice (Voz), Flow (Flujo with STEP 0 and Fases), Calibration (Lectura de energía), Principles (5 principles listed), Tools (4 tools with triggers), and NO_RESPONSE (mandatory section). Content matches the template's intent. |
| BP-2 | MEDIUM | PASS | Example coverage and cap (7 base + conditional, ≤20 total) examples.md contains 14 examples covering all 7 base scenarios (happy path Ej1, resource/link delivery Ej2/2b, objection handling Ej6, disqualification Ej5, emotional/sensitive Ej5, re-engagement Ej14, off-topic Ej11) plus two conditional scenarios: keyword trigger (Ej2/10/10b/12/13) and price objection (Ej6). Total count is 14, well under the 20-example cap. |
| BP-3 | HIGH | PASS | Examples align with the flow Every example in examples.md follows the flow defined in system.md: STEP 0 keyword check, then Fase 1 (apertura + calificación with fork), Fase 2 (conocer al lead), Fase 3 (empatía + pitch), Fase 4 (booking). All examples reach a terminal state (booking link sent, NO_RESPONSE, or derivation to Adri). No example ends mid-flow. |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md system.md documents explicit exceptions to the universal fork rule in STEP 0 ('Excepciones (saltar el fork)') and in Fase 1, making all stated rules internally consistent. For example, MODELO with known profession skips the fork; ARTE/ONLINE apply the fork then send link directly if professional. These are named exceptions, not contradictions. No shared precondition produces conflicting outputs. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files agree on behavior and parameters. system.md's flow rules (fork, keyword handling, booking gate) are consistently demonstrated in examples.md. keywords.json response hints align with system.md's flow steps. resources.json URLs match those cited in system.md and examples.md. program.json declares KIDS MÁSTER DIGITAL (12 weeks) and the taller online-infancia, both referenced consistently across files. No file demonstrates behavior that contradicts another under the same precondition. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All examples in examples.md use the same persona: warm, Colombian Spanish (tú/tienes/eres, no voseo), one question per message, short messages (max 2-3 lines), conversational tone. Voice samples in system.md match the tone and style demonstrated in examples. No jarring tonal shifts across examples. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions in system.md's flow include inline guards. Booking link is guarded by three conditions: (a) know the lead, (b) pitch + alignment + positive response, (c) explicit 'deseas agendarla?' question with SÍ. Derivation to Adri is guarded by the fork (mama/papa only). NO_RESPONSE is guarded by explicit triggers (rejection, emojis alone, minors, etc.). Examples demonstrate these guards firing correctly (Ej1 shows all three conditions met before booking; Ej5 shows derivation only after mama confirms interest). |
| BP-8 | HIGH | PASS | No stale version language in examples Examples use current flow language from system.md: fork phrasing ('buscas esto como profesional de infancia o como mama/papa?'), pitch language ('Kids Master Digital, 12 semanas'), booking CTA ('deseas agendarla?'), and NO_RESPONSE token. No examples reference outdated flow definitions or prior versions. |
| BP-9 | MEDIUM | PASS | No duplicated instructions Each behavioral instruction has a single canonical home. The fork rule appears once in Fase 1 (with exceptions documented in STEP 0). The booking gate (three conditions) is stated once in Fase 4. Keyword handling is documented in STEP 0 and keywords.json (which cross-references the flow, not duplicates it). No instruction is restated in two locations; cross-references exist where appropriate. |
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, conversational style, message length) is expressed via Voice section + examples, not as hard rules. Hard rules are reserved for factual constraints (no prices in chat, no invention, no diagnosis) and safety boundaries (minors → NO_RESPONSE). The 5 principles are appropriately scoped to things examples alone cannot teach (e.g., 'never invent information' is a safety boundary, not demonstrable through conversation). |
| 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 | 16 examples |
| 6e | 1.3 | PASS | 5 principles |
| 6g | PAT-006 | PASS | STEP 0 present |
| 6h | Anti-pat | PASS | no 'burbuja' |
| 6i | Anti-pat | PASS | no HTML comments |
| 6j | Anti-pat | FAIL | 19 em-dashes across 2 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 | FAIL | 1 in keywords.json + recent digest, never named in system.md: ['impacto']; (4 stale drift entr(ies) ignored — no recent digest mention) |
| 6s | Hygiene | WARN | 2 expired date reference(s) in SDK files |
| 6t | Coverage | WARN | 5/5 principle(s) without example: #1 No inventar. No dar precios., #2 No prometer resultados específicos., #3 Menores de edad → NO_RESPONSE., #5 Contenido inapropiado → NO_RESPONSE., #4 Un intento de cierre.; 6/11 flow step(s) without example: #1 Apertura + Calificación., #3 Empatía + Pitch gradual., #4 Booking., #2 Escuchar y empatizar brevemente, #5 Ofrecer la llamada con |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-07-14 | funnel performance roas analysis july 14 | analytics, ads, roas, conversion, performance |
| 2026-07-13 | keyword performance gaps taller modelo | keywords, prompt, performance, investigation |
| 2026-07-13 | agent takeover detection failure | bug, agent-behavior, human-takeover, critical |
| 2026-07-13 | weekly funnel performance jul06 12 | analytics, performance, funnel, keywords |
| 2026-07-09 | whatsapp community link distribution analysis | analytics, whatsapp-community, lead-tracking, data-request |
| 2026-07-06 | human takeover automation failure | bug, automation, human-takeover, critical |
| 2026-07-06 | agent human takeover protocol broken | bug, agent-behavior, urgent, handoff |
| 2026-07-06 | content strategy modelo keyword focus | content, instagram, keywords, conversion |
| 2026-07-06 | weekly funnel report jul 05 | metrics, performance, funnel, keywords |
| 2026-07-06 | weekly funnel report jun29 jul05 | metrics, performance, conversion, action-items |
| 2026-07-06 | resource delivery profession matching | resources, pdf, profession, qualification |
| 2026-07-01 | prompt version deployment status | prompt, version, deployment, keywords |
| 2026-07-01 | arte online taller keywords direct whatsapp routing | keyword-routing, whatsapp-integration, automation, prompt-update |
| 2026-07-01 | arte online taller keywords direct link protocol | agent-config, keywords, protocol-update, whatsapp-routing |
| 2026-06-29 | weekly funnel report jun22 jun28 volume drop | metrics, funnel, performance-alert |
| 2026-06-29 | weekly funnel report jun 22 28 volume drop | metrics, funnel, performance, alert |
| 2026-06-29 | agent performance and takeover failure | bug, human-takeover, agent-behavior, critical |
| 2026-06-25 | new taller online infancia keyword routing | new-taller, keyword-routing, qualification-flow, whatsapp-community, request |
| 2026-06-25 | new taller online protocol routing | workflow-change, qualification-rules, taller-routing, keyword-expansion |
| 2026-06-22 | enrollment attribution tracking system | analytics, tracking, data-ops |
| ID | Estado | Cambio pedido |
|---|---|---|
| 9 | pendiente | Qualification approach (v6) |
| 1 | pendiente | **Calificar antes de pitchear** — ask profession BEFORE pitching the program. Johana's real flow: qualify → empathize → pitch. NOT content-first. "Independiente o centro" is nice-t |
| 4 | pendiente | **Soft qualification early** — ask profession early in conversation ("cuéntame cuál es tu profesión?"). "Independiente o centro" is informational only — Johana: "es más para saber |
| @monirimo | pendiente | Reprogramó, no se concretó — pendiente follow-up |
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | sí | “agent too simple, lacks her voice/warmth” |
| Es queja | sí | “v5 'feels lost' — Johana tested v5 and found it unstructured. Needs more conversational direction without returning to interrogation.” |
| Queja constructiva (accionable) | sí | “Johana shared her exact manual sales flow (5+ screenshots) that generated 5 booked calls — prompt adjustment assigned to Juli.” |
| Señal | Cita textual | Fecha |
|---|---|---|
| Insatisfacción con calidad del agente — puntuación baja | “Weekly survey: 0 results, agent 2/5, Ninjo 2/5, team 5/5.” | — |
| Agente pausado por falta de voz y calidez | “agent too simple, lacks her voice/warmth” | 2026-04-02 |
| Versión v5 percibida como sin estructura | “Johana tested v5 and found it unstructured. Needs more conversational direction without returning to interrogation.” | — |
| Bug crítico: agente no cede el turno cuando Johana interviene | “agent continues responding and even disqualifies leads Johana is nurturing” | 2026-05-14 |
| Brief de marketing percibido como genérico | “Marketing brief flagged as too generic by Johana.” | 2026-03-24 |
| Johana aportó su flujo manual como estándar de oro — alta implicación | “Johana shared her exact manual sales flow (5+ screenshots) that generated 5 booked calls” | — |
| Acuerdo explícito de reactivación tras pausa — cliente sigue apostando | “reactivation agreed 2026-04-08. Johana expressed discomfort... but agreed to Agus's recommendation to turn it on and iterate with real data.” | 2026-04-08 |
| Johana entregó datos de agendados con outcomes para análisis — colaboración activa | “Johana entregó handles de 5 agendados de la semana (jannethballen, kzieseniss, manuelavg.psicologa, monirimo, judith._carrillo) con outcome de cada llamada” | 2026-05-27 |
| Iteración continua de keywords y contenido — alta actividad operativa | “Johana actively adds keywords as new posts go live. All additions go through operator channel.” | — |
Un creador que pide cambios concretos está enganchado (mejor señal que el silencio).
| ID | Estado | Cambio pedido |
|---|---|---|
| 9 | pendiente | Qualification approach (v6) |
| 1 | pendiente | **Calificar antes de pitchear** — ask profession BEFORE pitching the program. Johana's real flow: qualify → empathize → pitch. NOT content-first. "Independiente o centro" is nice-t |
| 4 | pendiente | **Soft qualification early** — ask profession early in conversation ("cuéntame cuál es tu profesión?"). "Independiente o centro" is informational only — Johana: "es más para saber |
| @monirimo | pendiente | Reprogramó, no se concretó — pendiente follow-up |