Differences

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

--- dido:99_annexes:annex-d-requirements:part-04:p4-req-21-12-006 [2026/08/07 14:30] – created owen
+++ dido:99_annexes:annex-d-requirements:part-04:p4-req-21-12-006 [2026/08/07 14:30] (current) – owen
@@ Line 1: / Line 1: @@
-====== P4-REQ-21-12-005 ======
+====== P4-REQ-21-12-006 ======
 [[dido:99_annexes:annex-d-requirements:part-04:start| Return to Requirements]]
@@ Line 5: / Line 5: @@
 ===== Statement =====
-Each approved script SHALL identify the artifacts it affects.
+Each approved script SHALL identify its logging behavior.
 ===== Source =====
@@ Line 13: / Line 13: @@
 ===== Rationale =====
-Scripts may create, modify, generate, start, stop, move, or remove implementation artifacts.
+Script logging provides observable information about invocation, activity, outcome, warnings, failures, and cleanup.
-Identifying affected artifacts allows reviewers to understand the scope of script activity and determine whether applicable repository, generation, governance, or Developer Handbook rules apply.
+Defining logging behavior allows script execution to be reviewed consistently and supports troubleshooting, operational review, and later evidence planning.
 ===== Applies To =====
@@ Line 21: / Line 21: @@
 This requirement applies to:
-  * governed source artifacts;
+  * approved scripts;
-  * generated artifacts;
+  * script invocation logging;
-  * configuration artifacts;
+  * script task logging;
-  * build artifacts;
+  * warning and failure logging; and
-  * repository state; and
+  * cleanup reporting.
-  * runtime implementation participants.
 ===== Verification =====
-Verification SHALL confirm that each approved script identifies the artifacts it affects.
+Verification SHALL confirm that each approved script identifies its logging behavior.
 Verification activities should include review checks confirming that:
-  * files created or modified are identified;
+  * invocation information is logged where required;
-  * generated artifacts affected are identified;
+  * performed tasks are identifiable;
-  * configuration or repository state affected is identified;
+  * outcomes are reported;
-  * runtime participants affected are identified where applicable; and
+  * warnings and errors are reported; and
-  * artifact effects are consistent with the script's approved purpose.
+  * logging follows the Developer Handbook.
 ===== Traceability =====
-This requirement connects approved scripts to the Phase 0 implementation artifacts and state they affect.
+This requirement connects script execution to the Phase 0 logging conventions defined by the Developer Handbook.
 Related requirement identifiers:
-  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-12-004]]
+  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-12-007]]
-  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-12-008]]
+  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-11-006]]
-  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-12-011]]
 Related source section: