Rhythm 2.0 Specifications

Appearance

SVC-COM-FUL-data-operationsData Operations Service Module

Markdown

SVC-COM-FUL-data-operations

Data Operations Service Module

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaCommerceModuleFulfillment, Shipping and InventoryRevision1

Read atservices-commerce c8b66a98

Data Operations Service Module ​

What This Service Is For ​

Load prepared historical Commerce records and read their imported results by source key.

Boundary ​

A shared engine coordinates jobs and batches, while collection records and routes remain with their owning modules. Collection-specific migration ownership is still a product question.

Operations in Words ​

Twelve collections expose submission, listing, inspection, source-key readback, result and rejection reads, apply, pause, resume, cancellation and retry. Every route uses console access and its declared collection permission set.

Events and Jobs ​

The dispatcher runs after nudges and on its minute schedule; the worker consumes queued batches and rechecks the submitter’s authority. No model inference or public change-event stream is involved.

Consistency Guarantees ​

Each item’s applied change retains its receipt and source crosswalk together. Cancellation reports committed work rather than reversing it; repeated batches skip completed items and deferred dependencies retain explicit outcomes.

Repository
services-commerce

Controls

42 controls apply, from the corpus control catalogue.

TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-004 TC-LOG-005 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CHG-007 TC-AVL-002 TC-AVL-003 TC-AVL-004 TC-MON-001 TC-MON-002 TC-MON-003 TC-MON-004 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002

Does Not Own

  • Platform owns the shared job engine and its batch, receipt and crosswalk contracts.
  • Imported collections remain owned by their record modules; this module’s physical records are warehouses, locations and stock.
  • Collection HTTP functions serve the generated routes; data operations has no separate API function.
  • Platform owns workspace loading and the availability gate for migration routes.

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