Platform · How you use it
A worked example on a single contract — yearly renewable term.
Start with premium and commission →AI agent
The agent understands the input you’re working on, advises how you should do it, and helps check for errors. It also knows the manual and your outputs, and explains results. For any input, open an agent focused on just that input.
Inputs are entered through the interface today.
You work an input · the agent advises, helps check, and explains
Beat 01
Yearly renewable term, one contract. You declare; uModel handles — and why.
You declare three items, each with its type.
Nothing automatic yet. The data is ready for the next declarations.
You declare AttainedAge, with its type. Its script:
// → AttainedAge IssueAge + ContractYear
Supplies ContractYear. AttainedAge steps up as ContractYear advances, and the premium rate steps up with it.
because of its formula, and the table’s AttainedAge index
You declare the tables and name the indexes. PremiumRate is annual premium per 1,000, by AttainedAge and Gender. CommissionRate is by policy year: high in year 1, renewal after.
Lookups use this contract’s own values.
because of the table’s declared indexes
Commission drops to the renewal rate at the first anniversary.
because of the policy-year index
A script uses a table by its name alone. No keys passed.
Change the rates, and every script that uses that table follows. None of them is edited.
You declare Premium (cash income) and Commission (cash expense), a contract worker, and two scripts:
// → Premium FaceAmount / 1000 * PremiumRate / 12
// → Commission Premium * CommissionRate
FaceAmount, and the premium with it, falls as policies leave the in-force.
because of its type
Mortality and lapse are set up once, elsewhere.
AttainedAge → Premium → Commission: each runs after what it reads.
because of order from dependencies
Beat 02
You said what each number means. uModel puts it on the statement.
You declared Premium as cash income and Commission as a cash expense.
Places them in the income statement — Premium as revenue, Commission as an expense.
because of their accounting meaning
| Line | Type | Period 1 | Period 2 | Period 3 |
|---|---|---|---|---|
| Premium | Revenue | — | — | — |
| Commission | Expense | — | — | — |
| Net | — | — | — | — |
Beat 03
Pick the basis for a run. Assign a different accounting interpretation and run again — the model doesn’t change. A run is configured with one basis at a time. The platform does not know any reporting framework — a basis is a name you define. Whatever differs between bases lives in your model.
One basis per run. Assign a different accounting interpretation, run again. Same model.
Beat 04
Each contract is projected individually, aggregated into journals, and rolled up for higher-level calculations.
Audit a single contract to review the details.
Next
A Finding already shows a full-fund seriatim run on a desktop. The progress table shows where each part stands.
The engine runs today; the platform around it is being built in the open. Occasional notes, no spam.