The coverage map distinguishes specified examples from missing proof. A covered category means an expected case is specified; executable bindings and their run results remain separate evidence. Each required rule has a proof link or an explicit coverage finding in the structured rule ledger.
services-membership:tests/acceptance/configuration/MBR-ACC-0118.acceptance.ts#MBR-ACC-0118: References other applications hold: a billing template that drops members names a program and a terminated reason and blocks their deletion, while a Committees eligibility rule naming a type is invisible to Membership and the type can be deleted from under it
An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case.
Steps
Submit a classification under a missing program and a package renewing into itself.
Expected
Responses identify the invalid program and renewal fields instead of returning an unexpected error.
Data
The FAA example records or equivalent records prepared within the isolated workspace.
Bound to
services-membership:tests/e2e/database-refusals.e2e.spec.ts#mistakes only the database catches, through the API › DEF-MBR-0086: a configuration write a check, a foreign key or an integer column refuses › refuses a type of a program that does not exist 400 naming program_id
services-membership:tests/e2e/database-refusals.e2e.spec.ts#mistakes only the database catches, through the API › DEF-MBR-0086: a configuration write a check, a foreign key or an integer column refuses › refuses a package renewing into itself 400 naming renews_into_package_id
services-membership:tests/e2e/database-refusals.e2e.spec.ts#mistakes only the database catches, through the API › DEF-MBR-0086: a configuration write a check, a foreign key or an integer column refuses › refuses a type of a program that does not exist 400 naming program_id
08Workspace isolation applies to every mutationboundaryapinegativetest
An isolated workspace contains the records and current versions needed for the case.
Steps
Create enough records for continuation, omit page size, then request an oversized page and an activity-filtered package page with no matching first-page rows.
Expected
The omitted size selects 50, the oversized size caps at 500 and an empty filtered page can still continue.
Data
Separate fixture records for the accepted and refused operations.
An isolated workspace contains the records and current versions needed for the case.
Steps
Update a valid type with enabled flow-down and an absent target alongside changed role selections.
Expected
The failed update preserves the prior type version and selected roles.
Data
Separate fixture records for the accepted and refused operations.
Source
services-membership:tests/e2e/database-refusals.e2e.spec.ts#mistakes only the database catches, through the API › DEF-MBR-0086: a configuration write a check, a foreign key or an integer column refuses › refuses flow-down enabled without a target type 400 naming flowdown_type_id, and writes no type,services-membership:modules/configuration/services/configuration/configuration-records.ts:createConfiguration
An isolated workspace contains the records and current versions needed for the case.
Steps
Change a package to a mismatched classification while submitting new unit rules.
Expected
The refusal preserves the original package version and original unit-rule rows.
Data
Separate fixture records for the accepted and refused operations.
Source
services-membership:tests/e2e/database-refusals.e2e.spec.ts#mistakes only the database catches, through the API › DEF-MBR-0086: a configuration write a check, a foreign key or an integer column refuses › refuses a package of a type of another program 400 naming membership_type_id, and writes no package nor unit rule,services-membership:modules/configuration/services/configuration/configuration-records.ts:createConfiguration
13Stale policy saves preserve the accepted casesinteractionapiproposed
An isolated workspace contains the records and current versions needed for the case.
Steps
Exercise the capability’s exposed operations with its read-only and management callers, then repeat with application access removed, an unlicensed workspace and an unavailable workspace.
Expected
Each named operation requires its declared authority; admission failures occur before any record or calculated result is exposed.
Data
Separate fixture records for the accepted and refused operations.
Source
services-membership:tests/unit/route-authorization.spec.ts#route authorization: every Membership operation names its permission › requires membership.structure.read of every structure read and membership.structure.manage of every change,services-membership:modules/configuration/aws/api/configuration.routes.ts:configurationModuleRoutes,services-membership:tests/e2e/terms-api.e2e.spec.ts#the terms API, end to end in process › refuses a caller who holds no key in the tenant