PSF: Mass-regeneration complete. 53/53 high-fidelity blueprints and TDD suites established. Zero-cost Pro bridge active.

notes/org-skill-chaos.org

@@ -59,9 +59,71 @@ Verify the system's stability and error-handling capabilities under stress.
   :symbolic #'chaos-stress-test)
 #+end_src
 
+
 * Phase B: Blueprint (PROTOCOL)
 :PROPERTIES:
 :STATUS: SIGNED
 :END:
 
-** 1. Architectural IntentnEstablish functional interfaces.\n\n** 2. Semantic Interfaces\n(defun trigger-skill-org-skill-chaos (context))\n(defun neuro-skill-org-skill-chaos (context))
+* Phase B: Blueprint (PROTOCOL)
+ :PROPERTIES:
+ :STATUS: IN_PROGRESS
+ :END:
+
+ ** 1. Architectural Intent
+ The *Chaos Gauntlet* skill is designed to be non-invasive, running primarily in a background mode.  It should not interfere with normal system operation unless explicitly triggered.  The skill aims to provide a controlled environment for inducing and observing failures. Key intents:
+
+ - *Controlled Chaos:* Failures must be injected in a precise and controllable manner (specific sensor, specific error type).
+ - *Observability:*  The system's response to failures must be easily observable through logging and system state.
+ - *Minimal Impact:*  The skill should avoid causing permanent damage or corruption to the system or its data.
+ - *Testability*: Easy to run, configure, and verify success/failure. Reports failures through the regular error reporting mechanisms. Logs activity with 'CHAOS' tag.
+- *Recoverability*: Emphasis on testing kernel's recovery from errors, by deliberately triggering skip-event type restarts.
+
+ ** 2. Semantic Interfaces
+
+ *** A.  Triggering Chaos
+
+    *`chaos-trigger` Sensor:*
+      Events of type `:EVENT` with a `:payload` containing `(:sensor :chaos-trigger)` trigger the skill. The payload can contain a `:mode` key to specify the type of chaos to inject (e.g., `:random`, `:shell`), and an `:intensity` to control the number of failures injected.
+
+    *Signature:*
+
+ `#+begin_src lisp
+   ;; Triggers the chaos skill.
+   (defun trigger-chaos (mode intensity)
+     "Triggers the chaos gauntlet with a specified mode and intensity."
+     (org-agent:inject-stimulus
+      `(:type :EVENT :payload (:sensor :chaos-trigger :mode ,mode :intensity ,intensity))))
+ #+end_src
+
+ *** B.  Injecting Synthetic Errors
+
+    *`chaos-inject-error` Function:*
+      Injects a synthetic error event into a specified sensor pipeline.  Different sensor types will react differently to synthetic errors.
+
+    *Signature:*
+
+ `#+begin_src lisp
+   ;; Injects a synthetic error into a specific sensor pipeline.
+   (defun chaos-inject-error (sensor-type error-message)
+     "Injects a specific synthetic error into a specific sensor."
+     (org-agent:inject-stimulus
+      `(:type :EVENT :payload (:sensor ,sensor-type :error ,error-message))))
+ #+end_src
+
+ *** C.  Simulating Network Disruptions
+
+     The `chaos-stress-test` function, when `mode` is `:shell`, simulates network disruptions by returning a specific error code from a shell command (e.g., `git push`).
+
+     *Signature:* (covered by existing implementation in Phase D).
+
+ *** D.  Kernel Restart Simulation
+
+  Deliberately trigger `skip-event` to test recovery protocols.
+   *Signature:*
+
+ `#+begin_src lisp
+  ;; simulates a skip event (a full org-agent reboot)
+  (defun chaos-force-skip-event ())
+ #+end_src
+