Financial Node - Backlinks [Dido Solutions, Inc Wiki]

This is a list of pages that seem to link back to the current page.

Application Programming Interface (API)
Audit Recording Role
Cash-Flow Computation Role
Centralized Management
Contract State Management Role
Control Plane
Crucible
Data Plane
Data Structure Instance
Data Distribution Service (DDS)
Distributed Immutable Data Object (DIDO)
Distributed Environment
Distributed Financial System
Distributed Network Topology
Evidence
FX Audit and Provenance Node
FX Audit Record
FX Audit Record Endpoint
FX Cash-Flow Obligation
FX Cash-Flow Obligation Endpoint
FX Command Acknowledgement
FX Contract State
FX Contract State Endpoint
FX Control Command
FX Node Status
FX Node Traceability
FX Policy and Release Node
FX Policy Decision
FX Policy Decision Endpoint
FX Provenance Record
FX Provenance Record Endpoint
FX Registry and Coordination Node
FX Release Package
FX Release Package Endpoint
FX Replay Request
FX Replay Request Endpoint
FX Replay Result
FX Replay Result Endpoint
FX Semantic Assertion
FX Semantic Interpretation Endpoint
FX Transaction Intake Endpoint
FX Transaction Intake Node
FX Transaction Record
FX Validation Node
FX Validation Result
FX Validation Result Endpoint
Health And Observability Plane
Interface Definition Language (IDL)
K3s
Kubernetes
Logical Audit and Provenance Plane
Logical Node
Logical Policy and Release Plane
Node Identity
Node Role
N
Obligation
Part 1 Concept to FX Logical Profile Element
Part 1 Concept to FX Logical Profile Element
Pedigree
Protocol Buffers
Provenance Recording Role
Registry and Coordination Role
Representational State Transfer (REST)
Remote Procedure Call (RPC)
Structural Validation Role
Traceability
P1-REQ-13-4-001
P1-REQ-13-4-002
P1-REQ-13-4-003
P1-REQ-13-4-004
P1-REQ-13-4-006
P1-REQ-13-4-011
P1-REQ-13-5-002
P1-REQ-13-5-003
P1-REQ-13-9-003
Introduction
1. Scope
3.1 Traceability to SIP-RA
3.3 Coverage of the Original FX Demo Reference Architecture
4.4 Logical Meaning Before Physical Realization
7.1 Overview
7.2 Node
8.7 Cross-Plane Relationships
10.3 Conceptual Element to Logical Element / PIM
10.4 Logical Element / PIM to Implementation Artifact / PSM
10.5 Implementation Artifact / PSM to Deployment Artifact
10.6 Deployment Artifact to Evidence
10.7 Bidirectional Review and Impact Analysis
11.2 Conceptual Elements Remain Distinct
11.3 Conceptual Architecture Does Not Prescribe Realization Mechanisms
11.6 Implementation Mappings Do Not Redefine Concepts
11.7 Deployment Artifacts Do Not Redefine Implementation Artifacts
12.2 Conceptual Elements Become Logical Elements
12.3 Logical Architecture Preserves Conceptual Meaning
12.6 Logical Architecture Provides the Basis for Implementation Profiles
12.7 Traceability from Part 1 to Part 2
13.4 Core Conceptual Element Requirements
13.5 Runtime Plane Requirements
13.9 Relationship to Logical Architecture / PIM Requirements
Foreword
Introduction
1. Scope
3.3 Traceability to Part 1 Conceptual Architecture
4.6 Traceability from Concept to Logical Model
5.7 Logical Traceability Model
6.1 Overview
10.3 Report Node Status
10.6 Issue Control Command
13.4 What Domain Profiles Preserve
Foreword
Introduction
1. Scope
3.1 Traceability to SIP-RA
3.3 Traceability to Part 1 Conceptual Architecture
3.5 Coverage of the Original FX Demo Reference Architecture
4.1 Domain Specialization without Conceptual Redefinition
4.2 FX Domain Scope before Implementation
4.3 Distributed FX Node Network
4.7 Traceability from Concept to Logical Profile
5.8 FX Demo Logical Traceability Model
14.6 Configuration Directory Model
14.7 Script Directory Model
14.13 Repository and Build Artifact Summary
15.6 Naming Convention Requirements
15.8 Logging Convention Requirements
15.9 Exception-Handling Requirements
Foreword
9.3 Competition and Provider Substitution
10.1 Use Case
9.4 Competitive Substitution

dido/99_annexes/annex-b-terms-and-definitions/f/financial_node.txt
Last modified: 2026/08/04 07:31
by nick_dido