Rule Use

What It Models

A rule use applies shared qualification logic to a particular application decision.

Identity and Attributes

It combines the consumer reference, release selection, parameters, uncertainty policy and availability.

Relationships

Eligibility owns the connection; the consuming application retains its own business record.

Invariants

Compatibility is a service check, while uniqueness and pin shape also have database constraints.

How It Is Stored and Shared

Eligibility stores uses and plans. Applications call its evaluation and binding contracts; neither record declares custom fields.

Open Design Questions

Changing products between rules is not atomic in the current browser orchestration, and ownership checks on the consumer record remain a planning disagreement.