Rhythm 2.0 Specifications

Appearance

SVC-PFM-OPS-jobsBackground Jobs

Markdown

SVC-PFM-OPS-jobs

Background Jobs

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaPlatformModuleOperational RecordsRevision1

Read atservices-platform ad3f6a65macroservice-libraries 54536a44react-console baf6dae3

Background Jobs ​

What This Service Is For ​

Background Jobs provides durable operational accounts and common monitors for work owned by Rhythm modules. The shared engine supplies reporting semantics, while Platform adds requester delivery and reconciliation of its own job families.

Boundary ​

The kind owner controls business tables, tasks and failure effects. Platform owns requester notices and publishes its own monitoring views. Compatible service views contribute read-only records to the common monitor; recovery does not write another service’s job tables.

Operations in Words ​

Customer reads cover the caller’s customer and reached workspaces. Workspace-addressed reads include every compatible service’s run for that workspace. HQ reads provide staff-wide scope and optional customer or workspace filters. Each group supplies list, count, kind, snapshot and history reads.

Snapshots retain steps, attempts and the definition published for the run, while excluding execution handles and row versions. Retry remains an owning workspace operation and cancellation has no Platform route. The contract records every operation’s Submissions exclusion.

Events and Jobs ​

No business events are declared. The five-minute reconciler reserves one invocation and hosts the additional workspace and website repair paths. Notifying kinds call requester delivery through their settlement work; the only notifying Platform kind is workspace provisioning.

Consistency Guarantees ​

Transactional submission does not include orchestration start. Version-checked reporting keeps step and summary writes together. Recovery timing depends on successful bounded passes. The corrected-success path can settle failure before its business effect, and requester delivery has neither a single-sender nor guaranteed-retry contract.

Owns
DOM-PFM-OPS-001
Repository
services-platform

Controls

48 controls apply, from the corpus control catalogue.

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

Does Not Own

  • Kind owners retain their tables, steps, tasks, submission authority and business failure effects.
  • Security and workspace lifecycle own access refresh, provisioning, purge and reset work; Jobs monitors and reconciles those records.
  • Cross-service monitoring reads published views without changing the other owner’s job records.

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