Lifecycle and Workspace Administration Boundaries

Context

The shared source module contains both record administration and coordination across applications. Specification ownership follows the behavior rather than requiring a source-directory split.

Decision

Assign lifecycle orchestration and participant contracts to workspace lifecycle, while workspace administration retains customer records, business standing and HQ browsing.

Alternatives Considered

Keep everything about workspaces in workspace administration: Combining both concerns would obscure the independent orchestration records and safeguards. Split the source module in code first: A physical refactor is an implementation choice and need not precede a specification boundary.

Consequences

Lifecycle-specific operations belong with orchestration; ordinary workspace operations remain with administration. The overlapping Security design needs a coordinated revision to establish one home for lifecycle facts. Lifecycle services retain responsibility for system-owned state on the workspace row.