| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 62 | 87 | -28.7% |
| Nuevas | 0 | 9 | -100.0% |
| Link sent | 12 | 6 | +100.0% |
| Calls booked | 0 | 0 | — |
| Booked/Link % | 0.0% | 0.0% | +0.0pp |
| 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) | 62 | 0 | 12 | 0 | 0.0% | 0.0% | — |
| Semana anterior (7d) | 87 | 9 | 6 | 0 | 0.0% | 0.0% | 0.0% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 07-30 | 8 | 0 | 0 | 0 | — | 0.0% | — |
| 07-29 | 7 | 0 | 2 | 0 | 0.0% | 0.0% | — |
| 07-28 | 5 | 0 | 1 | 0 | 0.0% | 0.0% | — |
| 07-27 | 8 | 0 | 3 | 0 | 0.0% | 0.0% | — |
| 07-26 | 14 | 0 | 1 | 0 | 0.0% | 0.0% | — |
| 07-25 | 9 | 0 | 1 | 0 | 0.0% | 0.0% | — |
| 07-24 | 11 | 0 | 4 | 0 | 0.0% | 0.0% | — |
| 07-23 | 7 | 0 | 1 | 0 | 0.0% | 0.0% | — |
| 07-22 | 11 | 0 | 2 | 0 | 0.0% | 0.0% | — |
| 07-21 | 7 | 0 | 1 | 0 | 0.0% | 0.0% | — |
| 07-20 | 12 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 07-19 | 16 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 07-18 | 16 | 5 | 1 | 0 | 0.0% | 0.0% | 0.0% |
| 07-17 | 18 | 2 | 1 | 0 | 0.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 system.md contains all 7 required sections for the principles template: Identity, Voice, Flow, Calibration, Principles, Tools, and NO_RESPONSE. Each section matches the template's specification in scope and intent. |
| BP-2 | MEDIUM | PASS | Example coverage and cap (7 base scenarios + conditional, ≤20 total) examples.md covers all 7 base scenarios (happy path Examples 2, 6; resource/link delivery Examples 1, 4, 5; objection handling Examples 3, 7, 8; disqualification Example 14; emotional/sensitive Examples 11, 12, 13; re-engagement Example 9; off-topic Example 10) plus two conditional scenarios (keyword trigger Examples 1-5; price objection Examples 3, 7, 8). Total count is 15 examples, within the ≤20 cap. |
| BP-3 | HIGH | PASS | Examples align with the flow Every example in examples.md maps to a step in system.md's Flow and reaches a terminal state (NO_RESPONSE, booking confirmed, or resource delivered with close). 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 Flow section explicitly documents exceptions (e.g., 'Keyword fired → follow its flow in keywords.json'; 'Money concern surfacing AFTER Gate 2 → REWIRED replay link once + close'). These are stated exceptions, not contradictions. The Calibration section and Principles section coexist without conflict — they govern different aspects (energy read vs. behavioral constraints). |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files agree on behavior and parameters. keywords.json declares keyword flows (REWIRED, SOAR, HEAL, AGE, RECLAIM, RETREAT, SORA) that are explicitly referenced in system.md Flow ('Keyword fired → follow its flow in keywords.json'). resources.json URLs match those in system.md and examples.md. program.json pricing rules align with system.md's objection handling and Flow steps. No file demonstrates behavior that contradicts another under the same precondition. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All examples use the same persona, vocabulary, formality level, and dialect. Voice samples in system.md (lowercase casual, short messages, one question per message, no markdown) are mirrored consistently across all 15 examples. No jarring tonal shifts. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions in system.md's Flow are guarded with inline conditions. Calendar link (Flow step 5) is guarded: 'Both qualification gates must pass AND pre-booking consent delivered before sending this link' (resources.json). REWIRED replay is guarded by Principle 3 (safety overrides). Resource delivery is guarded by topic/keyword matching and lead energy (Calibration). Multiple worked examples (1, 2, 3, 6, 7) demonstrate guards firing correctly. |
| BP-8 | HIGH | PASS | No stale version language in examples All examples use current language and CTAs that match system.md's Flow definition. The discovery call link, REWIRED replay URL, and resource URLs are all current. No examples reference deprecated flows or old resource names (e.g., no 'Soar Collective' as an active offer in examples, consistent with resources.json marking it ON_HOLD). |
| BP-9 | MEDIUM | PASS | No duplicated instructions Each behavioral instruction has a single canonical home. Flow steps are stated once in system.md. Keyword flows are defined once in keywords.json. Resource guards are stated once in resources.json. No instruction is restated in two locations; cross-references exist (e.g., 'Keyword fired → follow its flow in keywords.json') but not duplicates. |
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, warmth, reflection style) is expressed via Voice section and examples. Hard rules remain for factual constraints (pricing never stated in DMs, REWIRED replay URL, discovery call link, safety boundaries). The 5 Principles are behavioral constraints that examples alone would not teach (never invent info, never coach in DM, safety overrides, qualification sequence, English-only reminder). 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 | 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 | 82 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 | WARN | audit metadata (dates/slack refs) in 2 file(s) — adds noise to live prompt |
| 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 | PASS | all 13 keyword(s) consistent across keywords.json + system.md (no DB) |
| 6s | Hygiene | WARN | 4 expired date reference(s) in SDK files |
| 6t | Coverage | N/A | no Principles or Flujo section found in system.md |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-07-15 | ninjo roi sequencing and replay flow roadmap | roi, replay-flow, sequencing, ninjo-agent, funnel |
| 2026-07-15 | ninjo roi honest assessment replay flow | roi, replay-flow, sequencing, agent-strategy |
| 2026-07-15 | roi honesty replay flow | roi, retention, replay-flow, manychat, sequencing, ads |
| 2026-07-11 | decision timeline next steps monday | decision, timeline, next-steps |
| 2026-07-10 | ninjo as engine for new business arms | strategy, product-roadmap, scaling |
| 2026-07-10 | claude intelligence integration ninjo connected | product-feature, business-intelligence, ai-integration, decision |
| 2026-07-10 | monday next steps manychat ninjo transition | action-item, workflow |
| 2026-07-10 | rewired format decision timeline extended | action-item, timeline, decision-needed |
| 2026-07-10 | ninjo mtg replay flow spec | replay-flow, manychat, keywords, rewired, spec, call-transcript |
| 2026-07-10 | post mtg follow up tricky item | follow-up, action-item |
| 2026-07-09 | ninjo mtg scheduled july 10 | meeting, scheduling |
| 2026-07-08 | clean two week test partition workflow | workflow, attribution, testing, decision |
| 2026-07-08 | call scheduled two week plan lock | call, scheduling, coordination |
| 2026-07-08 | bot auto turnoff stability note | technical, stability |
| 2026-07-08 | replay nurture sequence strategy confirmed | strategy, nurture, replay |
| 2026-07-08 | claude ninjo data integration self serve | product, business-intelligence, proposal |
| 2026-07-08 | facebook business page capture setup | facebook, scaling, expansion, action-item |
| 2026-07-08 | clean two week test structure and scope | testing, attribution, scope-definition, manyChat-integration |
| 2026-07-08 | reengagement mcp 2week test team change | reengagement, mcp, claude-data, parallel-test, team-change, age-keyword, facebook, replay-flow |
| 2026-07-08 | bruce nonqualified autopause validation | forensics, non-qualified, auto-pause, validation, positive |
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 |
|---|---|---|
| Señal de churn activo: pidió pausa de facturación y evaluación de ROI antes de comprometerse otro mes | “None” | 2026-07-02 |
| Decisión de mantener el agente corriendo condicionada a revisión financiera y ROI — no es compromiso firme | “None” | 2026-07-03 |
| Cargo erróneo por suscripción antigua reactivada — evento de fricción que erosiona confianza en la plataforma | “None” | 2026-07-03 |
| Pago de expansión (scraper add-on) confirmado — señal de engagement activo y disposición a invertir más | “None” | 2026-06-04 |
| Adopción de integración Claude + datos Ninjo para BI en tiempo real — señal de profundización del uso | “None” | 2026-07-10 |
| Test limpio de dos semanas acordado con partición de keywords — cliente exige claridad de atribución antes de renovar | “None” | 2026-07-08 |
Sin cambios pendientes en el checklist ✅