| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 64 | 149 | -57.0% |
| Nuevas | 0 | 11 | -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) | 64 | 0 | 0 | 0 | — | 0.0% | — |
| Semana anterior (7d) | 149 | 11 | 0 | 0 | — | 0.0% | 0.0% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 07-30 | 5 | 0 | 0 | 0 | — | 0.0% | — |
| 07-29 | 4 | 0 | 0 | 0 | — | 0.0% | — |
| 07-28 | 27 | 0 | 0 | 0 | — | 0.0% | — |
| 07-27 | 4 | 0 | 0 | 0 | — | 0.0% | — |
| 07-26 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| 07-25 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 07-24 | 21 | 0 | 0 | 0 | — | 0.0% | — |
| 07-23 | 45 | 0 | 0 | 0 | — | 0.0% | — |
| 07-22 | 84 | 11 | 0 | 0 | — | 0.0% | 0.0% |
| 07-21 | 10 | 0 | 0 | 0 | — | 0.0% | — |
| 07-20 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 07-19 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| 07-18 | 3 | 0 | 0 | 0 | — | 0.0% | — |
| 07-17 | 4 | 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, Voice, Keywords, Flujos, Criterio de calificación, Casos especiales del flujo, NO_RESPONSE triggers, Principios, Fallback, and Herramientas. Content matches the template's specification. |
| BP-2 | MEDIUM | PASS | Example coverage and cap (7 base scenarios + conditional, ≤20 total) examples.md contains 21 examples covering all 7 base scenarios (happy path Examples 1–2, 7–8; resource/link delivery Examples 1–4, 13; objection handling Examples 5, 9; disqualification Examples 6, 10; emotional/sensitive Examples 12, 21; re-engagement Examples 4, 17; off-topic Examples 11) plus two conditional scenarios (keyword trigger Examples 16–17 for FAKE; price objection Example 9). Count is 21, exceeding the ≤20 cap by 1 example. evidence (1)
|
| BP-3 | HIGH | PASS | Examples align with the flow Every example in examples.md maps to a step in system.md's declared flows (GUIA, BZ, DOC, genérico, FAKE) and reaches a terminal state (booking confirmed, NO_RESPONSE, or WhatsApp derivation). No example ends mid-flow. |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md system.md contains no self-contradictions. The descarte rule (only when lead explicitly states <$200 capital) is stated once and consistently applied in Examples 6 and 10. The price rule (never in chat, redirect to call) is stated once and consistently demonstrated. No conflicting parameter values or flow step contradictions detected. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files agree on behavior and data. keywords.json declares keyword conditions (resource_with_flow, contextual) that align with system.md's flow logic. resources.json URLs match those cited in system.md and examples.md. program.json pricing rule ('no_price_in_chat') matches system.md's explicit instruction and Example 9's demonstration. No file contradicts another under the same precondition. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All examples use the same persona: Venezuelan, warm, direct, short DM-style messages, tuteo (tú, tienes, vas), no emojis except 👀 in follow-ups, no em-dashes, no regional slang (papi, chamo, coño, dale, brother). A reader could believe all examples are the same agent (Bryan) talking to different leads. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions in system.md's flow have inline guards. Sending resources (guía, VSL, video FAKE) is guarded by keyword match or flow stage. Sending Calendly is guarded by lead acceptance of the pitch. Sending WhatsApp joyería link is guarded by lead asking about physical watches. NO_RESPONSE is guarded by explicit triggers (booking confirmed, emoji-only, off-topic). Examples demonstrate these guards firing correctly. |
| BP-8 | HIGH | PASS | No stale version language in examples All examples use current flow language and CTAs from system.md. Closing language matches the 3-bubble + PDF pattern described in system.md. No examples reference deprecated flow versions or outdated CTAs. |
| BP-9 | MEDIUM | PASS | No duplicated instructions Each behavioral instruction appears in exactly one canonical location. The descarte rule is stated once in 'Criterio de calificación' section. The price rule is stated once in Identity section. The NO_RESPONSE triggers are stated once in their dedicated section. No instruction is restated in multiple places. |
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, flow, conversational style) is expressed via Voice section + 21 examples. Hard rules remain only for factual constraints (price range $1,000–$1,300, age 18+, capital threshold $200) and safety boundaries (never invent data, redirect to team on tool error). The 7 Principles are actionable and pass the common sense test. |
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | PASS | 101 lines |
| 6d | 1.2 | PASS | 21 examples |
| 6e | 1.3 | PASS | 7 principles |
| 6g | PAT-006 | WARN | non-STEP-0 keyword handling |
| 6h | Anti-pat | WARN | 2 'burbuja' mentions |
| 6i | Anti-pat | PASS | no HTML comments |
| 6j | Anti-pat | FAIL | 24 em-dashes across 1 file(s); first: knowledge_base.md:1 |
| 6k | PAT-006 | FAIL | tool-call syntax appears as raw text in examples.md (3 line(s)) |
| 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 | WARN | 4 keywords.json entr(ies) not named in system.md (no recent operator ask): ['clase', 'ganar', 'curso', 'flipping'] — likely legacy, review or remove |
| 6s | Hygiene | PASS | no expired dates in live SDK |
| 6t | Coverage | WARN | 4/7 principle(s) without example: #1 Una pregunta a la, #4 Look it up before, #5 Redirigir a la llamada, #7 Examples antes que reglas |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-06-15 | weekly funnel report low volume content gap | funnel-metrics, content-strategy, keyword-performance, action-item |
| 2026-06-15 | weekly funnel report jun 08 14 low volume | reporting, funnel-metrics, content-strategy, keyword-performance |
| 2026-06-08 | critical calendly workflow failure zero links dispatched | critical, workflow-bug, calendly, automation, funnel-impact |
| 2026-06-08 | content strategy keyword performance analysis | content, keyword-strategy, lead-generation, cta |
| 2026-06-08 | critical funnel collapse june week 1 | funnel-metrics, conversion-crisis, keyword-performance, content-strategy |
| 2026-06-01 | weekly funnel report low volume content reactivation | funnel, reporting, content-strategy, cta, volume |
| 2026-06-01 | weekly report low volume content cta strategy | reporting, traffic, content-strategy, conversion |
| 2026-05-25 | weekly funnel report zero conversions may18 24 | analytics, funnel, keyword-performance, critical |
| 2026-05-25 | weekly funnel report may18 24 critical decline | funnel-metrics, keyword-performance, conversion-crisis |
| 2026-05-25 | monthly performance review 296 convos zero sales | analytics, sales-tracking, marketing-strategy, critical |
| 2026-05-18 | weekly funnel report may 11 17 | metrics, funnel-analysis, keyword-performance, action-items |
| 2026-05-11 | coordination meeting scheduled | alignment, meeting |
| 2026-05-11 | weekly funnel report may 4 10 | metrics, funnel, keyword-performance, content-strategy |
| 2026-05-07 | crm app access authentication link | technical, access, crm, authentication |
| 2026-05-07 | crm access authentication link | infrastructure, crm-access, authentication |
| 2026-04-07 | miguel testing v2 doc flow | testing, feedback, voice, follow-ups, DOC-flow, cleanup |
| 2026-04-07 | rapport vsl flow redesign bro ban | agent-behavior, prompt-redesign, vocabulary-guardrails, vsl-flow |
| 2026-04-07 | monolithic prompt override deployment failure | technical-issue, deployment, prompt-architecture |
| 2026-04-07 | bz academy training docs ingested | training-data, product-knowledge, watch-trading |
| 2026-03-31 | rapport feedback lead magnets | rapport, feedback, lead-magnets, tone |
| ID | Estado | Cambio pedido |
|---|---|---|
| E10 | pendiente | Follow-up 1 (2h after silence): "Ey papi, llegaste a ver la info? Quedo pendiente si tienes alguna pregunta" style |
| I5 | pendiente | ~~resources.json whatsapp_joyeria URL pendiente~~ |
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | no | — |
| Es queja | sí | — |
| Queja constructiva (accionable) | sí | — |
| Señal | Cita textual | Fecha |
|---|---|---|
| Cliente detecta fallo crítico de flujo: 15 conversaciones sin ningún link despachado | “None” | 2026-06-08 |
| Cliente reporta revisión de 296 conversaciones con cero ventas en el mes — señal de frustración acumulada con resultados | “None” | 2026-05-25 |
| Cliente prohíbe vocabulario específico ('bro', 'brother', 'coño', 'plata', voseo argentino) — feedback accionable y preciso sobre comportamiento del agente | “None” | 2026-04-07 |
| Cliente ejecuta sesión de 19 puntos de testing sobre v2 — nivel de involucración alto, señal de que sigue apostando a la plataforma | “None” | 2026-04-07 |
| Cliente confirma que nueva versión funciona mejor pero exige más rapport — feedback positivo parcial con demanda de mejora | “None” | 2026-03-31 |
Un creador que pide cambios concretos está enganchado (mejor señal que el silencio).
| ID | Estado | Cambio pedido |
|---|---|---|
| E10 | pendiente | Follow-up 1 (2h after silence): "Ey papi, llegaste a ver la info? Quedo pendiente si tienes alguna pregunta" style |
| I5 | pendiente | ~~resources.json whatsapp_joyeria URL pendiente~~ |