Annex D: Requirements Traceability

Go to Crucible

Annex D maps the canonical leaf requirements in Annex C: Requirements to the Crucible pages that reference them.

Annex C remains the canonical source for requirement titles, Statements, rationale, and verification information. Annex D provides traceability links and coverage information without restating or redefining the requirements.

Requirements Traceability Index

The Requirements Traceability Index lists the canonical leaf requirements alphabetically by title.

The Requirement Title column links to the canonical requirement page. The Referenced By column identifies the Crucible pages that link to that requirement.

A requirement with no references requires review to determine whether:

The requirement lacks ConOps coverageThe requirement belongs outside the ConOpsThe requirement represents a future capabilityThe requirement page or backlink is incompleteThe requirement requires an additional operational page

D.1 Requirements Traceability Index

Go to Annex D: Requirements Traceability

Requirement Title	Referenced By
Authority to Operate Evidence
Baseline Composition
Baseline Workspace Preparation
Baseline-Only Composition
Version-Controlled Baseline Selection
Classified Environment Operations
Command-Line Interface
Compliance Baseline Definitions
Compliance Evidence Artifacts
Compliance Finding Transfer Bundle Inclusion
Compliance Finding Association Preservation
Compliance Reporting
Compliance Scanning Abstraction
Compliance Scanning Tool Integration
Container Image Construction
Cross-Domain Transfer Control
Custom Compliance Frameworks
Dependency Capture
Dependency Preservation
Dependency Store Representation
Deploy Infrastructure Resources
Deploy Containerized Workloads
Deploy Kubernetes Clusters
Deploy Platform Services
Deploy Virtual Machines
Deployment Validation
DISA STIG Compliance Baselines
FedRAMP Baseline Definitions
Edge Deployment Support
Hybrid-Cloud Deployment Support
Image Promotion Workflows
Image Signing
Image Verification
Immutable Infrastructure Workflows
Information Handling Rule Enforcement
Multiple Operating-System Support
Offline Repository Population
Operating-System-Independent Compliance Scanning
Provider Abstraction
Provider-Specific Extensions
Provider Deployment Portability
Risk Management Framework Evidence
Security Domain Access Control
Security Domain Information Enforcement
Security Domain Resource Enforcement
Security Control Traceability Matrix Evidence
Shared Interface Operations
Transfer Bundle Production
Unclassified Environment Operations
Virtual Machine Image Construction
Web-Based User Interface

Notes for Editors

Confirm each displayed title against the canonical requirement pageAdd every remaining Annex C leaf requirementExclude parent requirements that contain child requirementsRetain start for leaf requirements implemented as namespace index pagesSort the final table alphabetically by canonical displayed titleA requirement with no returned backlinks requires coverage review

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

Contents

Traceability Rules

The traceability information follows these rules:

Include only canonical leaf requirementsTreat a requirement implemented as a namespace start page as a leaf when it has no child requirementsExclude parent requirements that have leaf childrenLink each requirement title to its canonical Annex C pageSort the Requirements Traceability Index alphabetically by displayed titleIdentify every Crucible page that directly references the requirementDo not copy or paraphrase the canonical requirement StatementRecord requirements without references as uncovered until reviewedRecord ConOps pages without supporting requirements as unsupported until reviewed

Coverage Status

Detailed traceability pages can use the following coverage statuses:

Status	Meaning
Complete	The referenced Crucible content provides operational coverage consistent with the requirement Statement
Partial	The referenced content addresses only part of the requirement Statement
Not Covered	No current Crucible page provides identifiable coverage
Outside ConOps Scope	The requirement applies to another specification, design, implementation, verification, or governance artifact
Future Capability	The requirement applies to a capability outside the current operational baseline
Review Required	The available requirement or coverage information is insufficient to determine the appropriate status

Relationship to Annex E

Annex E: Issues records problems discovered during traceability review.

Examples include:

A requirement without operational coverageA ConOps capability without a supporting requirementA requirement that requires further decompositionAn ambiguous or incomplete requirement StatementAn incorrect parent or leaf classificationA missing requirement pageAn inconsistent requirement namespace or titleA proposed future capabilityAnnex D records the traceability condition. Annex E records the issue and its resolution status.

Notes for Editors

Populate the Requirements Traceability Index only after confirming the complete Annex C leaf-requirement inventory.

Do not list true parent requirements when their leaf children provide the normative Statements.

Where a leaf requirement uses a namespace start page for numerical ordering, link to the actual start page.

The Referenced By column should derive from direct links to the canonical requirement page wherever the available DokuWiki backlink mechanism permits dynamic generation.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.