Workspace decisions and participant execution

Context

The cited planning question has no final answer. This record retains the recommended boundary as a proposal, while observed participant execution supports the division of resource work.

Andrew must settle the module split before implementation responsibilities are assigned.

Decision

Retain staff-facing setup, load/reset, activation and retirement decisions with the workspace record; delegate resource execution to the participant owning each resource.

Alternatives Considered

Transfer setup and retirement decisions to the lifecycle module. That would separate workspace validation and staff authority from the record they govern.

Transfer loading and reset decisions to the Data Job Engine. The engine executes import work, while the workspace owner controls readiness and permission to clear it.

Consequences

Workspaces plans participant execution without assuming ownership of their records.

The lifecycle protocol is consumed from its owning module and covers description, preparation, verification, removal, inventory and reset.

Shared source scope does not authorize duplicate rule ownership.