Rhythm 2.0 Specifications

Appearance

WF-PFM-SEC-012Reconcile shared definitions, founding staff and principals on deploy

Markdown

WF-PFM-SEC-012

Reconcile shared definitions, founding staff and principals on deploy

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-PFM-SEC-013, CAP-PFM-SEC-015, CAP-PFM-SEC-016, CAP-PFM-SEC-018, CAP-PFM-SEC-017

KindWorkflowProduct areaPlatformModuleSecurity, Customers and WorkspacesRevision1ExaminercodexExamined on2026-10-23

Read atservices-platform ad3f6a65

Reconcile shared definitions, founding staff and principals on deploy ​

What It Does ​

Publication has three stages and two storage boundaries. Prepared catalog changes are not current; staged route requirements are visible; activation commits the catalog before switching the registry.

The Flow ​

The diagram separates the relevant success, alternative and failure paths. The numbered hop rows retain the detailed authority checks, delegated work and retry limits.

When Something Fails ​

The storage gap can leave catalog and active registry on different releases. Repeating activation is the intended convergence path, but failure/recovery proof remains a finding. Unchanged built-in versions do not imply that every deployment step writes nothing.

Immutable releases reject conflicting content. Staging preserves an already active release. Activation always invokes catalog commit before checking whether registry state changed; unchanged registry activation skips flushing, and unchanged built-in content preserves its version.

Catalog reconciliation transacts within Postgres, but route-registry activation uses a separate store afterward. During staging the authorizer reads active and staged requirements and applies both to shared routes. There is no atomic transaction across catalog and registry.

Open Design Questions ​

The recorded findings retain any stronger planning expectation, missing writer or unproved recovery path. Observed behavior does not approve those outstanding product choices.

Controls

55 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-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-DAT-005 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-SEC-001 TC-SEC-002 TC-SEC-003 TC-SEC-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

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