docs: add Reactive Signal Pipeline evolution design

README.org

@@ -1153,6 +1153,25 @@ To call a tool, you MUST use:
     (maphash (lambda (id obj) (declare (ignore id)) (when (equal (getf (org-object-attributes obj) attr-key) attr-val) (push obj results))) *object-store*)
     results))
 #+end_src
+
+** [EVOLUTION] Component VII: The Reactive Signal Pipeline
+*** Deep Reasoning: Beyond the recursive loop
+The current `cognitive-loop` is a recursive process that handles sensors and tools as distinct code paths. While functional, it is difficult to parallelize and observe. 
+- **The Circuit Board Model:** We are evolving the kernel into a functional transformation pipeline. Every event—be it a keystroke, a timer pulse, or a neural proposal—is a **Signal**.
+- **Consensus Gates:** By treating reasoning as a signal moving through a pipe, we can "split" the pipe to ask multiple LLMs simultaneously. A **Consensus Gate** later in the pipe compares the proposals and selects the most mathematically consistent one.
+- **Multi-Modal Fusion:** The pipeline can blend disparate signals (e.g. *User Prompt* + *Low Battery Alert*) into a single coherent cognitive event.
+
+*** The Signal Architecture
+#+begin_src mermaid
+graph LR
+    S1[Signal: User Message] --> P[Perceive Gate]
+    S2[Signal: Heartbeat] --> P
+    P --> N[Neuro Gate: Multi-Backend]
+    N --> C[Consensus Gate]
+    C --> V[Validation Gate: System 2]
+    V --> D[Dispatch Gate: Actuators]
+#+end_src
+
 * System Definition
 #+begin_src lisp :tangle org-agent.asd
 (defsystem :org-agent