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. 3.3 Security Domains and Transfer Boundaries5.4 Assess Compliance5.7 Preserve Evidence and Lifecycle Records6.1 Construct and Assess the Environment7.2 Produce the Transfer Bundle7.7 Preserve Traceability Across Environments8.4 Generate Supporting Evidence8.5 Transfer Compliance FindingsMO-001a — Infrastructure Environment CreationMO-003b — Provider-Independent Crucible DescriptionMO-003c — Provider-Independent Infrastructure BaselineMO-004a — Connected Environment OperationsMO-004b — Disconnected Environment OperationsMO-004c — Authorized Resource UseMO-004d — Disconnected Resource AvailabilityMO-005a — Infrastructure Baseline Artifact ManagementMO-005b — Infrastructure Baseline IdentificationMO-005c — Infrastructure Baseline Revision ControlMO-005f — Approved Infrastructure Baseline PreservationMO-005g — Infrastructure Deployment Baseline TraceabilityMO-005 — Reusable and Version-Controlled Infrastructure BaselinesOR-001a — Developer OperationsOR-001b — DevSecOps Engineer OperationsOR-001c — Platform Engineer OperationsOR-001d — System Administrator OperationsOR-001e — Security Engineer OperationsOR-001f — Compliance Officer OperationsOR-003a — Classified Environment OperationsOR-003f — Cross-Domain Transfer ControlFR-CFG-002 — Infrastructure as CodeC.3.1 Configuration ManagementFR-IMG-001 — Build Virtual Machine ImagesFR-IMG-002 — Build Container ImagesFR-IMG-003 — Immutable Infrastructure WorkflowsC.3.2 Image ManagementFR-AG-001 — Disconnected Deployment OperationsFR-AG-002 — Artifact Export PackagesFR-AG-003 — Artifact Import PackagesFR-AG-005 — Deployment Traceability Across Disconnected EnvironmentsC.3.5 Air-Gapped OperationsFR-COMP-004 — Compliance Evidence ArtifactsFR-COMP-010a — Compliance Finding Transfer Bundle InclusionFR-COMP-010b — Compliance Finding Association PreservationFR-COMP-010 — Transferable Compliance FindingsC.3.6 Compliance ManagementFR-DSO-003 — CI/CD Pipeline IntegrationFR-DSO-004 — Automated Build ExecutionFR-DSO-005 — Automated Deployment ExecutionFR-DSO-006 — Automated Validation ExecutionC.3.8 DevSecOps IntegrationAcceptance CriteriaArtifact CatalogArtifact Catalog RecordAuthorized ResourceBuild OperationCatalogCatalog EntryCI/CD PipelineCompliance AssessmentConcept of Operations (ConOps)ConfigurationConformanceConformance PointContainer ImageDeclarative ConfigurationDeployment BaselineDigital SignatureFunctional RequirementGitGovernance PolicyGovernedInfrastructure as Code (IaC)ImageInventoryOffline TransferOperational LifecycleOperational Lifecycle StatePackagePlatform DeploymentPolicyRegistryRepositoryResourceRetirementRevisionRevision HistorySecurity BaselineTransfer AuthorizationTransfer BoundaryTransfer BundleTransfer Bundle IntegrityValidation CriteriaValidation DecisionValidation OperationVersionVersion-Controlled ArtifactVersion ControlVersion Control SystemWeb-Based User Interface (Web UI)WorkspaceForewordIntroduction1.1 Purpose of the Handbook1.2 Scope of Phase 01.3 Intended Audience1.4 How to Use This Handbook2.1 Parent Architecture Sources2.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 Artefacts3.1 Purpose of the Phase 0 Baseline3.3 FX Demo Logical Profile Baseline3.5 Repository Baseline3.6 Baseline Change Control3. Phase 0 Baseline4.1 Repository Design Principles4.4 Generated Artefact Directories4.7 Test Directories4.8 Documentation Directories4.9 Git-Controlled and Non-Git-Controlled Content4. Repository Layout5.4 Java Environment5.5 DDS Tooling5.6 Docker / Container Environment5.7 Git Environment5.8 Environment Verification5. Development Environment6.1 Required Tools6.3 Version Requirements6.5 Prerequisite Validation6.7 Tool Baseline Checklist7.1 General Naming Principles7.2 Directory Naming7.4 Generated File Naming7.10 File Headers and Inline Documentation7.11 Spelling, Grammar, and Style7. Naming and File Conventions8.1 Purpose of Generated Artifacts8.2 Generated Versus Handwritten Files8.3 IDL-Derived Artifacts8.4 Python-Generated Support Artifacts8.6 Regeneration Rules8. Generated Artifacts9.4 Data Plane Type Definitions9.5 Type Generation Workflow9.6 Generated Type Locations9.7 Type Generation Validation9.8 Type Compatibility Rules9. DDS / IDL / Type Generation13.3 Python Utility Script Conventions13.4 createRepositoryStructure.sh13.7 generateTypes13.8 buildContainers.sh13.9 runAll.sh13.11 stopAll.sh14.1 Purpose of Containerisation in Phase 014.2 Container Design Principles14.8 Container Cleanup16.1 Purpose of Exception Handling Rules16.6 Container Errors17.1 Repository Initialisation17.4 Pull Request Expectations17.6 Generated File Review Rules17.7 Tagging the Phase 0 Baseline17. Git and Review Workflow18.9 Evidence Acceptance Criteria19.2 Full ACTUS Processing19.9 Full Multi-Vendor Interoperability20.1 Implementation Language Decisions20.2 DDS Vendor Decisions20.5 Generated Artifact Governance20.6 Repository Ownership20.9 Decision Record Expectations20.10 Risk Review and Baseline Acceptance dido/99_annexes/annex-b-terms-and-definitions/a/artifact.txt Last modified: 2026/07/20 00:51by nick_dido