From 6608fb5553f35857a5d65cbed1682afdce230b53 Mon Sep 17 00:00:00 2001
From: Amr Gharbeia <amr@gharbeia.net>
Date: Mon, 13 Apr 2026 14:39:44 -0400
Subject: [PATCH] ALIGN: Final terminology shift to Harness Communication

---
 org-skill-chaos.org        |  2 +-
 org-skill-emacs-bridge.org | 12 ++++++------
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/org-skill-chaos.org b/org-skill-chaos.org
index 0aca5fc..2617c06 100644
--- a/org-skill-chaos.org
+++ b/org-skill-chaos.org
@@ -20,7 +20,7 @@ The *Chaos Gauntlet* is an adversarial testing skill designed to ensure the syst
 Verify the system's stability and error-handling capabilities under stress.
 
 ** 2. User Needs
-- *Failure Simulation:* Ability to inject artificial delays or errors into the Harness Protocol bus.
+- *Failure Simulation:* Ability to inject artificial delays or errors into the Harness Communication bus.
 - *Byzantine Response Testing:* Test how Deterministic Engine handles nonsensical or malicious Probabilistic Engine proposals.
 - *Network Resilience:* Simulate Gitea or LLM provider timeouts.
 - *Recovery Verification:* Ensure the harness can recover from a "skip-event" restart.
diff --git a/org-skill-emacs-bridge.org b/org-skill-emacs-bridge.org
index 422e4d6..5827dc9 100644
--- a/org-skill-emacs-bridge.org
+++ b/org-skill-emacs-bridge.org
@@ -16,7 +16,7 @@ The *Emacs Bridge Agent* is the primary sensory and motor interface to Emacs. It
 :END:
 
 ** 1. Purpose
-Define the transport layer for Org-Agent Communication Protocol (Harness Protocol).
+Define the transport layer for Org-Agent Communication Protocol (Harness Communication).
 
 ** 2. User Needs
 - *Isolation:* Kernel remains transport-agnostic.
@@ -26,7 +26,7 @@ Define the transport layer for Org-Agent Communication Protocol (Harness Protoco
 ** 3. Success Criteria
 *** TODO Socket Listener Initialization
 *** TODO Multi-client Connection Handling
-*** TODO Harness Protocol Message Framing Verification
+*** TODO Harness Communication Message Framing Verification
 
 * Phase B: Blueprint (PROTOCOL)
 :PROPERTIES:
@@ -34,12 +34,12 @@ Define the transport layer for Org-Agent Communication Protocol (Harness Protoco
 :END:
 
 ** 1. Architectural Intent
-Interfaces for TCP I/O and protocol framing. Source of truth is the Harness Protocol specification.
+Interfaces for TCP I/O and protocol framing. Source of truth is the Harness Communication specification.
 
 ** 2. Semantic Interfaces
 #+begin_src lisp
 (defun start-emacs-server (&key (port 9105))
-  "Starts the Harness Protocol listener.")
+  "Starts the Harness Communication listener.")
 
 (defun broadcast-to-emacs (action-plist)
   "Sends a framed message to all connected clients.")
@@ -50,14 +50,14 @@ Interfaces for TCP I/O and protocol framing. Source of truth is the Harness Prot
 ** TCP Sensory Layer
 #+begin_src lisp :tangle ../projects/org-skill-emacs-bridge/src/bridge-logic.lisp
 (defun handle-emacs-client (stream)
-  ;; Logic for parsing length-prefixed Harness Protocol messages
+  ;; Logic for parsing length-prefixed Harness Communication messages
   (format nil "Handling client on stream: ~a" stream))
 #+end_src
 
 ** Outbound Actuation
 #+begin_src lisp :tangle ../projects/org-skill-emacs-bridge/src/bridge-logic.lisp
 (defun stream-to-emacs (stream action-plist)
-  "Streams a chunk of data to a specific Emacs client over Harness Protocol using framing."
+  "Streams a chunk of data to a specific Emacs client over Harness Communication using framing."
   (let* ((type (or (getf action-plist :type) :request))
          (payload (getf action-plist :payload))
          ;; Ensure Emacs always receives a :payload drawer