Insurance · the blueprint in detail
The blueprint, layer by layer
Which systems fill each layer, which of them we bring already built, and the route an agent has to take to reach any of them.
Pick the shape you are, and point at anything
The order of the layers is fixed. What stands in them is not. Point at any block for the reason it is there, and point at an agent to see the route it takes: out of the agent, through the ontology, through the gateway, and only then into a system of record.
Delegated authority, several programs at once, thin IT. The accelerators are the core, because there is rarely much underneath to preserve.
The people
who the work is for
Insideyour payroll
Underwriters · Program managers · Servicing · Claims · Finance · Compliance
Outsidewho you trade with
Brokers and agents · Program partners · Capacity providers · Insureds
Federated identity, scoped by entitlement to the programs they are appointed on.
Accountablewho answers for it
Platform team · Security · Internal audit · Your regulator
They read the same audit trail everyone else writes to.
Identity
one way in, people and services
same in every deal
An agent gets its own identity, not a person's. Provisioned, scoped and revoked like any other principal, so “which agent did this, under whose authority” has an answer that does not depend on whose session it borrowed.
Where the work happens
three peers, any of which can call the others
varies by segment
Workspacespeople inside
reached over REST
Agents live inside these too: a copilot in the bench is the same agent, reached from a screen.
Portalspeople outside
reached over REST
External identity is federated and scoped by entitlement, so a broker sees only the programs they are appointed on.
AgentsLLM-powered software that takes action
reached over MCP
At its authority limit an agent stops and hands the decision to a named person, with the reason attached. People ask agents for things; agents ask people to decide.
Ontology
the domain model: your entities, and the authority rules on them
same in every deal
A workspace renders from it, a portal is scoped by it, and an agent decides with it. Every agent resolves against it before the gateway sees the call.
Integration and policy gateway
governance and observability, in one place
same in every deal
Governance
- Authorization on every call, people and agents alike
- Authority limits taken from the binder
- Approval gates on defined actions
- Least privilege per operation, not per system
- Reversible: every write has an undo path
Observability
- Immutable audit of every action, whoever took it
- Tracing end to end, request to system of record
- Metrics, alerting and health per operation
- Exported to your SIEM, retained to your policy
- Prompt and response kept with the action
Reached two ways, governed one way. MCP for agents, so a model calls a tool that already contains the limits. REST and events for portals, workspaces and systems you already run. Both land on the same authorization and the same audit trail.
Systems of record
each slot is a choice, and we arrive with a recommendation
varies by segment
Canonical data layer
one model the whole book reconciles against
same in every deal
Point at any block, or tab to it, and the reason it is there shows up here: what it does for an MGA, and which option we would put in that slot. Point at an agent and its route is drawn, through the ontology and the gateway.
What the blueprint is designed around
Four properties of the architecture rather than features of any one system, which is the difference between a stack built for insurance and a stack that happens to hold insurance data.
- A regulated business
- Nothing reaches a system of record except through the gateway, so identity, authority limits, approval gates and an immutable audit trail belong to the architecture rather than to whichever system was bought last. When someone asks who changed a bound policy and on what authority, the answer is one query rather than a week of reconstruction.
- Delegated authority
- A binder fixes who can bind what, up to which limit, in which territory. Encoded at the gateway rather than remembered by people, a referral becomes an exception with a reason attached instead of a queue in someone's inbox.
- One identity, for people and agents
- SSO, SCIM provisioning and your own identity provider for the people. Service identities for the agents, one each, provisioned and revoked like any other principal, so an agent never acts on a borrowed session.
- Systems you cannot replace
- The core row is the part that varies. A policy system that has run for twenty years stays where it is, reached through the gateway like everything else, and can be swapped later without the layers above it being relearned.
Want this drawn against your own estate?