FAS-MBR-STR-05 Terms and Standing: Feature Acceptance Suite
Markdown Planning / Membership / Organizational Structure, Membership Configuration and Terms / Feature Acceptance Suite Terms and Standing: Feature Acceptance Suite What the Feature Must Do as a Whole The suite follows membership dates through coverage, explained closure and continuity. Each scenario combines outcomes that staff need to trust together and identifies the capability examples it relies on.
Interactions Between Capabilities Attempt termination using the unsuitable reason and recompute dates and standing from the retained term. The action fails; its unchanged period keeps the original standing and continuity inputs.
A complete feature run also revisits the accepted and refused outcomes when referenced configuration changes. Proposed cases require executable proof before they establish delivery qualification.
Regression Record Revision Change Scenario Why 1 initial all Establish cumulative feature coverage from the landed planning and design contracts.
Show evidence (sources, provenance, origins, pinned commits)Scenarios 5 scenarios proving FEAT-MBR-STR-05 as a whole.
01 Compute a membership period and interpret its standing behaviour proposed
Exercises CAP-MBR-STR-015 CAP-MBR-STR-016 Relies on ATS-MBR-STR-015-03 ATS-MBR-STR-016-03 ATS-MBR-STR-016-05 Preconditions A dated anniversary offering, classification grace and continuity allowances are supplied. Steps [object Object] Expected The dated outputs and standing decisions agree at each supplied date, with continuity decided from the effective periods. Data Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions. Source CAP-MBR-STR-015 ,CAP-MBR-STR-016 05 Live zero grace and leap-day calculation stay compatible regression negative proposed
Exercises CAP-MBR-STR-015 CAP-MBR-STR-016 Relies on ATS-MBR-STR-015-08 ATS-MBR-STR-016-03 Preconditions A calendar rule ends in February of a leap year and the type overrides grace with zero. Steps [object Object] Expected The calculated end uses leap day; the next day lapses under zero grace and uses program grace after the override is cleared. Data Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions. Source CAP-MBR-STR-015 ,CAP-MBR-STR-016 ← Previous Feature Acceptance Suite FAS-MBR-STR-04 · Membership Offerings: Feature Acceptance Suite Next Feature Acceptance Suite → FAS-MBR-STR-06 · Setup Governance: Feature Acceptance Suite