---
id: ADR-PFM-TNL-007
title: Ledgered Defaults and Baseline Reconciliation
product_area: platform
module: tenant-lifecycle
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  services-committees: 36129c24daeaadcdb339218c38cdeaff9861359d
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  services-submissions: 64236c19be89579ef5897aad7de3925ed3ce03bf
  services-websites: 5fc6823c69d5e6f208c21dba8c0eb3132f8bdc4c
  services-marketing: d071a159fe9782bb71ff246d5c67d5bbfe07fbfa
decision: Use a workspace seed ledger to retain application of starter defaults and deployment reconciliation to
  add missing baseline configuration without reversing customer choices.
constrains:
- DOM-PFM-TNL-003
- SVC-PFM-TNL-crm-tenant-lifecycle
- SVC-PFM-TNL-commerce-tenant-lifecycle
- SVC-PFM-TNL-committees-tenant-lifecycle
- SVC-PFM-TNL-membership-tenant-lifecycle
- WF-PFM-TNL-002
- WF-PFM-TNL-005
- WF-PFM-TNL-006
origin: services-platform:docs/standards/baseline-configuration.md#§1–§4 (D-48, Andrew 2026-10-19); services-platform:docs/tenants/tenant-lifecycle-plan.md#§6.3
alternatives:
- option: Insert defaults in migrations
  why_not: A migration cannot safely infer whether missing configuration was deliberately removed.
- option: Check for the record by name each time
  why_not: 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.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: docs/standards/baseline-configuration.md; modules/tenants/db/tenant-seed-applications.table.ts.'
- 'services-crm at a8d1364f: modules/tenant-lifecycle/services/lifecycle/baseline-reconciliation.ts.'
---

# 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.