The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | participant seed set (declaration) | Declare a new task-type seed with a new key and set version. | CAP-PFM-TNL-008 | The declaration distinguishes the added default from earlier seeds. | documented services-platform:docs/standards/baseline-configuration.md#§2 How it is declared |
| 2 | build: declaration completeness and manifests | Run CRM’s declaration completeness checks. | CAP-PFM-TNL-007 | Workspace table ownership remains complete and unique. | test services-crm:modules/tenant-lifecycle/tests/integration/db/declaration-completeness.integration.spec.js#leaves no tenant-keyed table undeclared |
| 3 | BaselineReconciliationRun (deployment) | Deploy the release and reconcile eligible workspaces. | CAP-PFM-TNL-009 | Missing seed applications are recorded and failures identify their workspaces. | test services-crm:modules/tenant-lifecycle/tests/unit/lifecycle/baseline-reconciliation.spec.js#runs the reconciliation on every update, which is every deployment |
| 4 | baseline reconciliation (one workspace) | Reconcile an older uncustomized workspace. | CAP-PFM-TNL-009 | Its seeded configuration and ledger match the current baseline. | test services-crm:modules/tenant-lifecycle/tests/integration/services/lifecycle/baseline-reconciliation.integration.spec.js#leaves an old tenant with exactly the types a tenant provisioned today holds |
| 5 | baseline reconciliation (customized workspace) | Reconcile a workspace with a deleted default type. | CAP-PFM-TNL-008 | The ledger keeps the customer’s deletion in place. | test services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#does not recreate a type the customer deleted |
| 6 | createTenant | Provision a workspace after the baseline addition. | CAP-PFM-TNL-002 | The same declared defaults are applied during construction. | test services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#applies every baseline task type the first time |
| 7 | initializeTenant | Initialize a participant for one workspace on demand. | CAP-PFM-TNL-009 | The participant applies defaults still missing from its ledger. | test services-platform:modules/tenants/tests/integration/services/provisioning/initialize-tenant.integration.spec.js#runs the participant for the tenant and says what it did |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 3 | A workspace cannot be reconciled. | Record its explanation while continuing with other workspaces. | The deployment response reports failure after the collected work. | test services-crm:modules/tenant-lifecycle/tests/unit/lifecycle/baseline-reconciliation.spec.js#fails the deployment when any tenant failed, naming the tenant and its message |
| failure | 2 | A workspace-keyed table lacks a declaration. | Fail the completeness check. | The declaration gate is not satisfied. | test services-crm:modules/tenant-lifecycle/tests/integration/db/declaration-completeness.integration.spec.js#leaves no tenant-keyed table undeclared |
| Id | Statement | Provenance |
|---|---|---|
01 | Reconciled older CRM fixtures match current seeded configuration and ledger entries. | test services-crm:modules/tenant-lifecycle/tests/integration/services/lifecycle/baseline-reconciliation.integration.spec.js#leaves an old tenant with exactly the seed ledger a tenant provisioned today holds |
02 | Repeating seed application creates no additional defaults. | test services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#skips every seed on a second provisioning |
03 | Reconciliation preserves a renamed or removed ledgered default. | test services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#leaves a type the customer renamed after it was seeded exactly as they left it |
End-to-end policy: none: Deployment and database boundaries supply the relevant evidence; this flow has no interactive customer screen.