---
id: ADR-MBR-MEM-019
title: Use the Shared Review Engine
product_area: membership
module: memberships
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Submissions owns answers, review and decisions; Membership stores a typed
  request and applies delivered outcomes through its registered subjects.
constrains:
  - DOM-MBR-MEM-004
  - SVC-MBR-MEM-applications
  - STATE-MBR-MEM-006
  - WF-MBR-MEM-016
origin: >-
  The lifecycle and commerce chapters (applications live in the Submissions
  engine), and the Submissions engine's decisions D-09 and D-10 as the
  application vocabularies cite them
alternatives:
  - option: Membership's own application review states
    why_not: >-
      Independent review states would duplicate the authoritative engine
      lifecycle.
  - option: No Membership record at all
    why_not: >-
      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.
supersedes: []
evidence:
  - >-
    services-membership at 5994c270: modules/applications/**;
    docs/migrations/participant/README.md
---

# 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.