What ships

• Transaction and Tranche — the issuance and its classes of notes as typed data: issuer, sponsor, perils, trigger, risk period, and per class the notional, expected loss, guidance and rating. Sponsor, broker, currency, perils and regions are node-path references into Reinsurance.
• Mandate — the investment guidelines AS DATA: eligible perils, currencies and triggers, the EL ceiling, the multiple floor, the concentration cap, the ticket ceiling. The module ships one; a deployment authors its own.
• Screening, Analysis, Recommendation — decision preparation as three records: the mandate checks with what was observed against what is allowed, the scored risk–profitability quadrant, and the drafted invest and pass cases with proposed terms.
• Decision — the guarded decision: approve with amount, spread floor and rationale; decline with a reason; defer with a date. Every revision is recorded with its stated reason, and the context it was taken under is stamped.
• Order and Allocation — the broker order drafted from the decision (Draft → Approved → Sent → Acknowledged) and what came back, through to the settled position.
• Journal — the append-only log of every step on a tranche.
• Pipeline — the desk: the board of every tranche by stage with its next step and deadline, the decision log and the order register — derived live, stores nothing.
• Ingestion — the intake: drop a broker pack (announcement, transaction and spreads CSVs, year-loss table) and ingest it into typed nodes, idempotently.

The module family

The core is the decision process. What surrounds it ships as separate, generic modules that read and write each other by node path only:

• Portfolio — the held book, marks, NAV and reporting for any asset class.
• PortfolioOptimization — RoRAC over loss tables, marginal analysis and pipeline ranking.
• EventMonitoring — peril events, industry losses, climate and market regime.
• TaskManagement — work items and the team.

Contents