Everything the engine can do

Eligibility & rating logic

What a single rule can express.

Eligibility conditions

• Nested AND / OR / NOT. arbitrarily deep condition trees, not a flat list of checks.
• Full comparison set. ==, !=, >=, >, <=, <, and in (list membership against an array) on any field.
• Raw expressions. arbitrary arithmetic/logic for the rare case the visual builder can't express.
• Composable rules. a condition can reference another one of your eligibility rules by id instead of duplicating its logic — expands inline in the trace, not just a name to look up separately.

Rating factor kinds

• Flat. a fixed multiplier or addend.
• Condition-based. applies only when a condition passes (e.g. a bundling discount).
• Table lookup. exact-match or numeric range, with optional linear interpolation between bands.
• Tiered / bracket. a progressive charge across brackets of a basis value (e.g. layered limits).
• Deductible curve. a factor read off a curve of deductible-to-factor points, step or interpolated.
• Raw expression. a factor's value computed from a formula, for anything the structured kinds can't express.
• Rule composition (rating_ref). compose another rating rule's own computed amount into this one.
• Accumulators. a persistent, cross-call running total — e.g. how much of an annual deductible has been paid so far.
• Reinsurance layers. excess-of-loss attachment point + limit, composable into a full layered tower.

Calculation correctness

• Effective-dating, region, and product-type scoping. one rule id can have multiple versions; the most specific match is selected automatically.
• Multi-line-item and multi-entity rating. rate a bundle of items, or the same rule across several members, in one call.
• Mid-term pro-ration. built in, not something you compute separately.
• Configurable rounding. half-up, half-even, or truncate, with per-region overrides.
• Exact decimal arithmetic. never floating-point rounding errors on money math.

Safety & governance

• Full evaluation trace on every call. not just a pass/fail or a number — a complete, nested explanation of exactly how each condition and factor contributed, suitable as an audit trail for a regulated industry.
• Loud failure. a calculation error surfaces immediately, never a silent default.
• Load-time and activation-time validation. overlapping effective-date/region/product versions of a rule are rejected outright.
• Semantic lint checks. dangling table references, unused tables, no-op factors, out-of-order brackets, and likely-negative amounts are flagged before deployment.
• Input schema validation. checkable before rating ever runs, not discovered at call time.