| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 64 | 55 | +16.4% |
| Nuevas | 33 | 23 | +43.5% |
| Link sent | 2 | 0 | — |
| Calls booked | 1 | 1 | +0.0% |
| Booked/Link % | 50.0% | — | — |
| Booked/Activas % | 1.6% | 1.8% | -0.3pp |
| Booked/Nuevas % | 3.0% | 4.3% | -1.3pp |
| Revenue variable | $5.25 | $4.66 | +12.7% |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 64 | 33 | 2 | 1 | 50.0% | 1.6% | 3.0% |
| Semana anterior (7d) | 55 | 23 | 0 | 1 | — | 1.8% | 4.3% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 06-02 | 8 | 2 | 0 | 0 | — | 0.0% | 0.0% |
| 06-01 | 5 | 3 | 1 | 1 | 100.0% | 20.0% | 33.3% |
| 05-31 | 5 | 4 | 1 | 0 | 0.0% | 0.0% | 0.0% |
| 05-30 | 5 | 2 | 0 | 0 | — | 0.0% | 0.0% |
| 05-29 | 16 | 10 | 0 | 0 | — | 0.0% | 0.0% |
| 05-28 | 21 | 9 | 0 | 0 | — | 0.0% | 0.0% |
| 05-27 | 4 | 3 | 0 | 0 | — | 0.0% | 0.0% |
| 05-26 | 7 | 4 | 0 | 0 | — | 0.0% | 0.0% |
| 05-25 | 11 | 5 | 0 | 0 | — | 0.0% | 0.0% |
| 05-24 | 10 | 8 | 0 | 0 | — | 0.0% | 0.0% |
| 05-23 | 3 | 0 | 0 | 0 | — | 0.0% | — |
| 05-22 | 3 | 2 | 0 | 0 | — | 0.0% | 0.0% |
| 05-21 | 7 | 0 | 0 | 1 | — | 14.3% | — |
| 05-20 | 14 | 4 | 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 + Mission (~100 words), Voice (6 real messages + summary), Flow (4 linear Etapas with inline guards), Calibration (energy states with actions), Principles (9 items, exceeds 5-7 but all actionable), Tools (7 tools listed with triggers), NO_RESPONSE (mandatory section present). Content fits template intent. |
| BP-2 | MEDIUM | PASS | Example coverage and cap (7 base + conditional, ≤20 total) examples.md contains 18 examples covering all 7 base scenarios (happy path, resource delivery, objection handling, disqualification, emotional/sensitive, re-engagement, off-topic) plus 2 conditional scenarios (keyword trigger in Example 1, price objection in Example 8). Total count is 18, within the ≤20 cap. |
| BP-3 | HIGH | PASS | Examples align with the flow All 18 examples follow the 4-Etapa flow (Entrada → Descubrimiento → Recurso → Programa + Llamada) in order. Each example reaches a terminal state: booking confirmed, NO_RESPONSE, cierre cálido, or manual_booking_requested. No example ends mid-flow. |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md system.md contains one potential tension: Etapa 1 states 'No hay límite de intercambios — avanzar solo cuando el contexto es real, no por cantidad de mensajes' AND Etapa 3 requires 'al menos 2 preguntas de profundidad respondidas + 1 validación emocional hecha + 1 repregunta' before advancing. However, these are not contradictions — the first rule governs *when* to advance (quality-based, not message-count-based); the second rule specifies *what quality* is required. They apply under the same precondition (deciding to advance from Etapa 1→3) but are complementary, not conflicting. Examples 1, 10, 13, 14 demonstrate both rules coexisting correctly. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files align on behavior and data. Keywords.json declares 5 keywords (INFO, PLAN, CAMBIO, DOCE, QUIERO) all with identical literal_response ('buenísimo! gracias por escribirme 🤗 comentame... qué te hizo tomar la decisión de hablarme?'), which matches system.md Etapa 0 opener. Examples 1, 3, 6, 8 demonstrate keyword triggers correctly. program.json pricing ($597 3mo, $997 6mo) is never mentioned in chat per system.md Principle 4 and Etapa 3 rule ('Nunca mandar link sin sí del lead'), and examples consistently avoid price disclosure. resources.json booking URL matches the Calendly link used in all examples. No file contradicts another under the same precondition. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All 18 examples use consistent rioplatense voice: voseo (vos, tenés, querés), direct tone, short messages (1-2 sentences, 15-25 words), minimal emojis (🤗 💪 ✨ 🙌), no em-dashes or lists, natural prose. Tone varies appropriately (empathetic, curious, direct, warm) but the underlying persona is uniform. A reader would recognize all examples as the same agent. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions in system.md have inline guards. Sending the booking link is guarded: 'Nunca mandar link sin sí del lead' (Etapa 3) and 'Invitar a llamada solo si hay contexto de calidad real: al menos 2 preguntas de profundidad respondidas + 1 validación emocional hecha + 1 repregunta usando las palabras del lead.' The guard is specific (not generic) and enumerates exact criteria. Examples 1, 10, 13, 14, 15 demonstrate the guard firing correctly when criteria are met. NO_RESPONSE is guarded by explicit trigger list. No unguarded action exists. |
| BP-8 | HIGH | PASS | No stale version language in examples All examples use current flow language from system.md. Openers match Etapa 0 ('buenísimo! gracias por escribirme 🤗 comentame... qué te hizo tomar la decisión de hablarme?'). Booking CTA matches Etapa 3 ('Perfecto! Preferís agendarlo vos directo con un link, o coordinamos por acá un día y un horario que te quede cómodo?'). NO_RESPONSE is literal token, not stale phrasing. No example uses outdated CTAs or flow steps. |
| BP-9 | MEDIUM | FAIL | No duplicated instructions Principle 5 ('Diagnóstico de calidad antes de programa — No avanzar a programa o llamada hasta tener contexto real: mínimo 2 preguntas de profundidad respondidas (no superficiales), 1 validación emocional genuina, y 1 repregunta usando las palabras que usó el lead.') is restated verbatim in Etapa 3 ('Invitar a llamada solo si hay contexto de calidad real: al menos 2 preguntas de profundidad respondidas + 1 validación emocional hecha + 1 repregunta usando las palabras del lead.'). The same instruction appears in two locations with nearly identical wording. This is duplication, not a principle reinforced by an example. evidence (2)
|
| BP-10 | MEDIUM | FAIL | Rule-vs-principle balance Principles 1–3 and 8–9 are behavioral rules disguised as principles. Principle 1 ('No inventar') is a safety boundary, not behavior. Principle 2 ('No diagnosticar, no prometer resultados') is a safety boundary. Principle 3 ('Menores de edad → derivar') is a safety boundary. Principle 8 ('Precio temprano → redirigir a descubrimiento') is a hard rule about flow branching, not a principle. Principle 9 ('Max 1 caso de éxito por mensaje') is a formatting rule. These should be expressed as examples or moved to a separate Safety/Rules section. The template guidance states: 'Behavioral guidance (tone, flow, conversational style) should be expressed as principles + examples. Hard rules should remain only for factual constraints, safety boundaries, and compliance constraints.' Principles 1–3 are safety (acceptable), but 8–9 are behavioral rules that should be demonstrated via examples, not stated as principles. evidence (2)
|
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | PASS | 104 lines |
| 6d | 1.2 | PASS | 18 examples |
| 6e | 1.3 | N/A | no Principles section |
| 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 | 62 em-dashes across 1 file(s); first: system.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 | 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 | 2 in keywords.json + recent digest, never named in system.md: ['DOCE', 'QUIERO'] |
| 6s | Hygiene | WARN | 1 expired date reference(s) in SDK files |
| 6t | Coverage | N/A | no Principles or Flujo section found in system.md |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-06-01 | weekly funnel metrics cambio keyword validation | metrics, keyword-performance, funnel-analysis, content-strategy |
| 2026-06-01 | buyer attribution tracking pending | attribution, data-tracking, buyer-mapping, unresolved |
| 2026-06-01 | weekly funnel report cambio keyword performance | reporting, keyword-performance, conversion-analysis, content-strategy |
| 2026-06-01 | buyer attribution loop cortex request pending | buyer-attribution, data-request, unresolved, pending-response |
| 2026-05-31 | high value lead intervention maritasilvetti | lead-scoring, manual-intervention, booking-pending, warm-lead |
| 2026-05-31 | high value lead maritasilvetti manual intervention | lead-scoring, manual-intervention, booking-pending, high-priority |
| 2026-05-26 | program quota status check | program-management, capacity-planning |
| 2026-05-26 | program capacity inquiry | capacity, program, pending-response |
| 2026-05-25 | weekly funnel report may 18 24 volume decline | metrics, funnel, weekly-report, volume-concern |
| 2026-05-25 | weekly report may 18 24 funnel performance | metrics, funnel, weekly-report, keywords |
| 2026-05-19 | whatsapp precall confirmation agent deployment | agent-deployment, whatsapp, booking-flow, precall |
| 2026-05-18 | buyer attribution loop blocker | attribution, analytics, blocker, recurring-request |
| 2026-05-18 | weekly metrics may 11 17 funnel analysis | metrics, funnel, weekly-report, keywords, conversion |
| 2026-05-15 | high value lead intervention daianfuentes | lead-intervention, high-value, manual-close, booking-stage |
| 2026-05-13 | pre call message template standardized | booking-confirmation, template, communication |
| 2026-05-13 | pre call message template standardization | templates, booking-flow, pre-call |
| 2026-05-11 | program quota opening confirmation | program-launch, sales-readiness |
| 2026-05-11 | quota opening sales cycle launch | sales, quota-opening, program-launch |
| 2026-05-11 | weekly funnel report may 4 10 | metrics, funnel, keywords, cambio-keyword |
| 2026-05-11 | weekly metrics may 4 10 volume drop keyword analysis | metrics, funnel, keyword-performance, action-items |
| ID | Estado | Cambio pedido |
|---|---|---|
| D5 | pendiente | Post-keyword `¡sí, mándamelo!`: el lead ya dijo "sí" — eliminar pasos de calificación, ir directo al link |
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | no | — |
| Es queja | no | — |
| Queja constructiva (accionable) | no | — |
| Señal | Cita textual | Fecha |
|---|---|---|
| Mikel aprobó entrega de métricas de abril sin objeción | “Mikel approved April metrics delivery (2,235 inbound, 149 outbound, 12 booked)” | 2026-05-04 |
| Mikel proveyó datos de buyers de abril para análisis de atribución — señal de colaboración activa | “Provided 5 April buyer names for attribution analysis (Antonella Ojeda, Ariana Aranda, Maria Florencia Sanchez, Candela Simon, Maria Jesus Vullez)” | 2026-04-30 |
| Mikel rechazó recomendaciones de setters — criterio propio, no frustración con la plataforma | “Declined setter recommendations; flow additions do not warrant implementation at current booking pace” | 2026-04-28 |
| No responde solicitudes repetidas de buyer attribution (3 veces pedido sin respuesta) — fricción operativa por omisión, no queja explícita | “Cortex pide consistentemente a Mikel handles de buyers para cruzar keyword → contenido → buyer (3 veces pedido, sin respuesta)” | — |
Un creador que pide cambios concretos está enganchado (mejor señal que el silencio).
| ID | Estado | Cambio pedido |
|---|---|---|
| D5 | pendiente | Post-keyword `¡sí, mándamelo!`: el lead ya dijo "sí" — eliminar pasos de calificación, ir directo al link |