Preferences and Workspace Settings Are Stored but Not Applied Yet

Context

The core release stores future delivery configuration without activating it for current notices.

Decision

Preferences, settings, wording, quiet periods, digests, identities and text accounting remain dormant persistence in the current release.

Alternatives Considered

Waiting to create every table would require later schema work around populated notification records. Applying future settings now would expand behavior beyond the approved core release.

Consequences

The declared definition-disabled outcome has no processing writer. Personal explanations describe configuration as a later-release capability. Activation needs an approved plan and orchestration proof beyond persistence guards.