Activate Cross-service Behaviors Through Deployment Switches

Context

These switches manage dependency readiness and background effects. The pinned code establishes deployment defaults, but this examination did not inspect live configuration or deploy anything.

Decision

Date reconciliation, owner-deletion policy and attention publishing are deployment-controlled; pinned defaults enable the first two in development, disable them in production and leave attention off without explicit configuration; deployed runtime values were not inspected.

Alternatives Considered

Enable all dependencies unconditionally. A deployment could invoke a missing cross-service capability and fail ordinary business work.

Expose these controls as workspace settings. That runtime product configuration is not implemented and would move a deployment-order concern into another contract.

Consequences

The differences from approved planning remain findings. A rollout decision must identify the intended production behavior and its prerequisites before preparation treats development behavior as representative.

Pinned defaults imply different development and production behavior for date settlement and association deletion. Planning and comments describing both switches as disabled everywhere conflict with the current defaults. Activation requires a recorded rollout decision; static defaults do not prove a running environment’s state.