====== MO-001 — Governed Distributed Test Environments ====== [[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to C.1 Mission Objectives]] ===== Statement ===== [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL maintain each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] as [[dido:99_annexes:annex-b-terms-and-definitions:g:governed|Governed]] throughout its [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]]. ===== Source ===== This requirement consolidates mission-level intent from the following Original Requirements in the draft DIDO-TE Requirements Register: * ''REQ-0001 — Three-level governance hierarchy'' * ''REQ-0002 — Governance organs per level'' * ''REQ-0003 — Membership request workflow'' * ''REQ-0005 — Legal documents per governance level'' * ''REQ-0006 — Additive-only legal-document inheritance'' * ''REQ-0008 — Domain access-control quadrant declaration'' * ''REQ-0009 — Tenancy isolation along governance boundaries'' * ''REQ-0010 — Domain-scoped environments'' * ''REQ-0086 — Substrate as a governed object with a recorded lifecycle'' The Original Requirements establish mission-level intent concerning: * A governance hierarchy * Governing [[dido:99_annexes:annex-b-terms-and-definitions:a:authority|Authorities]] * Governance organizations * Governance [[dido:99_annexes:annex-b-terms-and-definitions:r:role|Roles]] * [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_domain|Governance Domains]] * [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_policy|Governance Policies]] * Membership decisions * Authorization boundaries * Tenancy boundaries * Test Environment governance * Supporting-infrastructure governance * Operational Lifecycle governance MO-001 expresses the common mission-level outcome that each Test Environment remains Governed throughout its Operational Lifecycle. The supporting Operational, Functional, Security, Logging and Auditing, and Data Management requirements define the independently verifiable obligations governing: * Governance structures * Authority * Role assignments * Governance Policy application * Authorization * Isolation * Test Environment ownership * Operational Lifecycle transitions * Governance records * Governance Evidence ===== Rationale ===== A Test Environment can: * Allocate and consume [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resources]] * Use [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_resource|Operational Resources]] * Operate [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] * Operate [[dido:99_annexes:annex-b-terms-and-definitions:n:node_set|Node Sets]] * Use [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Targets]] * Perform [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] * Execute software * Exchange information * Access protected Resources * Create [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]] * Create [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] * Affect systems operated by multiple [[dido:99_annexes:annex-b-terms-and-definitions:o:organization|Organizations]] Each Test Environment requires an explicit governance context that identifies: * The governing Authority * The applicable Governance Domain * The governed Test Environment * The applicable scope * The applicable Organizations * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:community_of_interest|Communities of Interest]] * The responsible [[dido:99_annexes:annex-b-terms-and-definitions:a:actor|Actors]] * The applicable Roles * The applicable responsibilities * The applicable decision rights * The applicable Governance Policies * The applicable approval processes * The applicable change-control processes * The applicable exception and waiver processes * The applicable enforcement mechanisms * The applicable accountability mechanisms * The required Evidence * The required [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] * The required [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] Governance applies throughout the Operational Lifecycle of the Test Environment. Governance does not end after DIDO-TE creates, provisions, deploys, or activates the Test Environment. The supporting requirements define how DIDO-TE establishes, applies, evaluates, records, and enforces the applicable governance context. MO-001 establishes the mission-level outcome that the Test Environment remains Governed. ===== Applies To ===== This requirement applies to: * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:d:distributed_system|Distributed Systems]] * [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_domain|Governance Domains]] * Governing [[dido:99_annexes:annex-b-terms-and-definitions:a:authority|Authorities]] * [[dido:99_annexes:annex-b-terms-and-definitions:o:organization|Organizations]] * [[dido:99_annexes:annex-b-terms-and-definitions:c:community_of_interest|Communities of Interest]] * [[dido:99_annexes:annex-b-terms-and-definitions:a:actor|Actors]] * [[dido:99_annexes:annex-b-terms-and-definitions:r:role|Roles]] * [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_policy|Governance Policies]] * Test Environment operations * Test Environment [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resources]] * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_resource|Operational Resources]] * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_set|Node Sets]] * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Targets]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definitions]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Runs]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]] * [[dido:99_annexes:annex-b-terms-and-definitions:v:validation_decision|Validation Decisions]] * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]] * The [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] of each Test Environment ===== Verification ===== Verification confirms that: - Each Test Environment has an identified governance context - The governance context identifies the governing Authority - The governance context identifies the applicable Governance Domain - The governance context identifies the governed Test Environment - The governance context identifies its applicable scope - The governance context identifies the applicable Organizations and Communities of Interest - The governance context identifies the applicable Actors and Roles - The governance context identifies the applicable responsibilities and decision rights - The governance context identifies the applicable Governance Policies - The governance context identifies the applicable approval processes - The governance context identifies the applicable change-control processes - The governance context identifies the applicable exception and waiver processes - The governance context identifies the applicable enforcement mechanisms - The governance context identifies the applicable accountability and review processes - DIDO-TE applies the governance context to Test Environment operations - DIDO-TE evaluates each governed Test Environment operation according to the applicable Governance Policies - DIDO-TE applies the governance context throughout the Operational Lifecycle of the Test Environment - DIDO-TE applies the governance context in Connected, Disconnected, and Air-Gapped Environments - DIDO-TE preserves the Evidence required to demonstrate application of the governance context - DIDO-TE preserves Provenance for governance decisions and Test Environment operations - The verification record preserves Traceability among the Test Environment, governing Authority, Governance Domain, Actors, Roles, Governance Policies, governance decisions, Test Environment operations, Evidence, and verification result ===== Referenced By ===== The following pages reference this requirement: {{backlinks>.#dido:03-dido-te}} ===== Delivery Phase ===== TBD ===== Implementation Status ===== Assess the current DIDO-TE implementation against MO-001 and its supporting Operational, Functional, Security, Logging and Auditing, and Data Management requirements. ===== Requirement Status ===== Review and approve MO-001 as a proposed Mission Objective consolidated from the governance and Test Environment requirements in the draft DIDO-TE Requirements Register. ---- ===== Issues ===== The following unresolved issues affect this requirement: Define Governance in the shared DIDO Solutions Terms and Definitions corpus. Define the governance hierarchy applicable to DIDO-TE Test Environments. Define the relationship between a Test Environment and its governing Governance Domain. Define whether each Test Environment has one primary governing Governance Domain or can have multiple governing Governance Domains. Define the complete set of Test Environment operations governed by MO-001. Define how DIDO-TE identifies the governing Authority for a Test Environment. Define how DIDO-TE resolves Governance Policies inherited through the governance hierarchy. Define the precedence and conflict-resolution rules for Governance Policies established by different Authorities or at different levels of the governance hierarchy. Define the decision required when an applicable Governance Policy is missing, invalid, unavailable, or internally inconsistent. Define the Governance Evidence DIDO-TE preserves for each governance decision and Test Environment operation. Define the governance requirements applicable during each Test Environment Operational Lifecycle state and transition. ---- ===== Notes for Editors ===== This requirement page retains the stable requirement identifier ''MO-001''. This page is a leaf requirement page and omits a trailing '':start'' from its namespace. MO-001 consolidates mission-level intent from multiple Original Requirements. MO-001 does not result from splitting a single parent requirement and therefore uses a **Source** section rather than a **Derived From** section. Changes to the Statement preserve: * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] as the responsible Actor * Each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] as the governed subject * [[dido:99_annexes:annex-b-terms-and-definitions:g:governed|Governed]] as the required condition * The [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] as the temporal scope of the obligation The supporting requirements define: * The governance hierarchy * The governing Authorities * The Governance Domains * The relationship between each Test Environment and its Governance Domain * The applicable Actors and Roles * The applicable responsibilities * The applicable decision rights * The governed Test Environment operations * Governance Policy application * Governance Policy inheritance * Governance Policy precedence * Governance Policy conflict resolution * Authorization decisions * Tenancy isolation * Test Environment Operational Lifecycle governance * Governance records * Governance Evidence * Governance decision Provenance * Governance decision Traceability Material changes receive review and update the verification criteria, source records, supporting requirements, and Issues section. To reference this requirement Statement from another Wiki page, insert: {{section>dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-001#Statement&noheader&nofooter&noeditbtn}} Do not rename this page after an external citation unless a redirect or move plan is in place. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.