05 — Parties
Summary
Issuer, policyholder, insured, approver, maintainer, auditor — each mapped to a responsibility that exists today (the project lead, the estate, the site agent) and each with the runbook a session executes and the prevention the key topology will impose. The pilot lifts the prevention on the project lead's word: one session may run any role, the same hand may ask and answer under two hats, and the record names both. What that costs is stated: every acceptance in the pilot is self-accepted, which the economics say a draw must never be; the acceptor is still named as the policyholder so the record is right even when the hand is the same. Experience rating lands on the policyholder because the session is indifferent to the loss.
Key concepts
- Prevention deferred, not dropped — roles as runbooks until the key split
- The acceptor is the policyholder — the agent spends, the team carries
- Never approve an exclusion — the answer to an escalation is acceptance as uninsured or suspension, never a larger draw
Key ideas
- The RiskMandate team holds the instance a policy is written against and is not a party to the policy.
- A session-held enumeration key is a session-scoped identity, which the registry pack already found to be the wrong lifetime.
Read the document
📄 Pack document · 05__parties.md · rendered from the raw markdown (the source of truth)