Differences

This shows you the differences between two versions of the page.

--- dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:start [2026/07/16 01:33] – nick_dido
+++ dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:start [2026/07/16 12:10] (current) – [C.1 Mission Objectives] nick_dido
@@ Line 3: / Line 3: @@
 [[dido:02-crusible:99-annexes:annex-c-requirements:start|Go to Crucible Requirements]]
-The Crucible Mission Objectives identify the high-level outcomes that guide the system requirements, architecture, implementation, operation, and lifecycle.
+The [[dido:99_annexes:annex-b-terms-and-definitions:m:mission_objective|Mission Objectives]] identify the high-level outcomes that guide the [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] requirements, architecture, implementation, operation, and [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]].
-The Mission Objectives address:
+These objectives address infrastructure creation, deployment duration, platform independence, connected and disconnected operation, reusable and version-controlled infrastructure, and lifecycle management.
-  * Rapid creation of repeatable, compliant, and secure infrastructure environments
+===== Contents =====
-  * Reduction of platform-deployment timelines through automation
-  * Cloud-agnostic deployment
-  * Connected and disconnected operations
-  * Reusable and version-controlled infrastructure
-  * Infrastructure lifecycle management
-===== Mission Objectives =====
+{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives#1|js navbar nocookie maxjs#1 id#crucible_mission_objectives_nav}}
-{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives#1|js navbar nocookie maxjs#2 id#crucible_mission_objectives_nav}}
-----
 ===== Notes for Editors =====
-This document should be maintained as a set of linked wiki pages rather than a single monolithic page. Each major section should have its own stable URI so it can be referenced from other wiki pages, exported documents, presentations, AI-assisted tools, and semantic models.
+The individual requirement pages should retain the stable identifiers ''MO-001'' through ''MO-006''.
+The source statements should preserve the wording from the controlling System Requirements Specification.
+Normalized statements should replace weak verbs and undefined qualifiers with direct, testable behavior and applicable acceptance criteria.
+Incoming traceability should use the wiki Backlinks function rather than a manually maintained list.
+To reference a requirement Statement from another wiki page, insert:
+<code dokuwiki>
+{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}
+</code>
+Replace ''<namespace>'' with the namespace of the requirement page to reference.
+The section name following ''#'' SHALL match the section heading verbatim on the requirement page.
-Do not rename pages once they have been cited externally unless a redirect or move plan is in place.
+Do not rename requirement pages after an external citation unless a redirect or move plan is in place.
 ----