Use the Shared Review Engine

Context

Membership requests can need review, and Submissions already owns forms and stages. Membership retains the purchase and coverage facts needed to act on delivered results.

Decision

Submissions owns answers, review and decisions; Membership stores a typed request and applies delivered outcomes through its registered subjects.

Alternatives Considered

Membership's own application review states: Independent review states would duplicate the authoritative engine lifecycle.

No Membership record at all: Without a typed record, Membership would lack selected offers, chapters, seats and resulting order references.

Consequences

The current intake gap means imports establish typed applications. Checkout review requirements use the process flag rather than examining engine stages. Window, eligibility and outcome parameter settings are not executed by the active decision path.