CLIENT ROOM Upload · Pick branch · Run · Report

One door for KOKON forensic + diagnostic analysis

◇ Doctrine ◇ Trap coverage ◄ Mission Control

1 · Client

Pick an existing client or type a new name. New names auto-register on first RUN — no separate onboarding step.

2 · Client data

Upload the client's raw data. Paste JSON, upload a file, or run against a KOKON fixture sample. This handler captures the payload for provenance and dispatches to the branch-specific pipeline. S3 direct ingest is planned (INTAKE-2).

Paste JSON

Upload file

Sample fixture

.json / .zip / .csv accepted. Chain-of-custody records the SHA-256 of the uploaded bytes.

Run the branch against the sealed KOKON fixture data (byte-deterministic reference clients). Useful for smoke-testing the flow before a real client upload.

Use fixture (recommended for first run)

3 · Branch · what to analyse

Loss / hidden risks

Where is the company bleeding money, time, or hidden risks?

Fires the full doctrine ensemble across earnings quality, services P&L, peer ratios, framework normalisation, cross-border tax, consolidation, capital & liquidity, network / contagion, distress composites, governance, macro, and leak audits.

Cases: APEX · SERVICE · OMNI · SPECTRUM · GLOBAL · CASCADE · PILLAR · NEXUS · TRINITY · SENTINEL · ATLASM · AURELIA

AML forensics

Money-laundering, financial-crime, sanctions

Fires the AML detector family (structuring, mandate-aggregate, bridge) plus the governance overlap for related-party / control-environment evidence. Surfaces adjacent lanes for sanctions screening + crypto forensics.

Cases: MERIDIAN · SENTINEL · plus /ui/ofac-sdn + /ui/phase541

4 · Run

Ready · pick client + branch, then hit run

5 · Report

Client

—

Branch

—

Cases fired

—

Verdict

—

Findings total

—

Case	Layer	Verdict	Recall	FP refused	Indet	Findings	Sample findings

—