Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top Backlinks This is a list of pages that seem to link back to the current page. IP1-REQ-13-9-00513.9 Relationship to Logical Architecture / PIM Requirements1. Scope3.1 Traceability to SIP-RA3.5 Coverage of the Original FX Demo Reference Architecture3.6 Traceability Position4.2 FX Domain Scope before Implementation5.6 FX Demo Logical Information Model9.1 Overview15.4 FX Data Representation Independence16.4 FX Logical Data Structures Remain Distinct from Serialisation Formats1. Scope3.1 Traceability to SIP-RA3.3 Traceability to Part 1 Conceptual Architecture3.4 Traceability to Part 2 Distributed Node-Based Logical Architecture / Platform-Independent Model (PIM)3.5 Traceability to Part 3 FX Demo Logical Profile3.6 Traceability to Phase 0 Implementation Source Material3.7 Traceability to the Phase 0 Developer Handbook3.8 Traceability Position4.2 Phase 0 Implementation Scope4.5 Relationship to the FX Demo Logical Profile4.6 Relationship to Later Development Phases5.2 Implementation Artifacts Realize Logical Elements5.3 Traceability Before Code5.5 Generated Artifacts Before Manual Adaptation6.2 Part 3 Working Baseline6.4 Repository Baseline6.5 IDL and Generation Baseline6.7 Traceability Baseline6.9 Phase 0 Implementation Preconditions Summary7.3 IDL as Phase 0 Data Definition Mechanism7.5 Generated Types as Phase 0 Implementation Data Artifacts7.8 Repository Structure as Phase 0 Implementation Organization7.9 Technology Selection Boundaries7.10 Phase 0 Technology Selection Summary8.2 Node Mapping Principles8.10 FX Audit and Provenance Node Mapping8.11 FX Health and Observability Node Mapping8.12 FX Registry and Coordination Node Mapping8.13 FX Replay and Reconstruction Node Mapping8.14 External Oversight Participant Mapping9.2 Topic Mapping Principles10.1 Overview10.2 Information Structure Mapping Principles10.4 Generated Type Naming Principles10.5 FX Transaction Candidate Mapping10.6 FX Transaction Record Mapping10.7 FX Validation Result Mapping10.8 FX Semantic Assertion Mapping10.9 FX Contract State Mapping10.10 FX Cash-Flow Obligation Mapping10.11 FX Policy Decision Mapping10.12 FX Release Package Mapping10.13 FX Audit Record Mapping10.14 FX Provenance Record Mapping10.15 FX Node Status Mapping10.16 FX Control Command Mapping10.17 FX Command Acknowledgement Mapping10.18 FX Replay Request Mapping10.19 FX Replay Result Mapping10.20 Information-Structure-to-IDL Mapping Summary19.2 Boundary Between Part 4 and Part 519.3 Implementation Artefacts Prepared for Deployment19.4 Implementation Artefacts Prepared for Testability19.6 Implementation Artefacts Prepared for Evidence19.7 Part 5 Handoff20.2 Implementation Artefacts Do Not Redefine Logical Elements20.4 IDL Structures Do Not Redefine Logical Information Structures20.5 Generated Types Do Not Redefine Logical Information Structures20.12 Implementation Constraints Summary21.1 OverviewIntroduction1.1 Purpose of the Handbook1.2 Scope of Phase 01.3 Intended Audience2.1 Parent Architecture Sources2.6 Relationship to Generated Code and Runtime Artefacts3.1 Purpose of the Phase 0 Baseline3.4 Implementation Technology Baseline3.5 Repository Baseline3.6 Baseline Change Control4.1 Repository Design Principles4.4 Generated Artefact Directories4.7 Test Directories4.8 Documentation Directories4.9 Git-Controlled and Non-Git-Controlled Content5.5 DDS Tooling6.1 Required Tools6.3 Version Requirements6.6 Troubleshooting Tool Issues6.7 Tool Baseline Checklist6.8 Multiple Products, Platforms, and Implementations7.4 Generated File Naming7.10 File Headers and Inline Documentation8.1 Purpose of Generated Artifacts8.2 Generated Versus Handwritten Files8.3 IDL-Derived Artifacts8.5 Generated Documentation8.6 Regeneration Rules9.1 Role of IDL in Phase 09.2 IDL Source Location9.4 Data Plane Type Definitions9.5 Type Generation Workflow9.7 Type Generation Validation9.8 Type Compatibility Rules9. DDS / IDL / Type Generation10.4 Node Runtime Behavior10.6 Node Status Reporting11.4 Control Plane Message Semantics12.1 Purpose of the Data Plane in Phase 012.2 Placeholder Data Plane Topics12.3 FX Demo Data Topics12.6 Data Plane Validation13.1 Purpose of Build and Run Scripts13.5 checkPrerequisites.sh13.7 generateTypes14.1 Purpose of Containerisation in Phase 014.3 Container Build Inputs15.1 Purpose of Logging15.7 Control Plane Observation17.1 Repository Initialisation17.4 Pull Request Expectations17.6 Generated File Review Rules dido/99_annexes/annex-b-terms-and-definitions/i/idl.txt Last modified: 2026/08/04 07:09by nick_dido