Sin actividad del agente en la ventana.
| BP | Sev | Estado | Detalle |
|---|---|---|---|
| BP-1 | HIGH | PASS | Template compliance system.md contains all 7 required sections for principles template: 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 covers 6 of 7 base scenarios (happy path, resource/link delivery, objection handling, disqualification, emotional/sensitive lead, re-engagement present; off-topic question covered via Example 11 minor). Both conditionals met: keyword-trigger examples (Examples 5b, 14) and price-objection examples (Examples 3, 20). Total count is 21 examples, exceeding the ≤20 cap by 1. evidence (1)
|
| BP-3 | HIGH | PASS | Examples align with the flow Every example in examples.md maps to the flow steps in system.md (Modo 1 or Modo 2 → discovery → acknowledge + reframe → proposal → link/close or NO_RESPONSE). All examples reach terminal states (link sent, NO_RESPONSE, or graceful close). |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md system.md is internally consistent. Apparent tensions (e.g., 'Las inscripciones ya han cerrado' vs. bonos as palanca) are explicitly documented as exceptions in the same document. The Principio 4 rule ('No forzar') and the Cierre temporal firme section both state the same precondition (post-cierre, lead asking for time) and prescribe the same action (offer bonos as carrot, no soft language). No shared precondition produces conflicting outputs. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files agree on behavior and data. examples.md demonstrates the flow and principles from system.md correctly. keywords.json literal_response messages align with system.md's Principio 5 (first message includes 'Soy María del equipo de David'). program.json pricing and bonos match system.md and examples.md. resources.json URLs are used consistently. No file demonstrates behavior that contradicts another file under the same precondition. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All examples use consistent voice: tuteo mexicano (tú/tienes/eres), warm and direct, short messages, no opening punctuation, minimal emojis (only in Example 1 greeting context). Tone is asistencial and empathetic across all scenarios. A reader would recognize the same agent across all examples. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions in system.md's flow include inline guards. Sending links is guarded by country verification and payment method checks (Principio 6, Principio 7). NO_RESPONSE is guarded by explicit trigger conditions (off-topic, emojis solos, rechazo after 2 intentos, menor de edad). Examples demonstrate guards firing correctly (Example 5a: lead claims payment but estado_compra ≠ comprador → NO_RESPONSE; Example 3: lead says 'no tengo dinero' → cuotas offered, then empathetic close). |
| BP-8 | HIGH | PASS | No stale version language in examples All examples use current flow language and CTAs from system.md. Closing language matches current definitions (e.g., 'Las inscripciones ya han cerrado' + bonos as palanca, 'Cuando tu situación cambie, acá estamos'). No references to prior flow versions or deprecated CTAs. |
| BP-9 | MEDIUM | FAIL | No duplicated instructions The instruction 'NO usar signos de apertura (¿ ¡)' appears in system.md Voz section and is restated in examples.md Example 1 preamble implicitly (no opening punctuation shown). More critically, the rule 'Principio 5: Presentación' (first message must open with 'Hola, soy María del equipo de David') is stated in system.md and then restated verbatim in keywords.json literal_response entries and Example 1. This is duplication across three locations. evidence (3)
|
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance is expressed primarily through Principles (5-7 principles covering no invention, no promises of money, avatar religioso, no forzar, presentación, cuotas junto al link, scope de María) and demonstrated via examples. Hard rules are reserved for factual constraints (pricing, cuotas per country, medios de pago, NO_RESPONSE triggers). The balance favors principles + examples over rules. |
| 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 | 24 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 | FAIL | 40 em-dashes across 3 file(s); first: system.md:29 |
| 6k | PAT-006 | PASS | no tool syntax leak |
| 6l | Resources | FAIL | placeholder URL(s) in 2 file(s) |
| 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 | 8 keywords.json entr(ies) not named in system.md (no recent operator ask): ['CODIGO OCULTO', 'FORMULA DEL REINO', 'COSTO', 'MENSUALIDADES', 'GARANTIA', 'REEMBOLSO', 'INSCRIBIR', 'REGISTRAR'] — likely legacy, review or remove |
| 6s | Hygiene | WARN | 16 expired date reference(s) in SDK files |
| 6t | Coverage | WARN | 5/7 principle(s) without example: #1 No inventar, pero sí enviar lo que tienes., #2 No prometer dinero., #3 Avatar religioso., #4 No forzar., #5 Presentación. |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-06-17 | agencia lebrot slack migration | communication, platform-change, operational |
| 2026-06-16 | julieta collado return pending definition | coordination, pending-info, changes-review |
| 2026-06-15 | next launch data inquiry | discovery, next-launch, pending |
| 2026-06-15 | weekly funnel report titto jun 08 14 | reporting, funnel, titto, community-health |
| 2026-06-15 | weekly report titto jun 08 14 | report, metrics, titto, post-purchase-support |
| 2026-06-15 | next launch data status check | launch-planning, discovery, pending-info |
| 2026-06-08 | titto weekly funnel report jun 01 07 | weekly-report, funnel-metrics, titto-agent |
| 2026-06-04 | julieta collado meeting coordination | meeting, coordination, action-item |
| 2026-06-02 | app demo metrics monitoring request | product, app-launch, meeting-request, tooling |
| 2026-06-01 | iyb vip community post event retention check | post-venta, iyb-vip, community, retention, weekly-report |
| 2026-06-01 | iyb vip community post event baseline | iyb-vip, community, post-sale, retention, automated-report |
| 2026-05-25 | weekly funnel report titto may 18 24 | analytics, funnel, titto, reporting |
| 2026-05-25 | weekly funnel report titto may18 24 | report, funnel-analytics, conversion, keyword-analysis |
| 2026-05-23 | tito launch sales closure request | sales-closure, reporting, launch-metrics |
| 2026-05-22 | recorded bonus eligibility restricted | bonus-policy, closing-incentive, authority-clarification |
| 2026-05-22 | enrollment exception process refined | exceptions, process, deadline-management |
| 2026-05-22 | bonus post close policy adjustment | incentives, policy-change, post-close |
| 2026-05-22 | enrollment date confusion corrected | messaging, dates, first-class-reference |
| 2026-05-21 | maria closing urgency self instructions | urgency, closing-day, agent-bug, qa |
| 2026-05-21 | 3 installment template broadcast execution | execution, campaign, messaging |
| ID | Estado | Cambio pedido |
|---|---|---|
| M4 | pendiente | "INSCRIBIR" / "REGISTRAR" / "LINK": resource_with_flow — link de pago (URL pendiente, ver Y1) |
| P4 | pendiente | ManyChat: cuenta NUEVA creada 07/05 — pendiente conectar |
| V15 | pendiente | "Pendiente de pago" tag en flux durante el lanzamiento |
| AB12 | pendiente | **Cuotas país-dependientes (refinamiento L2-L6)**: las cuotas son solo MX/CO/CL/PE (+Klarna EEUU). En el resto Hotmart acepta tarjeta pero **NO mostrará opciones de cuotas en check |
| AC3 | pendiente | **Etiquetas ManyChat ya creadas por Julieta (13/05)**: lista cerrada pendiente de extraer y documentar en `keywords.json` / `objections.md` antes del deploy. María setea desde el S |
| AD11 | pendiente | **Etiquetas ManyChat — write**: el agente debe poder **setear** etiquetas que vuelven a ManyChat para disparar flows de follow-up/recontacto. Configuración técnica pendiente (Fran) |
| AD12 | pendiente | **Etiquetas ManyChat — read/timing**: el agente debe **entender cuándo** poner cada etiqueta. Lista cerrada de etiquetas (creadas por Julieta 13/05) pendiente de documentar en `key |
| AE17 | pendiente | **Follow-up 2hs — pago rechazado**: trigger = lead con error de pago, sin tag `comprador`. Lógica = asesoramiento inmediato al detectar + follow-up a 2hs desde último mensaje si si |
| AE18 | pendiente | **Follow-up 30min — carrito abandonado**: trigger = lead con carrito abandonado, sin tag `comprador`. Timing = 30 minutos. Wording pendiente |
| U30 | pendiente | **Lead sin contexto del lanzamiento (cold por anuncio/historias)**: el agente menciona "la clase de hoy no quedó grabada" y salta a Hotmart sin dar intro al programa. Mat: "qué hac |
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | no | — |
| Es queja | no | — |
| Queja constructiva (accionable) | no | — |
| Señal | Cita textual | Fecha |
|---|---|---|
| Feedback positivo explícito sobre performance del agente vs baseline anterior | “hemos mejorado mucho vs IYB” | 2026-05-21 |
| Cliente entregó data BF11 completa (JSON + IDs + doc comercial + informe) para alimentar al equipo Ninjo, señal de colaboración activa | “None” | 2026-04-30 |
| Cliente solicitó análisis del lanzamiento y pidió revisión del plan de acción, señal de engagement y expectativa positiva | “te dejo reporte del lanzamiento hasta ahora, decime como lo ves / hay una seccion de plan de accion donde vimos conve” | 2026-05-21 |
Un creador que pide cambios concretos está enganchado (mejor señal que el silencio).
| ID | Estado | Cambio pedido |
|---|---|---|
| M4 | pendiente | "INSCRIBIR" / "REGISTRAR" / "LINK": resource_with_flow — link de pago (URL pendiente, ver Y1) |
| P4 | pendiente | ManyChat: cuenta NUEVA creada 07/05 — pendiente conectar |
| V15 | pendiente | "Pendiente de pago" tag en flux durante el lanzamiento |
| AB12 | pendiente | **Cuotas país-dependientes (refinamiento L2-L6)**: las cuotas son solo MX/CO/CL/PE (+Klarna EEUU). En el resto Hotmart acepta tarjeta pero **NO mostrará opciones de cuotas en check |
| AC3 | pendiente | **Etiquetas ManyChat ya creadas por Julieta (13/05)**: lista cerrada pendiente de extraer y documentar en `keywords.json` / `objections.md` antes del deploy. María setea desde el S |
| AD11 | pendiente | **Etiquetas ManyChat — write**: el agente debe poder **setear** etiquetas que vuelven a ManyChat para disparar flows de follow-up/recontacto. Configuración técnica pendiente (Fran) |
| AD12 | pendiente | **Etiquetas ManyChat — read/timing**: el agente debe **entender cuándo** poner cada etiqueta. Lista cerrada de etiquetas (creadas por Julieta 13/05) pendiente de documentar en `key |
| AE17 | pendiente | **Follow-up 2hs — pago rechazado**: trigger = lead con error de pago, sin tag `comprador`. Lógica = asesoramiento inmediato al detectar + follow-up a 2hs desde último mensaje si si |
| AE18 | pendiente | **Follow-up 30min — carrito abandonado**: trigger = lead con carrito abandonado, sin tag `comprador`. Timing = 30 minutos. Wording pendiente |
| U30 | pendiente | **Lead sin contexto del lanzamiento (cold por anuncio/historias)**: el agente menciona "la clase de hoy no quedó grabada" y salta a Hotmart sin dar intro al programa. Mat: "qué hac |