| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 379 | 367 | +3.3% |
| Nuevas | 204 | 113 | +80.5% |
| 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 | $12.57 | $15.79 | -20.4% |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 379 | 204 | 0 | 0 | — | 0.0% | 0.0% |
| Semana anterior (7d) | 367 | 113 | 0 | 0 | — | 0.0% | 0.0% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 06-02 | 152 | 81 | 0 | 0 | — | 0.0% | 0.0% |
| 06-01 | 63 | 22 | 0 | 0 | — | 0.0% | 0.0% |
| 05-31 | 47 | 33 | 0 | 0 | — | 0.0% | 0.0% |
| 05-30 | 35 | 16 | 0 | 0 | — | 0.0% | 0.0% |
| 05-29 | 32 | 18 | 0 | 0 | — | 0.0% | 0.0% |
| 05-28 | 28 | 21 | 0 | 0 | — | 0.0% | 0.0% |
| 05-27 | 22 | 13 | 0 | 0 | — | 0.0% | 0.0% |
| 05-26 | 37 | 5 | 0 | 0 | — | 0.0% | 0.0% |
| 05-25 | 55 | 17 | 0 | 0 | — | 0.0% | 0.0% |
| 05-24 | 7 | 0 | 0 | 0 | — | 0.0% | — |
| 05-23 | 55 | 19 | 0 | 0 | — | 0.0% | 0.0% |
| 05-22 | 89 | 17 | 0 | 0 | — | 0.0% | 0.0% |
| 05-21 | 60 | 29 | 0 | 0 | — | 0.0% | 0.0% |
| 05-20 | 64 | 26 | 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 intent and specification. |
| BP-2 | MEDIUM | PASS | Example coverage and cap (7 base scenarios + conditional, ≤20 total) examples.md contains 15 examples covering all 7 base scenarios (happy path, resource/link delivery, objection handling, disqualification, emotional lead, re-engagement, off-topic) plus price-objection conditional (agent has pricing). Total count is 15, within the ≤20 cap. |
| BP-3 | HIGH | PASS | Examples align with the flow Every example in examples.md follows the 4-stage flow defined in system.md (Apertura → Welcome → Branching → Post-link), reaches a terminal state (conversion, soft close, or NO_RESPONSE), and does not skip required steps. |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md system.md contains a contradiction regarding the welcome message delivery. The Flow section states 'El welcome se manda en el mismo turno que la apertura (un solo mensaje, no dos)' but also prescribes different apertura responses that vary in length and content, creating ambiguity about whether all apertura paths result in a single combined message or multiple messages. evidence (2)
|
| BP-5 | CRITICAL | FAIL | No cross-file contradictions keywords.json contains literal_response messages that contradict the flow defined in system.md. The keyword responses deliver information and CTAs without following the 4-stage flow (Apertura → Welcome → Branching → Post-link), and they reference a landing URL (https://planmentalidad.taplink.ws) that system.md explicitly forbids due to a temporary pause. evidence (2)
|
| BP-6 | MEDIUM | PASS | Voice consistency across examples All examples in examples.md use consistent voice: warm, informal, voseo rioplatense, minimal punctuation, emoji usage, and the signature 'amor' closing. No jarring tonal shifts detected across the 15 examples. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) The Flow section prescribes sending the welcome message and WhatsApp link without an explicit guard condition. The rule 'El welcome se manda en el mismo turno que la apertura' lacks a stated precondition (e.g., 'only if lead is engaged' or 'only if lead is not a disqualifier'). The action could fire for any lead input. evidence (1)
|
| BP-8 | HIGH | PASS | No stale version language in examples All examples in examples.md use current language and CTAs consistent with system.md's flow definition. No stale phrases from prior flow versions detected. |
| BP-9 | MEDIUM | FAIL | No duplicated instructions The instruction 'No inventés información' appears in both Principles (item 3) and in the Flow section under 'Pregunta específica nueva' with nearly identical phrasing. This is a duplicated behavioral instruction that should have a single canonical home. evidence (2)
|
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, flow, conversational style) is expressed primarily through Voice examples and Flow steps with inline guards. Hard rules are reserved for factual constraints (pricing, eligibility, disqualifiers) and safety boundaries (no invention, no diagnosis). The balance is appropriate. |
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | PASS | 102 lines |
| 6d | 1.2 | PASS | 15 examples |
| 6e | 1.3 | WARN | 8 principles (target ≤7) |
| 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 | 36 em-dashes across 2 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 | WARN | 1 keywords.json entr(ies) not named in system.md (no recent operator ask): ['más info'] — likely legacy, review or remove |
| 6s | Hygiene | PASS | no expired dates in live SDK |
| 6t | Coverage | WARN | 5/8 principle(s) without example: #2 Nunca preguntes "bajar o masa" como pregunta inicial., #3 No inventés información., #4 No prometás resultados específicos., #6 El plan arranca cuando se abona., #7 Reframe pain antes del welcome. |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-06-02 | bug audio duplicado | bug, audio, duplicate-send, platform, resolved-workaround |
| 2026-06-02 | audio duplicate bug fix deployed | bug-fix, audio, deployed |
| 2026-06-02 | temporary payment link pause alias whatsapp | payment-flow, decision, temporary-change |
| 2026-06-02 | weekly agent performance summary | metrics, reporting, agent-performance |
| 2026-06-02 | cambio temporal link pago a whatsapp alias | payment, link-change, temporary, landing-down, whatsapp, alias |
| 2026-06-02 | audio keyword dm reactivado post fix idempotencia |
Sin pendientes en el checklist ✅
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | no | — |
| Es queja | sí | — |
| Queja constructiva (accionable) | sí | — |
| Señal | Cita textual | Fecha |
|---|---|---|
| Tami reporta bug de audio duplicado de forma precisa y accionable | “None” | 2026-06-02 |
| Tami coordina activamente el cambio temporal de flujo de pago con el equipo Ninjo, mostrando compromiso operativo | “None” | 2026-06-02 |
| No hay expresión de enojo, frustración ni amenaza de salida atribuible al cliente en ningún digest | “None” | — |
Sin cambios pendientes en el checklist ✅