01 Intake
Packet grouped
Broker email, slip, SOV, and loss history become one submission record.
ReRao Reinsurance OS
Risk work,beautifully clear.
ReRao turns broker submissions into cited, human-reviewed, audit-ready reinsurance packs—without asking teams to rebuild the file between intake, placement, operations, and diligence.
Source citations visible
Human approval gates
Audit-ready handoff
Broker control tower / agentic workflow
ReviewReadyPacketHuman-reviewed extraction
Northstar Property Treaty Renewal
Synthetic broker packet · cited facts · visible approval gate
6
proof events
3
field gaps
12
evidence spans
Inbound packet
broker-email.eml
Intent classified
submission linked
treaty-slip.pdf
Layer + limit extracted
p.2 cited
SOV-schedule.xlsx
TIV rows normalized
rows 2–84
loss-history.csv
Missing update
review routed
Agentic workflow
Six-step evidence gate
02 Extract
Facts structured
Cedant, treaty, limit, TIV, and exception fields gain confidence and citations.
03 Review
Exceptions routed
Missing loss history moves to the human review queue instead of being hidden.
04 Slip
Readiness visible
Draft language is prepared only after required facts and approvals are visible.
05 Approval
Human decides
Reviewer accepts, overrides, or requests follow-up before market handoff.
06 Audit
Evidence packaged
Events, source spans, decisions, and overrides remain inspectable.
Quote/slip send gateHuman approval required
Can I defend this file?
E&O ready
86%
Bind
Blocked
submission.received
4 source refs
review.required
loss-history gap
quote_slip.readiness
approval pending
Investor proof: agents prepare the file; humans keep authority; every decision keeps source and audit context.
Cinematic product proof
The file becomes the interface.
A premium workflow should feel calm: the packet enters, evidence is cited, humans decide, and the handoff carries its own audit memory.
Submission review desk
Broker submission review pack
ReRao broker workflow: an inbound broker email and supporting treaty files are grouped into a submission packet, structured extraction surfaces cedant, treaty, limit, TIV, exposure, and exception fields, a human review gate accepts or rejects facts, and evidence remains attached to the audit record.
One continuous record
From inbox to audit, without translation loss.
The signature is not a dashboard. It is a living review pack that keeps provenance, authority, and handoff context together.
01
Intake
The packet arrives whole.
Broker email, slip, SOV, loss history, and bordereaux stay attached to one operating record.
02
Evidence
Every fact shows its source.
Limits, exclusions, TIV, appetite signals, and open questions point back to page, row, and file.
03
Authority
Humans remain visibly in control.
Reviewers accept, override, or route exceptions before quote-slip readiness or market handoff.
04
Handoff
The audit trail travels.
Placement, operations, diligence, and model-risk teams inherit the same cited record.
Operating lanes
Built for the whole value chain.
Intake
Capture submissions without losing source context.
Broker emails, slips, schedules, and bordereaux enter one operating record with provenance visible from the first review.
Broker teams
Broker intake target workflow
Evaluate
Let agents prepare the work, not decide it in secret.
Extraction, appetite, and exception agents surface confidence, source coordinates, and missing evidence for human review.
Agents and reviewers
Repo-backed extraction and review services
Place
Coordinate market movement around the same record.
Quote context, deal-room activity, and market responses stay connected to submission evidence and authority state.
Brokers and markets
Deal-room and quote-slip app surfaces
Govern
Export a record that can survive scrutiny.
Human overrides, generated outputs, evidence bundles, and audit posture remain explicit for operations and model-risk review.
Operations and risk
Audit evidence bundle design
Quiet proof
Premium means not overclaiming.
Every public claim keeps maturity, provenance, and review boundaries visible. That restraint is what makes the product feel trustworthy enough for regulated work.
available
Source-grounded work
Every surfaced field points back to the document, schedule, or event that produced it.
Extraction confidence and broker review services
available
Human authority
Review gates keep acceptance, override rationale, and authority visible before downstream handoff.
Broker review completion and slip readiness endpoints
preview
Sovereign posture
Sensitive evaluations can be scoped against cloud, controlled-environment, and data-residency constraints.
docker-compose.sovereign.yml
preview
Open integration surface
API contracts, signed webhooks, and core-system targets are labeled by maturity instead of implication.
OpenAPI and webhook routers
Trust surface
Enterprise controls, presented calmly.
Security, isolation, integrations, and deployment posture are shown as inspectable surfaces—not hidden behind enterprise adjectives.
Row-level isolation
Tenant access is enforced at the database boundary, not only in application filters.
Audit evidence
Per-submission evidence bundles keep agent and human decisions reviewable.
SOC 2
Public copy must state audit status rather than certification completion.
Integration surface
Connectors with visible maturity.
Clerk SSO
availableOrganization-scoped auth with SAML/OIDC support through Clerk.
Postgres RLS
availableTenant isolation enforced at the database layer.
Email ingestion
previewInbound email stays in design-partner framing until automatic submission creation is verified end to end.
Signed webhooks
availableOutbound events are framed as an evaluation integration surface with signature and delivery semantics.
Design-partner evaluation
Bring one real packet. See the whole record.
Start with a scoped evaluation across broker intake, placement handoff, operations, audit evidence, or sovereign deployment.
Evaluation path
1cited operating record
4visible workflow gates
0black-box authority claims