Regulation-traceable rules

Version each compliance control with authority, applicability, facts, exceptions, outcome, owner, tests, approval, and effective dates—without encoding legal judgment as anonymous conditionals.

A useful rule explains not only what it does, but why it applies to this action. “Block after seven calls” is not a complete rule; it omits actor coverage, particular debt, rolling-window definition, exceptions, state overlays, and whether the threshold is a legal presumption or a stricter lender policy.

Rule anatomy

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	Typed inputs plus freshness and provenance requirements.
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 outcome

Effective dating

Publishing a new version never rewrites a past decision. Historical explanation replays the exact rule version, facts, and clock available then. Future-dated versions can be tested in shadow without affecting live actions.

Change workflow

LifecycleCompliance rule version

DRAFTauthority and applicability authored

VALIDATEDschema and complete test pack pass

APPROVEDnamed reviewers accept version

SCHEDULEDeffective time and rollback ready

ACTIVEresolves for in-scope actions

RETIREDhistorical replay only

ACTIVE→SUSPENDEDkill switch stops new resolution

SUSPENDED→ACTIVEapproved remediation

Testing standard

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. A rule cannot activate with only a happy-path example.

Decision explanation

GET /v1/servicing/compliance/decisions/{decisionId} returns the immutable rule trace, including jurisdiction and effective version. It cites the authority configured for the tenant but does not present LendEasy’s output as legal advice.

LendEasy supplies a rule framework and reviewable starting content. The lender remains responsible for determining legal applicability, approving policy, validating outcomes, and monitoring regulatory change with qualified counsel.