The category map separates defined scenarios from missing proof. A covered category has a scenario; a binding records inspected test assertions and carries no execution result. State-model completeness and untested interactions remain explicit gaps.
Refused first-access input leaves no accepted construction. The combined scenario sets up the stated boundary, changes the upstream condition and observes its effect on the dependent outcome. Its steps and assertions are proposed; component tests do not establish this combined execution.
A staff request creates a customer and names an administrator whose existing identity has incompatible authority.
Steps
Submit the request, let first-administrator provisioning reach its authority check and inspect the build and invitation records.
Expected
The participant refuses, the build remains failed for staff recovery and no second invitation is sent. This checks a build-stage refusal rather than submission rollback.
Data
Create a separate run-owned workspace for each decision branch and an unaffected comparison workspace. Use a controlled clock, paused task or injected fault at the boundary named in the scenario.