This is an old revision of the document!
Registry and Coordination Role
Discussion
The Registry and Coordination Role identifies responsibility for recording FX logical Node participation, roles, capabilities, supported endpoints, information-structure versions, lifecycle state, compatibility metadata, and coordination context.
This role includes receiving registration information, maintaining logical participation records, supporting compatibility review, coordinating control-plane interactions, and preserving registration or coordination traceability.
The Registry and Coordination Role participates primarily in the FX Logical Control Plane. It also supports the FX Logical Health and Observability Plane when registration includes operational conditions and the FX Logical Audit and Provenance Plane when registration records support review or evidence.
Definition
responsible for recording FX logical Node participation, roles, capabilities, supported endpoints, information-structure versions, lifecycle state, compatibility metadata, and coordination context
Source
Specialization of Logical Node Role from Part 2: Distributed Node-Based Logical Architecture, Section 6.4, Logical Admission Rules from Part 2: Distributed Node-Based Logical Architecture, Section 11.6, and Control Plane from Part 1: Conceptual Architecture, Section 8.2; generalised from registry, capability advertisement, service registration, and control-plane material in the original FX Demo Reference Architecture.
Note
The Registry and Coordination Role does not prescribe a service registry, discovery tool, configuration service, directory, orchestration system, database, or runtime control service.
Example
The FX Registry and Coordination Node performs the Registry and Coordination Role by recording that the FX Cash-Flow Computation Node supports a specific FX Cash-Flow Obligation definition version.