A single model cannot simultaneously answer the question of what the unresolved exposure operating loss is across the whole portfolio, which matters are drifting toward their statute of limitations, what the behavioural pattern in a given cluster predicts about escalation, and whether the reserve in a specific cohort reflects genuine liability or an information gap that targeted evidence provision could close. These are structurally different questions. They require structurally different engines.
CySive is not a single model. It is the architecture that governs the mosaic — assigning each question to the engine built for it, holding the canonical state that all engines read from, enforcing the doctrine that governs what can be recommended and by whom, and maintaining the audit trail that makes every output defensible under regulatory scrutiny.
UEOL
Unresolved Exposure Operating Loss
Net present value of unresolved liability across the entire portfolio. The balance-sheet number. Requires a discount rate engine and a reserve structure, not a language model.
SOL-001
Limitation Sentinel
Jurisdiction-aware, deadline-ranked surveillance of every open matter against its applicable statute of limitations. Operates continuously, not at strike dates.
BIM-009
Behavioural Intent Model
Pattern recognition across the full matter history. Detects performative resolve — the posture of apparent engagement that precedes a shift toward adversarial escalation.
EWM-007
Early Warning Model
Regime-shift detection. Identifies when the structural dynamics of a cluster have changed — before the reserve development makes it visible.
Blast Radius
Adverse Correlation Engine
Portfolio stress test. Correlated exposure simulation when a cluster liquidates adversely. The question every acquirer should be asking before they sign.
These engines share a canonical state. One versioned record of truth — the matter register, the exposure model, the change history — written only by the operator through deterministic process, never by inference. Every output is traceable to the state that produced it. Every change is logged. Every recommendation carries a confidence interval, an authority check, and a change set, before anything moves.
This is not a governance wrapper applied after the fact. It is the architecture. The doctrine is not a rule sheet. It is an executable constraint that runs before every recommendation leaves the system.
When a funder evaluates the book, they see one surface of the latent world. When the GC reviews the same matters, they see another — same underlying state, different utility function, different actionable view. When the regulator asks what was known and when, the audit trail produces a precise answer, not a reconstruction.
The institutions that manage liability at scale — a sovereign health body carrying tens of billions in clinical negligence provision that grows every year, the Lloyd's syndicates with decades of APH still emerging, the global carriers whose social inflation exposure has no formal model of why development is adverse — do not need a better prediction. They need an architecture that treats their liability estate as what it actually is: a dynamical world, with state, with actions, with governed transitions, and with a canonical record of every decision made within it.