The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | membership_attention_sweep | The morning sweep runs. | CAP-MBR-MEM-014 | Alerts open for memberships ending within the horizon without a renewal. | test services-membership:modules/memberships/tests/integration/services/expiring-memberships.integration.spec.ts#publishes an open item for a membership whose term ends inside the horizon |
| 2 | createBillingTemplate | Record a renewal template with a notice, a reminder and a drop reason. | CAP-MBR-MEM-013 | The template is saved. | test services-membership:tests/e2e/billing-api.e2e.spec.ts#creates a template |
| 3 | createBillingRun | Create a run from the template over the terms ending this season. | CAP-MBR-MEM-013 | A draft run with the template's documents. | test services-membership:tests/e2e/billing-api.e2e.spec.ts#creates a run from the template |
| 4 | planBillingRun | Plan the run on today's date. | CAP-MBR-MEM-013 | Renewing and lapsed candidates with their orders, notices, reminders and drops, and the statistics. | test services-membership:modules/billing/tests/integration/billing-runs.integration.spec.ts#plans the candidates and their actions on the run’s date |
| 5 | listBillingRunActions | Review the planned actions. | CAP-MBR-MEM-013 | Each candidate's notice and reminder is listed. | test services-membership:tests/e2e/billing-api.e2e.spec.ts#plans it, and lists its notice and reminder |
| 6 | executeBillingRun | Execute the run. | CAP-MBR-MEM-013 | One order per renewing member, the notices and reminders submitted, and the lapsed terms dropped with the reason. | test services-membership:modules/billing/tests/integration/billing-runs.integration.spec.ts#executes on the jobs engine: one order per renewing candidate (Jo’s with both dues chapters), a notice and reminder each, one drop per lapsed term |
| 7 | createTerm | A member's renewal is committed. | CAP-MBR-MEM-014 | Their expiring alert is resolved as renewed. | test services-membership:modules/memberships/tests/integration/services/expiring-memberships.integration.spec.ts#resolves the item renewed in the staff renewal’s transaction |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 3 | The administrator sets the template to run on a schedule instead. | A recurring run creates and plans one run per occurrence in the association's time zone. | The season runs itself, once per occurrence. | test services-membership:modules/billing/tests/integration/billing-runs.integration.spec.ts#creates and plans one run per occurrence of a recurring run, a redelivered occurrence finding it |
| alternate | 6 | A member's term is corrected after the run was planned. | That member's action is settled as stale. | Nothing is billed on the old facts. | test services-membership:modules/billing/tests/integration/billing-runs.integration.spec.ts#refuses as stale an action whose term changed after planning |
| failure | 6 | The execution job fails part way. | The run returns to planned with its settled actions kept. | The administrator executes it again. | unknown |
| failure | 6 | Notices are submitted before Platform knows their purposes. | Platform stores the requests and sends nothing. | Members receive no notice. | unknown |
| Id | Statement | Provenance |
|---|---|---|
01 | A second execution of the same run does nothing. | test services-membership:modules/billing/tests/integration/billing-runs.integration.spec.ts#does nothing on a second execution |
02 | Each renewing member receives one order, with every chapter's dues on it. | test services-membership:modules/billing/tests/integration/billing-runs.integration.spec.ts#executes on the jobs engine: one order per renewing candidate (Jo’s with both dues chapters), a notice and reminder each, one drop per lapsed term |
03 | Each lapsed member is dropped with the run's reason and keeps their term's dates. | test |
End-to-end policy: optional: Membership has no console screens yet; the journey is proved through the API and the jobs engine in process. A browser test becomes required when the billing screens are built.