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. 1.1 Purpose1.2 Scope1.4.2 What the Wiki Contains1. Introduction2.1 Operational Need2.2 Mission and Expected Outcomes3.3 Security Domains and Transfer Boundaries3. Operational Environment4.3 External Systems5.1 Select and Compose Baselines5.4 Assess Compliance5.5 Deploy the Environment5.6 Validate the Result5. Operational ConceptMO-001a — Infrastructure Environment CreationMO-001c — ReproducibilityMO-001d — Security Baseline ConformanceMO-001e — Compliance Baseline ConformanceFR-CFG-002 — Infrastructure as CodeFR-AG-002 — Artifact Export PackagesFR-AG-003 — Artifact Import PackagesFR-AG-004 — Baseline SynchronizationFR-AG-005 — Deployment Traceability Across Disconnected EnvironmentsC.3.5 Air-Gapped OperationsFR-BAS-002 — Compose Selected BaselinesC.3.9 Baseline Composition and WorkspaceCrucibleMO-002a — Reproducible Test EnvironmentsMO-004a — DIDO Baseline ComparisonMO-004b — Validation Decision Based on DIDO Baseline ComparisonMO-004 — DIDO Baseline Comparison and ValidationMO-005 — Comparative Evaluation of Candidate SolutionsC.1 Mission ObjectivesENV-001k — Define Version and Baseline InformationENV-001 — Define Test RequirementsENV-002b — Instantiate Included Test ObjectsENV-002c — Instantiate Included NodesENV-002d — Provision Required Test ResourcesENV-002e — Apply Configuration ValuesENV-002i — Enforce Deployment ConstraintsENV-002j — Apply Version and Baseline InformationENV-002k — Record Test Environment ConfigurationENV-002l — Validate Test Environment ConfigurationENV-002 — Configure Test EnvironmentENV-003a — Apply Required BaselineENV-003c — Initialise Participating NodesENV-003d — Initialise Test ObjectsENV-003e — Provision Required Test ResourcesENV-003j — Validate Controlled Starting StateENV-003k — Record Controlled Starting StateENV-003l — Prevent Execution from Invalid Starting StateENV-003 — Establish Controlled Starting StateENV-004a — Define Deterministic Environmental ConditionsENV-004b — Control Baselines and ConfigurationsENV-004j — Detect Environmental VariationENV-004k — Record Environmental VariationENV-004l — Validate Environmental DeterminismENV-004m — Prevent Execution Under Uncontrolled ConditionsENV-004 — Provide Deterministic Test EnvironmentAuthorityBaseline ApprovalBaseline CompositionBaseline ImmutabilityBaseline RepositoryBaseline ReuseBaseline SelectionCatalogCatalog EntryCommunity of InterestCompliance AssessmentCompliance BaselineConformanceContainer ImageContainer PlatformControlled InputCostDeclarative ConfigurationDeployment BaselineDeployment OperationDeployment RollbackDeployment ValidationEnergy ConsumptionEvaluation CharacteristicException HandlingFunctional CorrectnessGovernance PolicyGovernedInfrastructure as Code (IaC)ImageImage BaselineIncomplete Test RunInfrastructure BaselineInfrastructure BlueprintInfrastructure ConfigurationInfrastructure EnvironmentInfrastructure ResourceMaintainabilityOperational StabilityPerformance EfficiencyPlatform DeploymentPlatform Independent InformationPolicyQuality CharacteristicRecoverabilityRegistryReliabilityRepositoryResource ConsumptionRetirementRevisionRollbackScalabilitySecurity BaselineStarting ConditionStorage ConsumptionTest RunValidationValidation CriteriaValidation DecisionVersionVirtual Machine19.2 Boundary Between Part 4 and Part 519.6 Implementation Artefacts Prepared for Evidence19.7 Part 5 Handoff20.8 Scripts Do Not Redefine Interaction Patterns20.10 Phase 0 Does Not Define Later Phase Implementation ProfilesForewordIntroduction1.1 Purpose of the Handbook1.2 Scope of Phase 01.3 Intended Audience1.4 How to Use This Handbook2.2 Relationship to SIP-RA2.3 Relationship to FDIS-RA2.5 Relationship to the Phase 0 Implementation Source Material2.6 Relationship to Generated Code and Runtime Artefacts2. Relationship to the Architecture Documents3.1 Purpose of the Phase 0 Baseline3.2 Logical Architecture Baseline3.3 FX Demo Logical Profile Baseline3.4 Implementation Technology Baseline3.5 Repository Baseline3.6 Baseline Change Control3. Phase 0 Baseline4.2 Top-Level Repository Structure4.5 Configuration Directories4.7 Test Directories4.9 Git-Controlled and Non-Git-Controlled Content5.1 Supported Operating Systems5.4 Java Environment5.5 DDS Tooling5.6 Docker / Container Environment5.7 Git Environment5.8 Environment Verification5. Development Environment6.1 Required Tools6.2 Optional Tools6.3 Version Requirements6.4 Tool Installation Notes6.5 Prerequisite Validation6.6 Troubleshooting Tool Issues6.7 Tool Baseline Checklist6.8 Multiple Products, Platforms, and Implementations6.9 Tool Baseline Checklist Instances6. Prerequisites and Tooling7.1 General Naming Principles7.2 Directory Naming7.6 Configuration File Naming7.7 Topic Naming7.10 File Headers and Inline Documentation7.11 Spelling, Grammar, and Style8.1 Purpose of Generated Artifacts8.4 Python-Generated Support Artifacts8.6 Regeneration Rules8.7 Protecting Handwritten Code from Overwrite9.1 Role of IDL in Phase 09.4 Data Plane Type Definitions9.6 Generated Type Locations9.8 Type Compatibility Rules9. DDS / IDL / Type Generation10.4 Node Runtime Behavior10.8 Node Configuration11.4 Control Plane Message Semantics11.5 Control Plane QoS Expectations11.7 Control Plane Observability11. Control Plane Topics12.3 FX Demo Data Topics12.4 Topic Participation Rules12.6 Data Plane Validation12.7 Data Plane Non-Goals for Phase 012. Data Plane Topics13.9 runAll.sh13.10 runNode.sh13.12 prepareGitRepository.sh13. Build and Run Scripts14.1 Purpose of Containerisation in Phase 014.4 Container Runtime Configuration14.8 Container Cleanup16.7 Recoverable and Non-Recoverable Errors16. Exception Handling17.1 Repository Initialisation17.4 Pull Request Expectations17.7 Tagging the Phase 0 Baseline17. Git and Review Workflow dido/99_annexes/annex-b-terms-and-definitions/b/baseline.txt Last modified: 2026/07/13 11:28by nick_dido