Norden Intelligence System // reporting architecture under LFi
Norden is not the employer story. It is the evidence system that made a live clinic account readable.
Publicly, LFi keeps the client case, the intervention, and the professional proof. Norden keeps the operating layer built around that case: exports, cohort logic, reporting surfaces, and the split between internal reading, client reading, and printable delivery.
The value of this page is not that a clinic ran email. The value is that the account stopped being read as one blurred channel and started being handled as a system with evidence, boundaries, and decision consequences.
Exhibit / reporting registry
Narrative contract
This dossier only works if the split with LFi remains strict. Norden should never perform as an employer page, a disguised agency case study, or a fake product site.
LFi tells the client story and the career proof. Norden tells the system, the reporting architecture, the evidence chain, and the intelligence layer built around that story.
LFi dossier
Norden dossier
System mandate
The visible intervention starts on August 21, 2025 with 250820 Agosto #1. From that point,
the account stops behaving like one undifferentiated email stream. B2C and B2B need separate reading.
The active base becomes an operating object. Reporting has to explain the new logic, not just list outputs.
Norden exists because the account became too consequential to read with screenshots, memory, and ad hoc commentary. The problem was legibility.
Evidence chain
Norden deserves a separate dossier because the account was converted into a repeatable chain of evidence. The point is not the dashboard veneer. The point is the sequence from export to decision.
scripts/export_brevo_norden.py
Campaigns, segments, lists, account metadata, and schema land in dated local snapshots instead of floating inside platform memory.
config/case-context.json
The visible intervention point, audience split, reporting voice, and comparison windows are fixed explicitly before interpretation starts.
scripts/build_brevo_cohorts.py
Real opener sets are hashed with SHA-256 so recurrence, overlap, and rotation can be inspected without preserving raw contact PII.
scripts/build_norden_workspace.py
Internal reading, client reporting, printable output, and source documents are compiled from the same audited base instead of diverging into separate realities.
Reporting surfaces
The system matters because it can speak differently to different readers without changing the underlying truth. Norden is a translation layer with guardrails.
app/cliente.html
Executive Spanish reading with stage comparison, B2C/B2B separation, priorities, and next-step recommendations.
app/interna.html
Working layer for overlap logic, intervention framing, segmentation method, documentation, and attribution-safe interpretation.
app/printable/informe-ejecutivo-norden.html
Formal handoff for readers who need a static artifact instead of an interactive walkthrough.
docs/reports/*
Markdown evidence remains readable outside the interface, and downstream career extraction still belongs publicly inside LFi.
Cohort logic
The strongest operational value in Norden is not a pretty chart. It is the ability to tell who keeps returning, who rotates by theme, and who stays silent inside the active base.
Mainline window
The union of openers shows a stable repeat-opener pattern rather than one-off noise.
Expanded-base window
250826 Agosto #2The narrative holds even after the first visible base expansion, which keeps the system reading consistent.
Tactical 2026 window
Enough of the current active segment opened at least once to make cohort logic operationally useful.
Use for conversion pushes, agenda logic, continuity, and tighter cross-sell with fatigue control.
Use to form stable subsegments by interest instead of treating the whole active base as one block.
Keep inside the active universe, but lower the pressure and test softer re-entry routes.
Theme signals already visible in the rotative layer: Orthodontics 1,026, Sedation 944, Aesthetics/Botox 848, Benefits/Convenios 616, Prevention 549.
Reading split
The internal layer and the client layer answer different questions. What Norden prevents is a fork into two different truths.
Internal brief
Client brief
The printable executive report is the bridge: formal enough for circulation, grounded enough to remain tied to the same audited source base.
Closing memorandum
01This case shows an evidence architecture, not just campaign execution.
02It proves one source base can feed internal, client, and printable reporting without narrative drift.
03It demonstrates the ability to turn live operations into reusable decision support under delivery pressure.
Next useful expansion inside the workspace should deepen the evidence system, not simulate a product demo: segment membership snapshots, clicker-layer cohorts, and a claim-by-claim evidence matrix.
