Component templates¶
Reusable building blocks that products assemble: cover, benefit, rider, fee, waiting period, etc.
A generic template captures shared behaviour. A line-of-business template (e.g. funeral) specialises the same shape with different defaults and validation — still one runtime, different published data.
Status¶
🟡 Example definitions below — schema and publish workflow planned (phase A — P1)
Core fields (v0)¶
Every component template carries at least:
| Field | Purpose |
|---|---|
componentCode |
Stable identifier in Product Studio and on hydrated snapshots |
componentDescription |
Human-readable label for channels and ops |
componentType |
Archetype — maps to runtime ComponentType (e.g. RISK_FUNERAL) |
escalationMethod |
How benefit or premium escalates over time (none, CPI, fixed %, age-band) |
recurring |
Whether the component bills on a repeating cycle (true / false) |
More attributes (waiting period, sum assured rules, decision pack refs) will be added as templates mature.
Example — generic cover component¶
A minimal template any product can reuse or extend:
{
"componentCode": "COVER-GENERIC-01",
"componentDescription": "Generic risk cover component",
"componentType": "RISK_LIFE",
"escalationMethod": "NONE",
"recurring": true
}
At quote time, Quantum-Tree hydrates this into a CoverComponent on the contract snapshot. Kinetic reads recurring and escalationMethod from behaviour bindings to schedule milestones.
Example — funeral component¶
Same machinery, funeral-specific defaults — no separate funeral engine:
{
"componentCode": "FUNERAL-FAMILY-01",
"componentDescription": "Family funeral benefit — main member plus dependents",
"componentType": "RISK_FUNERAL",
"escalationMethod": "CPI",
"recurring": true
}
| Field | Funeral example | Notes |
|---|---|---|
componentCode |
FUNERAL-FAMILY-01 |
Unique within the product catalogue |
componentDescription |
Family funeral benefit… | Shown on schedules and channel UIs |
componentType |
RISK_FUNERAL |
Aligns with ComponentType in Quantum-Tree |
escalationMethod |
CPI |
Annual benefit escalation via Kinetic + decision pack |
recurring |
true |
Monthly premium cycle |
Escalation methods (draft)¶
| Value | Meaning |
|---|---|
NONE |
Flat benefit and premium for the life of the contract |
CPI |
Escalate by consumer price index (decision pack supplies rate) |
FIXED_PERCENT |
Fixed annual percentage increase |
AGE_BAND |
Step change at defined ages |
Component types (runtime)¶
Templates reference the same enum the contract engine uses today:
componentType |
Typical use |
|---|---|
RISK_LIFE |
Term life, whole life |
RISK_FUNERAL |
Funeral and burial benefits |
RISK_CREDIT_LIFE |
Credit-linked cover |
RISK_DISABILITY |
Income protection |
RISK_CRITICAL_ILLNESS |
Dread disease |
ASSET_* / TRAVEL |
Non-life lines |
Related¶
- Product definitions — how templates are assembled into a product
- Behaviour bindings — escalation and recurring drive Kinetic milestones
- Capability matrix — P1
- Quantum-Tree — where hydrated components live at runtime