| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 42 | 449 | -90.6% |
| Nuevas | 7 | 160 | -95.6% |
| Link sent | 0 | 0 | — |
| Calls booked | 0 | 0 | — |
| Booked/Link % | — | — | — |
| Booked/Activas % | 0.0% | 0.0% | +0.0pp |
| Booked/Nuevas % | 0.0% | 0.0% | +0.0pp |
| Revenue variable | $4.45 | $39.34 | -88.7% |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 42 | 7 | 0 | 0 | — | 0.0% | 0.0% |
| Semana anterior (7d) | 449 | 160 | 0 | 0 | — | 0.0% | 0.0% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 06-02 | 3 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 06-01 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 05-31 | 3 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 05-30 | 4 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 05-29 | 8 | 3 | 0 | 0 | — | 0.0% | 0.0% |
| 05-28 | 16 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 05-27 | 6 | 0 | 0 | 0 | — | 0.0% | — |
| 05-26 | 7 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 05-25 | 10 | 5 | 0 | 0 | — | 0.0% | 0.0% |
| 05-24 | 6 | 3 | 0 | 0 | — | 0.0% | 0.0% |
| 05-23 | 8 | 2 | 0 | 0 | — | 0.0% | 0.0% |
| 05-22 | 28 | 7 | 0 | 0 | — | 0.0% | 0.0% |
| 05-21 | 113 | 49 | 0 | 0 | — | 0.0% | 0.0% |
| 05-20 | 277 | 93 | 0 | 0 | — | 0.0% | 0.0% |
| 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 not explicitly shown but covered by NO_RESPONSE rule). Keyword-trigger example (Example 14) and price-objection examples (Examples 3, 20) are present. 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 a step in system.md's flow (Modo 1 or Modo 2) and reaches a terminal state (link sent, NO_RESPONSE, or objection handled with CTA). Examples follow the flow order without skipping required steps. |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md system.md is internally consistent. The rule 'Las inscripciones ya han cerrado' (Datos del programa) is paired with an explicit exception: 'excepciones hasta 24/05' (meta.md) and 'la venta solo avanza si paga el mismo día' (Principio 4). These are stated exceptions, not contradictions. No conflicting parameter values or flow steps detected. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files agree on behavior and data. Examples demonstrate the flow and principles correctly. Keywords.json literal_response messages align with system.md voice and opening. program.json pricing (USD 147 launch, USD 497 anchor) matches system.md and examples.md. resources.json URLs are used consistently. No file contradicts another under the same precondition. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All examples use consistent tuteo mexicano (tú/tienes/eres), warm and direct tone, short messages, no opening punctuation marks, and minimal emoji use (only in closing when lead says 'gracias'). Voice is uniform across all 21 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/payment method checks (Principio 6). Offering bonos is guarded by 'si el lead duda' (Principio 4, Knowledge Base §Bonos como palanca de cierre). NO_RESPONSE triggers are explicitly listed. Examples demonstrate guards working correctly (e.g., Example 5a shows NO_RESPONSE when lead claims payment without estado_compra=comprador). |
| BP-8 | HIGH | PASS | No stale version language in examples Examples use current flow language and CTAs. References to 'Sistema Tippol , El Administrador del Reino' and 'El Código Oculto del Dinero en la Biblia' match system.md. Closing language ('Las inscripciones ya cerraron', bonos as palanca) aligns with current flow definition. |
| BP-9 | MEDIUM | PASS | No duplicated instructions Each behavioral instruction has a single canonical home. Principles are stated once in system.md. Flow steps are not restated in examples preambles. The rule 'NO re-presentarse' (Principio 5) appears once in system.md and is demonstrated in Example 19, not duplicated. Cross-references are minimal and appropriate. |
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, flow, conversational style) is expressed via Voice section and Principles + examples. Hard rules remain for factual constraints (price USD 147, 7-day guarantee, 8 weeks duration, country-specific payment options). The balance favors principles and examples over prescriptive 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 | FAIL | 1 in keywords.json + recent digest, never named in system.md: ['COSTO']; (7 stale drift entr(ies) ignored — no recent digest mention) |
| 6s | Hygiene | WARN | 7 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-01 | iyb vip community post event baseline | iyb-vip, community, post-sale, retention, automated-report |
| 2026-06-01 | iyb vip community post event retention check | post-venta, iyb-vip, community, retention, weekly-report |
| 2026-05-25 | weekly funnel report titto may18 24 | report, funnel-analytics, conversion, keyword-analysis |
| 2026-05-25 | weekly funnel report titto may 18 24 | analytics, funnel, titto, reporting |
| 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 | bonus post close policy adjustment | incentives, policy-change, post-close |
| 2026-05-22 | enrollment date confusion corrected | messaging, dates, first-class-reference |
| 2026-05-22 | enrollment exception process refined | exceptions, process, deadline-management |
| 2026-05-21 | 3 installment template broadcast execution | execution, campaign, messaging |
| 2026-05-21 | template delivery history visibility gap | technical-debt, integration, ninjo-manychat |
| 2026-05-21 | performance vs baseline confirmed | performance, metrics |
| 2026-05-21 | launch close recap and thanks | launch-recap, client-success, next-project |
| 2026-05-21 | payment option defaults clarified | payments, messaging, regional-rules, policy |
| 2026-05-21 | maria closing urgency self instructions | urgency, closing-day, agent-bug, qa |
| 2026-05-21 | recorded bonuses close day strategy | incentives, closing-strategy, messaging |
| 2026-05-21 | charlas feedback 12cuotas klarna bonos | feedback, payment-options, bonos, cierre |
| 2026-05-21 | template broadcast visibility gap | automation, ninjo, template-broadcasts, bug |
| 2026-05-20 | day2 ops video tags bonos fix | video-clase-18-05, tags-report, becas, bonos, manychat-bug |
| 2026-05-20 | agent response delay investigation | bug, agent-behavior, response-time |
| 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 |
|---|---|---|
| Señal positiva explícita del cliente sobre performance del agente vs baseline histórico | “hemos mejorado mucho vs IYB” | 2026-05-21 |
| Participación activa y colaborativa del cliente: entrega de datos, feedback iterativo y validaciones continuas | “None” | — |
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 |