Regulation-traceable rules
Every compliance control carries its authority, applicability, tests, and effective dates, so any past decision can be replayed against the exact rule version that produced it.
Every compliance control on the platform carries its own authority, the conditions under which it applies, the tests it runs, and the dates it was in force — so a decision made eight months ago can be replayed against the exact rule version that produced it, rather than against today’s.
“Block after seven calls”
- Whose calls, and about which debt?
- How is the window rolled, and what are its exceptions?
- Do state overlays change it?
- Is seven a legal presumption or a stricter lender policy?
A regulation-traceable rule
- Names its authority and its approvers
- Declares who, where and when it applies
- Declares the facts it needs, and their freshness
- Carries an effective interval and a test pack
Nine attributes, and the logic is one
Each one answers a question the condition alone cannot:
| Attribute | Purpose |
|---|---|
ruleId and version |
Stable identity for decisions, tests, and change history. |
| Authority | Statute, regulation, order, consent term, contract, or approved lender policy. |
| Applicability | Actor, product, debt, customer, jurisdiction, purpose, channel, and action. |
| Effective interval | Which version resolves at a specific time. |
| Required facts | The exact inputs it needs, how fresh they must be, and where they may come from. |
| Logic and exceptions | Deterministic condition and explicitly modeled exceptions. |
| Outcome | Pass, warning, approval, block, or missing-facts behavior. |
| Owner and approvers | Compliance/legal owner and separation-of-duties evidence. |
| Test pack | Boundary, exception, conflict, stale-fact, and historical replay cases. |
Applicability before strictness
Federal, state, contractual, and lender-policy rules do not always combine by selecting the numerically “strictest” threshold. The engine first resolves which rules apply and how counsel-approved conflict policy composes them. A state rule may be additive, preempted, actor-specific, product-specific, or triggered by a different fact.
action + actor + debt + party + jurisdiction + channel + purpose + time
↓
applicable rule set
↓
exception and conflict resolution
↓
aggregate outcomeA new version never rewrites a past decision
Historical explanation replays the exact rule version, facts, and clock available then. Judging last year’s call by this year’s rule answers a question nobody asked and cannot answer the one an examiner actually puts, which is whether the platform followed the policy that was in force. Future-dated versions can be tested in shadow without affecting live actions.
Six stages, and retired still replays
The test pack every rule version carries
Each version carries fixtures for one unit below, at, and one unit above boundaries; daylight-saving transitions; missing and stale facts; exception eligibility; multiple debts; state/federal overlays; superseded consent; and historical replay. Compliance rules fail at their edges rather than in the middle — the seventh call, the hour the clocks change, the fact that arrived stale — and a rule proved only on the obvious case has been tested exactly where it was never going to break.
The trace cites authority, not advice
The owning operation retains its immutable decision and rule trace in the evidence chain and applicable reports, so the explanation survives the request that produced it. GET /v1/servicing/compliance/decisions/{decisionId} exposes that trace directly, including jurisdiction and effective version. It cites the authority configured for the tenant and does not present LendEasy’s output as legal advice.