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.
Activation during reset exposes the next batch guard. 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 loading implementation workspace has a reset paused between batches and a separate caller with activation authority.
Steps
Activate the load while reset remains open, then resume the next reset batch and inspect already removed and remaining rows.
Expected
Activation can return the workspace to active; the next reset batch refuses its changed lifecycle. Earlier committed removals stay removed and the reset cannot silently continue.
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.