The category map separates specified cases from recorded gaps. A proposed case describes proof to implement; a binding identifies the assertions supplied by an existing executable file. The permission and transition ledgers record the individual checks needed for the capability.
The interaction scenarios exercise locate people and organizations; save corrections without overwriting another change; maintain a person’s organizational relationships; remove records and their owned information; inspect a record’s changes over time. They change one part of a prepared record and inspect the dependent outcome. Unbound interactions remain proposed rather than implying an existing end-to-end implementation.
The frontmatter pins the repositories and identifies the source anchors for each scenario. Bindings record inspected assertions, while unbound cases remain proposed. Source inspection supplies no execution result or product approval.
Coverage
Rulecovered
Transitioncovered
Validationgap: FND-CRM-ENT-061
Permissioncovered
Edgegap: FND-CRM-ENT-061
Failurecovered
Boundarycovered
Concurrencycovered
Invariantcovered
Interactioncovered
Test Scenarios
17 scenarios proving CAP-CRM-ENT-013; 10 bound to an existing test.
01Archive needs its own keypermissionapinegativetest
An eligible record and configuration fixture exist for each operation; the caller can reach only the run’s workspace.
Steps
For each declared permission, execute its matching operation with that permission, then without it while retaining the other required grants. Read affected records after every refused mutation.
Expected
The authorized case reaches the operation; the missing-grant case is refused and preserves saved data. Record access alone does not authorize the other declared actions.
Data
Run-owned records and configuration in an isolated workspace.