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.
Accepted construction changes access only after readiness. 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 new customer workspace is requested and one remote readiness check reports a missing resource.
Steps
Submit the request, run construction through the failing readiness check, inspect ordinary access, repair the resource and retry.
Expected
The accepted identity remains the same; access stays closed on failure and opens only after the repaired attempt succeeds.
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.