Pricing governance breaks when model logic and production versions live apart.
Actuarial and product teams cannot control pricing confidently when assumptions, formulas, tables, approvals, and live calculations cross tools without a shared version history.
Models, rate tables, review states, published versions, and calculation traces can remain part of one governed pricing record.
The work should carry its reasoning forward.
Inputs become decisions, exceptions remain visible, and the evidence behind the outcome travels with the output instead of being reconstructed later.
Inputs
- Exposure fields
- Actuarial assumptions
Decisions
- Formula logic
- Rate selection
Exceptions
- Model referral
Evidence
- Calculation trace
Outputs
- Published price
Pricing model and version
A published pricing version retains the logic and inputs behind each result.
| Record | Role in the work |
|---|---|
| Model input | Every pricing input records its source, type, validation, and effective value. |
| Calculation node | A named formula exposes how intermediate values contribute to the final premium. |
| Rate table | The selected table retains its version, effective dates, and matching dimensions. |
| Trace output | The completed trace explains the inputs, rules, tables, and rounding behind the price. |
Review a pricing model with AllegoryOS and see how its logic can remain governable in production.
Bring the work as it operates today. We will trace its inputs, decisions, exceptions, evidence, and outputs together.