Review — elartedevivir.ar

← overview

ventana últimos 7d vs 7d previos · tz America/Argentina/Buenos_Aires · último cambio Ninjo: 2026-09-25 18:53 (keywords, hace 3d) · 333 untracked

254

Nuevas (7d)

prior 101

Calls booked

0.0% de link

Link sent

1.4% de activas

Revenue variable

333 msgs

Resumen — período vs período

Métrica	this 7d	prior 7d	Δ
Activas	966	202	+378.2%
Nuevas	254	101	+151.5%
Link sent	14	23	-39.1%
Calls booked	0	0	—
Booked/Link %	0.0%	0.0%	+0.0pp
Booked/Activas %	0.0%	0.0%	+0.0pp
Booked/Nuevas %	0.0%	0.0%	+0.0pp
Revenue variable	$0.00	$0.00	—

Funnel — semana actual vs anterior

Período	Activas	Nuevas	Link sent	Calls booked	Booked/Link	Booked/Activas	Booked/Nuevas
Semana actual (7d)	966	254	14	0	0.0%	0.0%	0.0%
Semana anterior (7d)	202	101	23	0	0.0%	0.0%	0.0%

Ver desglose por día

Día	Activas	Nuevas	Link sent	Booked/Link	Booked/Activas	Booked/Nuevas
09-27	159	9	0	—	0.0%	0.0%
09-26	383	107	3	0.0%	0.0%	0.0%
09-25	313	111	1	0.0%	0.0%	0.0%
09-24	23	6	2	0.0%	0.0%	0.0%
09-23	37	7	5	0.0%	0.0%	0.0%
09-22	33	6	3	0.0%	0.0%	0.0%
09-21	18	8	0	—	0.0%	0.0%
09-20	6	3	0	—	0.0%	0.0%
09-19	6	4	0	—	0.0%	0.0%
09-18	24	11	4	0.0%	0.0%	0.0%
09-17	38	22	3	0.0%	0.0%	0.0%
09-16	40	16	2	0.0%	0.0%	0.0%
09-15	37	20	7	0.0%	0.0%	0.0%
09-14	51	25	7	0.0%	0.0%	0.0%

run 2026-07-24T14:58:26+00:00 · fuente: live DB state (daily_audit pipeline)

4/10

BP semánticos PASS

top-10 best practices

14/16

Determinísticos PASS

2 FAIL · 0 WARN

C0 · H1 · M0

Fails por severidad

critical / high / medium

—

Drift

DB vs repo local

BP semánticos (top-10 best practices)

BP-1

BP-2

BP-3

BP-4

BP-5

BP-6

BP-7

BP-8

BP-9

BP-10

BP	Sev	Estado	Detalle
BP-1	HIGH	FAIL	Template compliance system.md contains only 'test only' — a placeholder with no substantive content. The principles template requires 7 mandatory sections: Identity, Voice, Flow, Calibration, Principles, Tools, and NO_RESPONSE. None are present. evidence (2) {'file': 'system.md', 'quote': 'test only'} {'file': 'templates/principles.md', 'quote': 'Prompt structure: 7 sections in `system.md` + `examples.md` ... Identity + Mission, Voice, Flow, Calibration, Principles, Tools, NO_RESPONSE'}
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/sensitive, re-engagement, off-topic) plus two conditional scenarios (keyword trigger in Example 7, price objection in Example 4). Total count is 15, within the ≤20 cap.
BP-3	HIGH	N/A	Examples align with the flow system.md is a placeholder ('test only') and contains no flow definition. Without a flow to map against, this rule cannot be evaluated. Once system.md is populated with a Flow section, this check will apply.
BP-4	CRITICAL	N/A	No internal contradictions in system.md system.md is a placeholder ('test only') with no substantive content. There are no rules to contradict. This check will apply once system.md is populated.
BP-5	CRITICAL	PASS	No cross-file contradictions Although system.md is a placeholder, examples.md, keywords.json, resources.json, program.json, objections.md, and knowledge_base.md are internally consistent. Examples demonstrate behavior (e.g., Example 1 shows presencial pricing, Example 11 shows online exterior pricing) that aligns with program.json pricing rules. Keywords in keywords.json (e.g., 'regalo', 'taller', 'parte 1') are demonstrated in examples.md (Examples 7, 2, 1 respectively). No file contradicts another under a shared precondition.
BP-6	MEDIUM	PASS	Voice consistency across examples All 15 examples use consistent voice: warm, direct, voseo (Argentine Spanish), minimal emojis (mostly 🙂, 🌿, ❤️), conversational tone, and similar message length. No jarring tonal shifts between examples.
BP-7	CRITICAL	N/A	Unguarded actions (PAT-004) system.md is a placeholder ('test only') and contains no flow steps or action instructions. Without a Flow section defining actions, this rule cannot be evaluated. Once system.md is populated, this check will apply to risky actions (sending links, qualifying, booking).
BP-8	HIGH	N/A	No stale version language in examples system.md is a placeholder with no flow definition to compare against. Examples cannot be checked for staleness without a current flow definition. This check will apply once system.md is populated.
BP-9	MEDIUM	PASS	No duplicated instructions system.md is a placeholder ('test only') with no instructions to duplicate. Knowledge files (objections.md, keywords.json, program.json, knowledge_base.md) each have a single canonical home for their instructions. No duplication detected across files.
BP-10	MEDIUM	N/A	Rule-vs-principle balance system.md is a placeholder ('test only') and contains no Principles section. This check will apply once system.md is populated with behavioral guidance (tone, flow, conversational style) vs. hard rules (facts, safety, compliance).

Checks determinísticos

Check	Sec	Estado	Notas
6a	1.8	PASS	NO_RESPONSE present (limits not checked, --no-db)
6c	3.x	PASS	2 lines
6d	1.2	PASS	15 examples
6e	1.3	N/A	no Principles section
6g	PAT-006	FAIL	keywords defined but no handling in system.md
6h	Anti-pat	PASS	no 'burbuja'
6i	Anti-pat	PASS	no HTML comments
6j	Anti-pat	PASS	no em-dashes
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: ['respiracion', 'sky']; (5 stale drift entr(ies) ignored — no recent digest mention)
6s	Hygiene	PASS	no expired dates in live SDK
6t	Coverage	N/A	no Principles or Flujo section found in system.md

canal — · sync 2026-09-28

344

Digests

4 en últimos 14d

Cambios pedidos / pendientes

del checklist

355

Threads

en el canal

2026-09-28

Última sync

del digest

Cosas nuevas (digests recientes)

Fecha	Tema	Tags
2026-09-28	weekly funnel report sep21 sep28	analytics, conversion, weekly-report, traffic-motor, keyword-performance
2026-09-21	weekly funnel report sep 14 20 conversion crisis	funnel-metrics, conversion, weekly-report, critical
2026-09-21	weekly funnel report sep14 20 zero confirmations	funnel, conversion, weekly-report, performance-drop
2026-09-14	weekly funnel analysis sep 07 13	conversion-funnel, analytics, follow-up-strategy
2026-09-07	weekly lead volume conversion plateau	analytics, conversion-metrics, lead-quality
2026-09-07	weekly performance spike lead volume	analytics, conversion, content-strategy, whatsapp-funnel
2026-09-04	whatsapp lead processing pipeline	leads, whatsapp, automation, deduplication
2026-09-03	database query security gate blocking lead alerts	alerts, automation, infrastructure, blocker
2026-09-02	whatsapp shared phone leads processing 2026 09 02	leads, whatsapp, automation, operational
2026-09-01	whatsapp shared phone leads processing sep 2026	leads, whatsapp, automation, ledger-maintenance
2026-09-01	whatsapp shared phone lead processing batch	leads, whatsapp, deduplication, data-ops
2026-08-31	weekly activity report event based conversions	reporting, conversion-analysis, content-strategy, events
2026-08-31	phone number timing funnel optimization	funnel, conversion, ux-flow, phone-collection
2026-08-31	whatsapp shared phone leads processing	leads, whatsapp, automation, ledger-management
2026-08-31	event focused traffic shift week aug25 31	content, conversion, keyword-performance, traffic-pattern
2026-08-31	weekly performance report aug25 31	reporting, conversion, volume, insights
2026-08-28	whatsapp shared phone leads processing aug 27 28	leads, whatsapp, automation, ledger-update
2026-08-26	whatsapp shared phone lead processing aug 26 27	leads, whatsapp, automation, ledger-management
2026-08-25	whatsapp shared phone leads processing aug 25	leads, whatsapp, deduplication, precalificacion
2026-08-24	new whatsapp lead nancymcataldo score 3	lead, whatsapp, phone-shared

Cambios pedidos por el creador / pendientes

ID	Estado	Cambio pedido
C9	pendiente	Si existe ultimo_pendiente → no saludar, retomar desde ese paso
C10	pendiente	Si pasan 12-48h y lead responde "hola/sí/ok" → no saludar, retomar último pendiente
F2	pendiente	Si contexto_previo=true → NO ejecutar M1 (saludo). Continuar desde ultimo_pendiente
Y4	pendiente	"Hola" y "Lucas AOL" tenían link presencial viejo `1ZodB7D` / ambiguo `1yFkCfx`

sentiment del cliente → Ninjo · scoreado ahora (2026-09-28 20:11:50) · modelo claude-sonnet-4-6 · ventana 7d

-1

Sentiment score

neutral_con_señales_de_desenganche

Alto

Churn risk

del lado del cliente

Cambios pedidos

pendientes en checklist

Volumen cliente

agente: 254 convs

Matriz de volumen

enganchado pero en distres

Cliente activo (volumen alto) pero con tono negativo: enganchado, riesgo está en el TONO, no en el silencio.

Sentiment del cliente

📋 El cliente (Maca Coronel / elartedevivir.ar) está en silencio operativo total desde marzo-abril: no responde encuestas, no interactúa en el canal de operaciones, y hay problemas técnicos no resueltos (payment link roto en agente 'Hola'). Todo el trabajo de los digests es producido por Ninjo/Cortex sin participación del cliente. Esto es desenganche pasivo de alto riesgo — no hay hostilidad explícita pero tampoco señal de vida. Acción urgente: contacto directo fuera del canal (llamada o WhatsApp a Maca Coronel) para verificar si el cliente sigue usando activamente la plataforma, detectar fricción oculta y reactivar el vínculo antes de que el silencio derive en churn silencioso.

Señal	Valor	Evidencia (cita del cliente)
Enojado con la plataforma	no	—
Es queja	no	—
Queja constructiva (accionable)	no	—

Evidencia citada

Señal	Cita textual	Fecha
Desenganche total del cliente rep: Maca Coronel no interactúa con el canal de operaciones desde su presentación	“None”	2026-04-06
Dos encuestas semanales consecutivas sin respuesta del cliente	“None”	2026-04-06
Canal de notificaciones sin actividad del cliente desde marzo	“None”	2026-03-25

Cambios pedidos por el creador (Métrica 1)

Un creador que pide cambios concretos está enganchado (mejor señal que el silencio).

ID	Estado	Cambio pedido
C9	pendiente	Si existe ultimo_pendiente → no saludar, retomar desde ese paso
C10	pendiente	Si pasan 12-48h y lead responde "hola/sí/ok" → no saludar, retomar último pendiente
F2	pendiente	Si contexto_previo=true → NO ejecutar M1 (saludo). Continuar desde ultimo_pendiente
Y4	pendiente	"Hola" y "Lucas AOL" tenían link presencial viejo `1ZodB7D` / ambiguo `1yFkCfx`