Evidence - Backlinks [Dido Solutions, Inc Wiki]

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

3.2.2 Explicit Separation of Interpretive Concerns
1.1 Purpose
1.2 Scope
1.3 Intended Audience
1.4.1 Why a Wiki
1.4.2 What the Wiki Contains
1.4.3 Using the Wiki
1.4.4 Maintaining the Wiki
1. Introduction
2.1 Operational Need
2.2 Mission and Expected Outcomes
2. Operational Need and Mission
3.1 Connectivity Conditions
3.2 Deployment Environments
3.3 Security Domains and Transfer Boundaries
3. Operational Environment
4.1 Human Actors
4.3 External Systems
5.1 Select and Compose Baselines
5.2 Construct Images
5.3 Capture and Preserve Dependencies
5.4 Assess Compliance
5.5 Deploy the Environment
5.6 Validate the Result
5.7 Preserve Evidence and Lifecycle Records
5. Operational Concept
6.1 Construct and Assess the Environment
8.4 Generate Supporting Evidence
8. Compliance Operations
MO-001b — Deployment Duration
MO-001c — Reproducibility
MO-001d — Security Baseline Conformance
MO-001e — Compliance Baseline Conformance
MO-002a — Maximum Platform Deployment Duration
MO-002b — Platform Deployment Duration Reduction
MO-003a — Cross-Platform Deployment
MO-003b — Provider-Independent Crucible Description
MO-003c — Provider-Independent Infrastructure Baseline
MO-003d — Limitation of Provider-Specific Dependencies
MO-004a — Connected Environment Operations
MO-004b — Disconnected Environment Operations
MO-004c — Authorized Resource Use
MO-004d — Disconnected Resource Availability
MO-005a — Infrastructure Baseline Artifact Management
MO-005b — Infrastructure Baseline Identification
MO-005c — Infrastructure Baseline Revision Control
MO-005d — Approved Infrastructure Baseline Selection
MO-005e — Infrastructure Baseline Reuse
MO-005f — Approved Infrastructure Baseline Preservation
MO-005g — Infrastructure Deployment Baseline Traceability
MO-006a — Operational Lifecycle Association
MO-006b — Infrastructure Lifecycle Initiation
MO-006c — Infrastructure Lifecycle State Recording
MO-006d — Infrastructure Lifecycle Transition Execution
MO-006e — Infrastructure Environment Retirement
OR-001a — Developer Operations
OR-001b — DevSecOps Engineer Operations
OR-001c — Platform Engineer Operations
OR-001d — System Administrator Operations
OR-001e — Security Engineer Operations
OR-001f — Compliance Officer Operations
OR-002c — Deployment Acceptance Record
OR-003a — Classified Environment Operations
OR-003f — Cross-Domain Transfer Control
FR-CFG-002 — Infrastructure as Code
FR-AG-002 — Artifact Export Packages
FR-AG-003 — Artifact Import Packages
FR-AG-005 — Deployment Traceability Across Disconnected Environments
FR-COMP-002 — Compliance Scanning Tool Integration
FR-COMP-003 — Compliance Reporting
FR-COMP-004 — Compliance Evidence Artifacts
FR-COMP-009a — Security Control Traceability Matrix Evidence
FR-COMP-009b — Risk Management Framework Evidence
FR-COMP-009c — Authorization to Operate Evidence
FR-COMP-009 — Security-Control Implementation Evidence
C.3.6 Compliance Management
FR-DSO-003 — CI/CD Pipeline Integration
FR-BAS-003 — Process Predeployment and Postdeployment Steps
Crucible
MO-001 — Governed Distributed Test Environments
MO-002a — Reproducible Test Environments
MO-002b — Reproducible Test Execution
MO-002 — Reproducible Test Environments and Test Execution
MO-003 — Automated Test Execution
MO-004a — DIDO Baseline Comparison
MO-004b — Validation Decision Based on DIDO Baseline Comparison
MO-004 — DIDO Baseline Comparison and Validation
MO-005 — Comparative Evaluation of Candidate Solutions
MO-006a — Application-Independent Testing
MO-006b — Infrastructure-Independent Testing
MO-007a — Connected Environment Operation
MO-007b — Disconnected Environment Operation
MO-007c — Air-Gapped Environment Operation
MO-007 — Connected, Disconnected, and Air-Gapped Operation
MO-008b — Evidence Traceability
MO-008 — Traceable Test Results and Evidence
MO-009d — Test Resource Use Traceability
MO-009 — Reusable Test Resources
C.1 Mission Objectives
ENV-001a — Define Test Environment Purpose
ENV-001c — Identify Included Test Objects
ENV-001d — Identify Included Nodes
ENV-001k — Define Version and Baseline Information
ENV-001 — Define Test Requirements
ENV-002g — Enforce Environmental Constraints
ENV-002h — Enforce Security Constraints
ENV-002k — Record Test Environment Configuration
ENV-002l — Validate Test Environment Configuration
ENV-002 — Configure Test Environment
ENV-003f — Load Required Test Inputs
ENV-003g — Establish Required Communication Relationships
ENV-003h — Apply Applicable Constraints
ENV-003i — Remove or Isolate Residual State
ENV-003j — Validate Controlled Starting State
ENV-003k — Record Controlled Starting State
ENV-003l — Prevent Execution from Invalid Starting State
ENV-003 — Establish Controlled Starting State
ENV-004a — Define Deterministic Environmental Conditions
ENV-004b — Control Baselines and Configurations
ENV-004c — Control Test Inputs
ENV-004d — Control Time Sources
ENV-004e — Control Random Values
ENV-004f — Control Execution Ordering
ENV-004g — Control Resource Allocation
ENV-004h — Control External Dependencies
ENV-004i — Control Communication Conditions
ENV-004j — Detect Environmental Variation
ENV-004k — Record Environmental Variation
ENV-004l — Validate Environmental Determinism
ENV-004m — Prevent Execution Under Uncontrolled Conditions
ENV-004 — Provide Deterministic Test Environment
ENV-005a — Emulate Distributed Topology
ENV-005b — Emulate Participating Nodes
ENV-005c — Emulate Communication Behaviour
ENV-005d — Emulate Time and Clock Conditions
ENV-005e — Emulate Resource Conditions
ENV-005f — Emulate Node Failures
ENV-005g — Emulate Communication Failures
ENV-005h — Emulate Network Partitions
ENV-005i — Emulate Membership and Topology Changes
ENV-005j — Emulate Recovery Behaviour
ENV-005k — Observe Distributed Interactions
ENV-005l — Record Distributed-System Emulation
ENV-005m — Validate Emulation Fidelity
ENV-005 — Emulate Distributed Systems
ENV-006 — Reproduce Real-World Conditions
ENV-007 — Support Repeatable Test Environments
NOD-001a — Identify the Node Role
NOD-001b — Identify the Node Type
NOD-001c — Define Node Interfaces
NOD-001d — Define Node Dependencies
NOD-001e — Define Node Resource Requirements
NOD-001f — Define Node Lifecycle Behaviour
NOD-001g — Define Node Observability Requirements
NOD-001h — Validate the Node Definition
NOD-002a — Select the Node Definition
NOD-002b — Select the Node Implementation
NOD-002c — Resolve Node Dependencies
NOD-002d — Allocate Node Resources
NOD-002e — Instantiate the Node
NOD-002f — Establish the Node Initial State
NOD-002g — Record Node Provisioning
NOD-002h — Validate the Provisioned Node
NOD-002 — Provision a Node
NOD-003a — Select the Node Configuration
NOD-003b — Resolve Node Configuration Values
NOD-003c — Apply the Node Configuration
NOD-003e — Protect Sensitive Configuration Values
NOD-003f — Record Node Configuration
NOD-003g — Validate the Configured Node
NOD-003 — Configure a Node
NOD-004a — Establish the Initial Node State
NOD-004b — Start the Node
NOD-004c — Confirm Node Readiness
NOD-004d — Transition the Node State
NOD-004e — Stop the Node
NOD-004g — Handle a Node Lifecycle Exception
NOD-004h — Record Node Lifecycle Activity
NOD-004 — Control the Node Lifecycle
NOD-005a — Authorize Node Execution
NOD-005b — Initiate Node Execution
NOD-005c — Provide Node Inputs
NOD-005d — Observe Node Execution
NOD-005e — Control Node Execution
NOD-005f — Handle a Node Execution Exception
NOD-005g — Complete Node Execution
NOD-005h — Record Node Execution
NOD-005 — Execute a Node
NOD-006 — Isolate a Node
NOD-007 — Identify a Node
NOD-008a — Establish Node Observation
NOD-008b — Observe Node State
NOD-008c — Observe Node Activity
NOD-008d — Observe Node Resource Use
NOD-008e — Detect a Node Deviation
NOD-008f — Record Node Observations
NOD-008 — Observe a Node
NOD-009a — Establish Node Resource Controls
NOD-009b — Allocate Node Resources
NOD-009c — Control Node Resource Use
NOD-009d — Handle a Node Resource-Control Exception
NOD-009e — Release Node Resources
NOD-009f — Record Node Resource Control
NOD-009 — Control Node Resources
NOD-010a — Specify a Node Fault
NOD-010b — Authorize Node Fault Injection
NOD-010c — Prepare Node Fault Injection
NOD-010d — Inject a Node Fault
NOD-010e — Control a Node Fault
NOD-010f — Recover from a Node Fault
NOD-010g — Record Node Fault Injection
NOD-010 — Inject Node Faults
NOD-011a — Specify Node State Preservation
NOD-011b — Capture Node State
NOD-011c — Protect Preserved Node State
NOD-011d — Verify Preserved Node State
NOD-011e — Retain Preserved Node State
NOD-011f — Restore Preserved Node State
NOD-011g — Dispose of Preserved Node State
NOD-011h — Record Node State Preservation
NOD-011 — Preserve Node State
NOD-012 — Reset a Node
NOD-013 — Maintain Node Traceability
TWIN-005f — Preserve Twin Realization State Provenance
CON-005 Define Conformance Evidence
CON-006 Define Traceability Relationships
Annex C: Requirements
Access Control
Accreditation
Accreditation Boundary
Accredited Software Factory
Application Independence
Authorization to Operate (ATO)
Audit and Provenance State Record
Audit Recording Role
Authorizing Authority
Baseline Immutability
Candidate Solution
Cash-Flow Computation Role
CI/CD Pipeline
Community of Interest
Compliance
Compliance Assessment
Compliance Finding
Configuration Record
Configuration Validation
Conformance
Conformance Assessment
Conformance Claim
Conformance Criterion
Conformance Determination
Conformance Model
Conformance Point
Contract State Management Role
Cost
Crucible
Cryptographic Material
Deployment Baseline
Deployment Rollback
Deployment Validation
Energy Consumption
Evaluation Characteristic
Exception Handling
Execution Facility
Executable Instruction
Executable Instruction
Expected Result
E
Federal Risk and Authorization Management Program (FedRAMP)
Functional Correctness
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 Control Command Endpoint
FX Endpoint Traceability
FX Evidence Traceability
FX Information Structure Traceability
FX Interaction Traceability
FX Logical Change Control
FX Logical Compatibility
FX Logical Policy Constraints
FX Logical Versioning
FX Node Status
FX Node Status Endpoint
FX Node Traceability
FX Policy Decision
FX Policy Decision Endpoint
FX Provenance Record
FX Provenance Record Endpoint
FX Release Package
FX Replay Request
FX Replay Result
FX Replay Result Endpoint
FX Runtime Plane Traceability
FX Semantic Assertion
FX Semantic Interpretation Endpoint
FX Transaction Candidate
FX Transaction Intake Endpoint
FX Transaction Intake Node
FX Transaction Lifecycle State
FX Transaction Record
FX Validation Result
FX Validation Result Endpoint
Governance Policy
Governed
Health Reporting Role
High-Assurance Environment
Image Promotion
Incomplete Test Run
Infrastructure Independence
Interpretation-Controlled Transition
Logical Audit and Provenance Plane
Logical Node
Maintainability
Observation
Operational Stability
Part 1 Concept to FX Logical Profile Element
Part 1 Concept to FX Logical Profile Element
Performance Efficiency
Policy
Policy Evaluation Role
Protocol Buffers
Provenance
Provenance Recording Role
Qualified Node
Quality Characteristic
Record
Recoverability
Registry and Coordination Role
Release Control Role
Reliability
Repository
Resource
Resource Consumption
Retirement
Risk Management Framework (RMF)
Role
Rollback
Scalability
Security Control Traceability Matrix (SCTM)
Security
Semantic Interpretation Role
Sequence Step
Security Technical Implementation Guide (STIG)
Storage Consumption
Structural Validation Role
Test Argument Value
Test Definition
Test Executable
Test Execution
Test Execution Exception
Test Execution Exception Type
Test Item
Test Resource
Test Result
Test Run
Test Run State
Test Run Termination Reason
Test Sequence
Test Step
Timeout
Traceability
Transaction Intake Role
Transfer Bundle
Validation
Validation Criteria
Validation Decision
Verdict
Web-Based User Interface (Web UI)
P1-REQ-13-2-001
P1-REQ-13-2-002
P1-REQ-13-4-001
P1-REQ-13-4-009
P1-REQ-13-4-010
P1-REQ-13-5-010
P1-REQ-13-6-001
P1-REQ-13-6-006
P1-REQ-13-6-008
P1-REQ-13-6-012
P1-REQ-13-7-001
P1-REQ-13-7-005
P1-REQ-13-7-006
P1-REQ-13-7-007
P1-REQ-13-7-008
P1-REQ-13-8-001
P1-REQ-13-8-002
P1-REQ-13-8-003
P1-REQ-13-8-004
P1-REQ-13-8-005
P1-REQ-13-8-006
P1-REQ-13-9-003
P1-REQ-13-10-003
P2-REQ-16-5-010
P2-REQ-16-5-011
P2-REQ-16-7-008
P2-REQ-16-8-005
P2-REQ-16-9-004
P2-REQ-16-9-005
P2-REQ-16-9-006
P2-REQ-16-9-008
P2-REQ-16-9-009
P2-REQ-16-9-012
P2-REQ-16-10-005
Introduction
1. Scope
Foreword
Introduction
1. Scope
3.1 Traceability to SIP-RA
3.2 Alignment with FDIS-RA
3.3 Coverage of the Original FX Demo Reference Architecture
3.4 Traceability Position
3. Traceability to Parent and Source Architectures
4.1 Separation of Concerns
4.5 Traceability
4.6 Evidence Orientation
4.7 Governance of Meaning
4. Conceptual Architecture Principles
5.1 Overview
5.6 Classification Values and Runtime Identifiers
5.7 Classification and Governance
6.1 Overview
6.2 Finance Ecosphere
6.5 Classification Inheritance for FX Profiles
6.7 Classification Governance
7.1 Overview
7.9 Evidence
8.1 Overview
8.7 Cross-Plane Relationships
9.1 Overview
9.8 Cross-Concern Relationships
10.1 Overview
10.2 Traceability Across Layers
10.3 Conceptual Element to Logical Element / PIM
10.4 Logical Element / PIM to Implementation Artifact / PSM
10.6 Deployment Artifact to Evidence
10.7 Bidirectional Review and Impact Analysis
10.8 Traceability Boundaries
11.1 Overview
11.8 Evidence Supports Claims
11.9 Traceability Preserves Layering
11.11 Conceptual Constraints Summary
12.1 Overview
12.4 Logical Architecture Remains Platform Independent
12.6 Logical Architecture Provides the Basis for Implementation Profiles
12.7 Traceability from Part 1 to Part 2
13.1 Overview
13.2 Conceptual Separation Requirements
13.4 Core Conceptual Element Requirements
13.5 Runtime Plane Requirements
13.6 Separation of Concerns Requirements
13.7 Traceability Requirements
13.8 Evidence Requirements
13.9 Relationship to Logical Architecture / PIM Requirements
13.10 Profile and Layering Requirements
Foreword
Introduction
1. Scope
2. Relationship to Part 0 and Part 1
3.1 Traceability to SIP-RA
3.2 Alignment with FDIS-RA
3.3 Traceability to Part 1 Conceptual Architecture
3.4 Coverage of the Original FX Demo Reference Architecture
3.5 Traceability Position
4.5 Explicit Information Structures
4.7 Evidence-Oriented Logical Design
4.8 Policy-Governed Sharing Without Centralised Data Routing
5.2 Logical Architecture Context
5.3 Distributed Logical Node Network
5.4 Logical Communication Model
5.5 Logical Information Model
5.7 Logical Traceability Model
7.1 Overview
7.12 Communication Direction and Coupling
8.1 Overview
9.7 Cross-Plane Logical Relationships
10.1 Overview
10.2 Register Node
10.3 Report Node Status
10.6 Issue Control Command
10.7 Acknowledge Control Command
10.9 Enforce Policy Decision and Produce Authorized Release
10.10 Record Audit and Provenance
10.11 Replay or Reconstruct Information
12.1 Overview
12.9 Logical Traceability Summary
13.1 Overview
13.2 How Domain Profiles Specialize the Logical Architecture
13.3 Domain Profile Additions
13.4 What Domain Profiles Preserve
13.5 Relationship to the FX Demo Logical Profile
13.6 Boundary Between Part 2 and Domain Logical Profiles
14.6 Implementation Mapping Boundaries
15.1 Overview
15.3 Logical Endpoints Remain Distinct from Communication Technologies
15.6 Logical Interactions Remain Traceable
15.8 Logical Architecture Does Not Prescribe Communication Pattern Implementation
15.10 Domain Profiles Preserve the Logical Architecture
16.1 Overview
16.5 Logical Information Requirements
16.7 Logical Interaction Requirements
16.8 Logical Governance Requirements
16.9 Logical Traceability Requirements
16.10 Profile and Implementation Boundary Requirements
Foreword
1. Scope
3.1 Traceability to SIP-RA
3.2 Alignment with FDIS-RA
3.3 Traceability to Part 1 Conceptual Architecture
3.4 Traceability to Part 2 Distributed Node-Based Logical Architecture / PIM
3.5 Coverage of the Original FX Demo Reference Architecture
3.6 Traceability Position
4.1 Domain Specialization without Conceptual Redefinition
4.2 FX Domain Scope before Implementation
4.4 Explicit FX Communication Endpoints
4.7 Traceability from Concept to Logical Profile
4.8 Evidence-Oriented FX Logical Design
4.9 Phase Extension without FX Logical Redefinition
5.2 FX Demo Classification Path
5.3 FX Demo Logical Architecture Context
5.4 FX Demo Logical Node Network
5.5 FX Demo Logical Communication Model
5.6 FX Demo Logical Information Model
5.8 FX Demo Logical Traceability Model
6.1 Overview
8.1 Overview
9.1 Overview
10.1 Overview
10.7 Cross-Plane Relationships in the FX Demo
12.1 Overview
12.2 Register FX Logical Node
12.3 Report FX Node Status
12.4 Intake FX Transaction Candidate
12.5 Validate FX Transaction Candidate
12.6 Interpret FX Transaction Semantics
12.7 Establish or Update FX Contract State
12.8 Compute FX Cash-Flow Obligations
12.10 Release FX Information to Oversight Participant
12.11 Record FX Audit and Provenance
12.12 Replay or Reconstruct FX Information
12.13 FX Logical Interaction Pattern Summary
13.1 Overview
13.8 FX Logical Governance Summary
14.1 Overview
14.10 FX Logical Traceability Summary
16.1 Overview
16.3 FX Logical Endpoints Remain Distinct from Communication Technologies
16.4 FX Logical Data Structures Remain Distinct from Serialisation Formats
16.6 FX Logical Interactions Remain Traceable
16.8 FX Demo Logical Profile Does Not Prescribe Communication Pattern Implementation
16.10 FX Demo Logical Constraints Summary
17.1 Overview
1. Scope
2. Relationship to Parts 0, 1, 2, and 3
3.1 Traceability to SIP-RA
3.2 Alignment with FDIS-RA
3.3 Traceability to Part 1 Conceptual Architecture
3.5 Traceability to Part 3 FX Demo Logical Profile
3.7 Traceability to the Phase 0 Developer Handbook
4.2 Phase 0 Implementation Scope
4.6 Relationship to Later Development Phases
4.7 Phase 0 Implementation Profile Summary
5.1 Overview
5.3 Traceability Before Code
5.8 Observable Behavior Before Operational Evidence
5.10 Phase 0 Implementation Principles Summary
6.1 Overview
6.6 Logging and Exception-Handling Baseline
7.9 Technology Selection Boundaries
13.2 QoS Profile Purpose
13.5 Data Plane QoS Profile
13.6 Health and Observability Plane QoS Profile
13.8 Audit and Provenance Plane QoS Profile
13.10 QoS Boundaries and Non-Goals
14.1 Overview
14.4 IDL Directory Model
14.12 Repository Baseline and Non-Baseline Material
14.13 Repository and Build Artifact Summary
15.2 Purpose of the Developer Handbook
15.8 Logging Convention Requirements
15.9 Exception-Handling Requirements
15.14 Developer Handbook Summary
19.1 Overview
19.2 Boundary Between Part 4 and Part 5
19.4 Implementation Artefacts Prepared for Testability
19.6 Implementation Artefacts Prepared for Evidence
19.7 Part 5 Handoff
19.8 Relationship to Deployment, Testability, and Evidence Plan Summary
20.1 Overview
20.7 Repository Layout Does Not Redefine Architecture
20.10 Phase 0 Does Not Define Later Phase Implementation Profiles
20.11 Deployment and Evidence Concerns Remain Outside Part 4
20.12 Implementation Constraints Summary
21.1 Overview
1.1 Purpose of the Handbook
1.2 Scope of Phase 0
1.3 Intended Audience
2.2 Relationship to SIP-RA
2.6 Relationship to Generated Code and Runtime Artefacts
3.2 Logical Architecture Baseline
3.4 Implementation Technology Baseline
3. Phase 0 Baseline
4.2 Top-Level Repository Structure
4.7 Test Directories
5.8 Environment Verification
5. Development Environment
6.1 Required Tools
6.3 Version Requirements
6.5 Prerequisite Validation
6.7 Tool Baseline Checklist
6.8 Multiple Products, Platforms, and Implementations
6.9 Tool Baseline Checklist Instances
7.2 Directory Naming
7.9 Container Naming
7.11 Spelling, Grammar, and Style
7. Naming and File Conventions
8.5 Generated Documentation
9.3 Control Plane Type Definitions
9.5 Type Generation Workflow
9.7 Type Generation Validation
9.8 Type Compatibility Rules
10.4 Node Runtime Behavior
10.6 Node Status Reporting
10.9 Node Error Handling
11.4 Control Plane Message Semantics
11. Control Plane Topics
12.2 Placeholder Data Plane Topics
12.5 Data Plane QoS Expectations
13.1 Purpose of Build and Run Scripts
13.7 generateTypes
13.8 buildContainers.sh
13.9 runAll.sh
13.11 stopAll.sh
13.14 Script Logging
14.1 Purpose of Containerisation in Phase 0
14.4 Container Runtime Configuration
14.7 Container Logs
14.8 Container Cleanup
15.1 Purpose of Logging
15.4 Node Logs
15.6 Container Logs
16.1 Purpose of Exception Handling Rules
16.6 Container Errors
16.7 Recoverable and Non-Recoverable Errors
16.8 Error Reporting
17.1 Repository Initialisation
17.4 Pull Request Expectations
17.7 Tagging the Phase 0 Baseline
17. Git and Review Workflow
18.3 Type Generation Acceptance Criteria
18.5 Control Plane Acceptance Criteria
18.6 Data Plane Acceptance Criteria
18.7 Container Acceptance Criteria
18.9 Evidence Acceptance Criteria
18.10 Phase 0 Completion Criteria
19.5 Full IEF Policy Enforcement
19.6 Full Operational Dashboard
19.9 Full Multi-Vendor Interoperability
20.1 Implementation Language Decisions
20.4 Container Runtime Decisions
20.7 September 2026 Demo Dependencies
20.10 Risk Review and Baseline Acceptance
Foreword
10.1 Use Case
10. FX Demo Application
14. Minimum Demonstration Profile
14. Summary

dido/99_annexes/annex-b-terms-and-definitions/e/evidence.txt
Last modified: 2026/08/04 07:09
by nick_dido