C.2 Operational Requirements
This section identifies the requirements governing the operation of the capabilities, services, and realizations that satisfy this specification's requirements.
Operational Requirements address the conditions under which distributed verification and testing operate across organizational, administrative, technical, jurisdictional, and governance boundaries.
These requirements govern operational behavior and constraints without prescribing a particular product, implementation, or realization technology.
The requirements in this section derive from the source documents identified in Annex B. Some requirements derive directly from those sources. Others normalize or decompose source concepts into individually verifiable architectural obligations.
Operational Requirements are distinct from Functional Requirements. Functional Requirements define the capabilities and behavior the architecture provides. Operational Requirements define conditions, constraints, responsibilities, and operating characteristics applicable when those capabilities are used.
Requirements
| Requirement ID | Requirement Title | Primary Source Basis |
|---|---|---|
| OPR-001 | Support Distributed Operation | <source basis> |
| OPR-002 | Operate Across Governance Boundaries | <source basis> |
| OPR-003 | Identify Applicable Governance Context | <source basis> |
| OPR-004 | Preserve Governance Determinations | <source basis> |
| OPR-005 | Escalate Unresolved Conflicts | <source basis> |
| OPR-006 | Operate Across Organizational Boundaries | <source basis> |
| OPR-007 | Preserve Traceability Across Boundaries | <source basis> |
| OPR-008 | Preserve Evidence Across Boundaries | <source basis> |
Contents
Notes for Editors
Derive the Operational Requirements from the applicable source requirements, governance constraints, operational concepts, and ConOps material before creating individual OPR requirement pages.
Add explicit links to proposed OPR requirement pages under Contents while the requirement set is being created. Remove the explicit links after the pages are finalized because the indexmenu automatically discovers them.
Operational Requirements use the OPR requirement prefix.
Do not place Test Environment, Node, Test Definition, Test Execution, or other capability-specific Functional Requirements in this section.
Do not use Operational Requirements to prescribe Crucible, DevSecOps, or another specific realization unless the requirement explicitly governs interoperability with that realization.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.