Rhythm 2.0 Specifications

Appearance

SVC-PFM-INT-integrationsIntegration gateway, connections and messages service

Markdown

SVC-PFM-INT-integrations

Integration gateway, connections and messages service

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaPlatformModuleIntegration access, customer extensions and shared workflow configurationRevision1

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

Integration gateway, connections and messages service ​

What the Service Owns ​

This service owns the integration catalogue, installations, account links, capability selection, execution history and message delivery. Applications request provider work through the gateway and interpret the returned business outcomes themselves.

Operations ​

The operation rows define the callable boundary, its access class, exact permission declarations and planning coverage. Configuration and operational administration are not published as intake captures. Public health and provider callbacks retain their declared access boundaries.

Consistency and Failure ​

Account state, dependent binding reassessment and both audit records commit in a single database transaction. A database error rolls back these changes together.

Installation lifecycle changes include affected accounts, bindings and subscriptions in their transaction. No partial database cascade commits.

Credential replacement and verification work commit after external secret creation; usable accounts need not change standing while the replacement is checked. Database refusal requests cleanup of the new secret; cleanup itself can fail or be delayed.

Execution admission commits its key claim with the record, and settlement commits any required completion event with the outcome. Ambiguous provider outcomes require lookup rather than automatic reversal.

Provider effects and saved outcomes converge through lookup, reconciliation and eventual operator resolution. No automatic provider compensation occurs; the consuming application decides subsequent business action.

Queue-backed routing and delivery provide repeated attempts rather than exactly-once transport. Backoff ends in dead work that authorized operators can retry or replay.

Administrator mail is requested after the database mutation commits. Send errors are logged without an automatic mail retry.

Provider endpoint registration follows successful account verification. Failed setup can leave a locally saved endpoint without a provider reference.

Events and Jobs ​

The declarations distinguish application events, incoming requests, queue work and direct host reads. These are different transport boundaries; registering a declaration does not by itself publish an application event.

Open Questions ​

Provider effects, secret writes and post-commit mail do not share database rollback. Reconciliation has no execution mutex and consults the connection’s current release, so it does not guarantee use of the deployment that originally served the call. No scoped operation calls a language model.

Owns
DOM-PFM-INT-001DOM-PFM-INT-002DOM-PFM-INT-003DOM-PFM-INT-004
Repository
services-platform

Controls

57 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-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 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-PRV-004 TC-SEC-001 TC-SEC-002 TC-SEC-003 TC-SEC-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-VEN-001 TC-VEN-002 TC-VEN-003

Does Not Own

  • Accounting owns payment meaning and consumes execution and provider outcomes.
  • Applications that own source records publish the changes used by subscriptions.
  • Security owns grants, authorization evaluation, principals and security audits; integration mutations use its audit writer.
  • The jobs service owns the durable roots, steps and monitoring used for account checks.
  • Adapters implement provider-specific behavior within the shared contracts.
  • Workspace lifecycle schedules deletion and calls the integration cleanup participant.

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