Methodology

A forensic doctrine, not a prompt.

LUMEN does not “ask an AI what it thinks” about a company. It runs a proprietary doctrine — sequential passes, batteries of checks with calibrated thresholds, per-deliverable procedures — and uses the model as a disciplined executor. Here we tell the architecture; the thresholds, the weights and the procedures remain LUMEN\'s craft and never leave the server.

The passes — from data honesty to the final file
PASS 0
Perimeter and honesty

What data is actually there? Available years, freshness, source tier (data room > filed accounts > public), automatic FI detection (banks/insurers switch battery and metrics). If the data is not enough for the requested mode, LUMEN says so here — before analyzing.

PASS 1
Reconstruction

The numbers: income statement, balance sheet, cash flow, multi-period. Every load-bearing number enters with the [SOURCE | DATE | NATURE] tag; your providers' market data enters marked [MKT] with a timestamp.

PASS 2
Forensic hunt

The D (cash/accounting), F (notes and footnotes) and PW (warning patterns) batteries run on the reconstructed numbers. Every check that fires carries severity, evidence and its OWN falsifier.

PASS 3
Convergence and verdict

The fired checks are read by cluster; the dominant mechanism emerges — the simplest explanation that holds the anomalies together. PURSUE/DECLINE/BIFURCATED verdict with a GREEN/AMBER/RED band, conviction and overall falsifier.

PASS 4 + EXP
Deliverable

The verdict becomes the requested document: the chosen deliverable's procedure (one for each of the 69) dictates structure, depth and style. With a Slot B, LUMEN mimics YOUR internal format.

PASS 5
Extraction and contract

The load-bearing numbers are locked into a single-source contract: Excel, deck and report read from the same values. If a number does not tie across the views, the run stops and declares which one.

Not every deliverable runs every pass: a tearsheet makes 3 calls, a full diligence 6. The exact sequence is decided by the deliverable — and the progress bar always shows the real passes, never an estimate.

44+13 checks that never sleep
D1–D13
Battery D — cash does not lie

Cash conversion, working capital, DSO/DIO/DPO, capex vs depreciation, recurring one-offs, interest coverage, covenant headroom. Where book earnings and cash diverge, the real story is almost always there.

F1–F21
Battery F — the notes at the back

Reverse factoring, aggressive capitalizations, related parties, channel stuffing, gains in EBITDA, auditor and policy changes: the forensic hunt in the notes to the accounts, where the surprises are buried.

PW1–PW10
Battery PW — the warning patterns

Guidance shifted to H2, insider selling, CFO turnover, call language, consensus drift: the behavioral signals that precede the numbers.

FI1–FI13
Battery FI — banks and insurers

CET1, NPL and coverage, NIM, LCR/NSFR, cost of risk, Texas ratio, Solvency II, combined ratio: when PASS 0 detects a financial intermediary, EV/EBITDA steps aside and the regulatory battery steps in.

Every fired check comes out with severity, cited evidence and a falsifier. The checks are read by cluster (cash/accounting · narrative/credibility · insider/structure): it is the convergence between clusters, not the single alert, that moves the verdict.

The pact with the reader

Every verdict is falsifiable. It always comes out with the observable condition that would disprove it — a number, a date, a source. If the falsifier fires, the verdict changes: it is the opposite of a horoscope. The TRACKREC ledger keeps the issued verdicts, the hits and the misses, viewable in the platform.

What we do not know is written down. Unverifiable data stays marked [NV] in every view; every report closes with the diligence agenda: what is missing, what is not verifiable, what to ask management. An analysis that declares its limits is worth more than one that hides them.

The numbers do not contradict each other. The load-bearing values are locked into a single-source contract: the Excel, the deck and the report read from the same numbers. If something does not tie, the run stops and says which number does not add up — it does not deliver a wrong file.

What it is built on
Proprietary doctrine

The LUMEN doctrine is a proprietary body of valuation, forensic-accounting, M&A and credit methodology, distilled into operational cards injected into the passes that need them.

Real forensic cases

The batteries' thresholds and patterns are calibrated on documented cases (Bio-On, Carillion, Wirecard and others): every check exists because someone, somewhere, lost money.

Standards and regulation

IAS/IFRS (IAS 7 44F-H on reverse factoring, IAS 24 on related parties, IAS 38, IFRS 15), bank prudential requirements, Consob practice: the checks cite the standard that grounds them.

Data with provenance

Market and consensus come from YOUR providers (FMP, FRED, Alpha Vantage, FactSet, Bloomberg DL) and enter marked [MKT]/[CONS] with source and date. The engine's web research numbers the sources and declares the stale ones.

The harshest way to judge a methodology is to read its output.
Open the Wirecard example →Sign in