Ledgered Defaults and Baseline Reconciliation

Context

A missing record can mean either an unapplied default or a deliberate customer removal. Ledger evidence distinguishes those cases.

Decision

Use a workspace seed ledger to retain application of starter defaults and deployment reconciliation to add missing baseline configuration without reversing customer choices.

Alternatives Considered

Insert defaults in migrations: A migration cannot safely infer whether missing configuration was deliberately removed. Check for the record by name each time: Name lookup can recreate a renamed or deleted default.

Consequences

Ledgered application preserves deliberate changes to defaults. Where deployment reconciliation exists, older workspaces receive newly declared seeds. Commerce adoption and missing deployment passes remain implementation gaps.