Rhythm 2.0 Specifications

Appearance

DOM-PFM-TNL-004Initial Data Load

Markdown

DOM-PFM-TNL-004

Initial Data Load

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Specified by
CON-PFM-TNL-004

Design

Owned by
SVC-PFM-TNL-tenants

KindDomain objectProduct areaPlatformModuleWorkspace Lifecycle Across ApplicationsRevision1

Read atservices-platform ad3f6a65services-crm a8d1364fservices-commerce c8b66a98services-committees 36129c24services-membership 5994c270services-submissions 64236c19services-websites 5fc6823cservices-marketing d071a159

Initial Data Load ​

What It Models ​

Initial loading records the controlled import period and its reset attempts. The workspace keeps its latest opening facts, while durable reset jobs retain removal progress.

Identity and Attributes ​

The load uses workspace identity; every reset has its own durable job identity. The latest opening actor, time and optional bounded reason; repeated entry during loading and activation preserve it. Optional staff explanation retained on the reset job. Validated removal order for the participants classified as emptied. Stored participant position and bounded batch progress. Returned removal counts and inapplicable outcomes for visited participants. Aggregated resource totals exposed by reset inspection. Pending, running, succeeded or failed; recovery submits a new reset. Platform’s declared emptied and retained lists with reasons, plus required remote reset support. Returning lifecycle to active; this has no separate load-completion record.

Relationships ​

The workspace owns the opening facts on its lifecycle row. The reset invokes classified participant behavior across service boundaries.

Invariants ​

The structured invariants distinguish service and database enforcement from documented obligations. The listed enforcement points bound what the workflow can rely on.

How It Is Stored and Shared ​

Platform’s lifecycle service owns this design object. The physical declarations identify its stored records, while shared jobs provide durable execution and inspection.

Open Design Questions ​

Reset does not enforce the planned check for writes outside import, and activation does not inspect reset outcome. Reopening loading can replace previous opening facts, while application restoration differs by participant.

Relationships

ToCardinalityOwnershipCrosses a serviceOn archive or delete
DOM-PFM-TNL-001one-to-oneThe workspace owns the opening facts on its lifecycle row.no
DOM-PFM-TNL-003many-to-manyThe reset invokes classified participant behavior across service boundaries.yes

Invariants

InvariantProtectsEnforced atProvenance
INV-DOM-PFM-TNL-004-01
A new loading entry requires active implementation standing; a repeated entry during loading returns its existing record.
serviceobserved
services-platform:modules/tenants/services/persistence/tenants.ts:enterTenantLoading
INV-DOM-PFM-TNL-004-02
Repeated loading entry and repeated activation of a previously loaded active workspace retain the existing facts.
serviceobserved
services-platform:modules/tenants/services/persistence/tenants.ts:enterTenantLoading, activateLoadedTenant
INV-DOM-PFM-TNL-004-03
Activation preserves business standing and opening facts, and refuses a never-loaded active workspace.
serviceobserved
services-platform:modules/tenants/services/persistence/tenants.ts:activateLoadedTenant
INV-DOM-PFM-TNL-004-04
Reset requires loading implementation at admission, locked creation and each batch.
serviceobserved
services-platform:modules/tenants/services/reset/tenant-reset-operations.ts (requireResetAuthority)
INV-DOM-PFM-TNL-004-05
A database constraint permits only one pending or running reset per workspace.
service, databaseobserved
services-platform:modules/tenants/db/tenant-reset-jobs.table.ts:tenant_reset_jobs_open_uidx
INV-DOM-PFM-TNL-004-06
Reset classification accounts for Platform participants and validates planned remote reset declarations before removal.
serviceobserved
services-platform:modules/tenants/services/lifecycle/reset-participants.ts; services/reset/reset-tenant.ts:resetPlan

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software