Rhythm 2.0 Specifications

Appearance

CAP-MBR-MEM-011Define what applications are for and read the applications

Markdown

CAP-MBR-MEM-011

Define what applications are for and read the applications

Markdown
  • DocumentDraft
  • Product intentConfirmed
  • ImplementationPartially observed

Planning

Feature
FEAT-MBR-MEM-04
Key concepts
CON-MBR-MEM-004
Actors
ACT-MBR-006, ACT-MBR-007, ACT-MBR-009
Journeys
JNY-MBR-MEM-003
Related
CAP-MBR-MEM-012, CAP-MBR-MEM-009, CAP-MBR-MEM-015
Proved by
ATS-MBR-MEM-011

KindCapabilityProduct areaMembershipModuleMemberships, Applications and Membership BillingRevision1

Read atservices-membership 5994c270react-console baf6dae3

Define what applications are for and read the applications ​

Purpose ​

Some associations review people before they may join, renew or change chapters. The review itself happens in the Submissions engine. Membership must know what each application process decides, and must let staff see the applications behind their members.

How It Works ​

An administrator records an application process for a program. It names the operation the process decides, the packages it offers, the membership outcome an approval drives, the engine's definition, and whether applications are reviewed. A window, an eligibility binding and outcome parameters may be stored. A version-checked process update retains omitted fields and retains offered packages when their list is omitted. Staff read applications page by page, and officers see only those whose membership is in their units. An application of a person who is not yet a member is visible only to workspace-wide staff. Membership creates no application itself: the engine's intake is not connected yet, so today applications exist only through an import. The product should make a closed process refuse applications and should apply its eligibility binding; today nothing reads either.

Relationships ​

  • Related to CAP-MBR-MEM-012 because the process decides what a delivered decision does.
  • Related to CAP-MBR-MEM-009 because a reviewed process makes a purchase wait for approval.
  • Depends on the Submissions engine (MOD-SUB-SUB) for intake, review and decisions.

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes
Each reviewed path to membership is tied to the operation and packages it governs.Applications are visible to the staff and officers who may see the membership they concern.
Surfaces
consoleapi
Constraints
A process name is at most 200 characters and offers at most 50 packages.
Intent sources
services-membership:README.md#2026-10-18 — Final acceptanceservices-membership:docs/migrations/membership-core/README.md#Tables and migrations

Controls

37 controls apply, from the corpus control catalogue.

TC-AVL-002 TC-AVL-003 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-007 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PRV-001 TC-PRV-002 TC-SEC-001 TC-SEC-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004

Permissions

KeyChecked atScope
membership.configuration.readapitenant
membership.configuration.manageapitenant
membership.members.readapirecord

Business Rules

8 rules, 7 to be proved before approval. A rule's product intent is derived from its origin: 8 confirmed by a product decision, the rest inheriting this capability's confirmed.

IdRuleKindEnforced atProvenance
01must prove
Confirmed
An application process names its kind (enrol, renew, reinstate, rejoin or change of chapter), its program, the packages of that program it offers, the membership outcome it drives, the Submissions definition it runs on, and whether its applications are reviewed, which is the default.
no proof recorded yet
validationapi, servicetest
services-membership:tests/acceptance/commerce/MBR-ACC-0346.acceptance.ts#MBR-ACC-0346
02must prove
Confirmed
A process's window cannot close before it opens, and each offered package must be a package of the workspace and of the process's program; each refusal names its field.
no proof recorded yet
validationservice, databasetest
services-membership:tests/e2e/database-refusals.e2e.spec.ts#refuses a package of another program 400 naming package_ids[0] and the program
03must prove
Confirmed
A process's outcome parameters hold only the outcome's effective timing and a package override, at most 2 KB.
no proof recorded yet
validationservice, databasetest
services-membership:tests/acceptance/commerce/MBR-ACC-0347.acceptance.ts#MBR-ACC-0347
04must prove
Confirmed
The list of processes answers each with its offered packages in order, exactly as reading the one process does.
no proof recorded yet
policyservicetest
services-membership:tests/e2e/application-processes-api.e2e.spec.ts#answers each listed process with the packages it offers, in their order, as the read of the process does
05must prove
Confirmed
An application is Membership's record of a Submissions engine submission; Membership itself never creates one, so applications come from the engine's intake or from an import.
no proof recorded yet
lifecycleserviceunknown
FND-MBR-MEM-041
06must prove
Confirmed
An application is read in the scope of the membership it names; one that names no membership yet is visible only to workspace-wide readers, and a refusal reveals nothing of the linked membership.
no proof recorded yet
permissionapi, serviceunknown
FND-MBR-MEM-042
07must prove
Confirmed
The product should keep a process that has closed or not yet opened, or whose eligibility binding refuses the applicant, from taking an application.
no proof recorded yet
policyserviceunknown
FND-MBR-MEM-040
08
Confirmed
An application records the units its applicant chose, in order.
policydatabasedocumented
services-membership:docs/migrations/membership-core/README.md#What was built

Scenarios

IdGivenWhenThenProvenance
01An administrator records a join process for the national program offering Regular and Student.The process is listed and read.Both answers carry the two packages in order and the process is reviewed by default.test
services-membership:tests/e2e/application-processes-api.e2e.spec.ts#answers each listed process with the packages it offers, in their order, as the read of the process does

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software