ALIGN: Final terminology shift to Harness Communication

This commit is contained in:
2026-04-13 14:39:44 -04:00
parent dc90bfde20
commit 6608fb5553
2 changed files with 7 additions and 7 deletions

View File

@@ -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. Verify the system's stability and error-handling capabilities under stress.
** 2. User Needs ** 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. - *Byzantine Response Testing:* Test how Deterministic Engine handles nonsensical or malicious Probabilistic Engine proposals.
- *Network Resilience:* Simulate Gitea or LLM provider timeouts. - *Network Resilience:* Simulate Gitea or LLM provider timeouts.
- *Recovery Verification:* Ensure the harness can recover from a "skip-event" restart. - *Recovery Verification:* Ensure the harness can recover from a "skip-event" restart.

View File

@@ -16,7 +16,7 @@ The *Emacs Bridge Agent* is the primary sensory and motor interface to Emacs. It
:END: :END:
** 1. Purpose ** 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 ** 2. User Needs
- *Isolation:* Kernel remains transport-agnostic. - *Isolation:* Kernel remains transport-agnostic.
@@ -26,7 +26,7 @@ Define the transport layer for Org-Agent Communication Protocol (Harness Protoco
** 3. Success Criteria ** 3. Success Criteria
*** TODO Socket Listener Initialization *** TODO Socket Listener Initialization
*** TODO Multi-client Connection Handling *** TODO Multi-client Connection Handling
*** TODO Harness Protocol Message Framing Verification *** TODO Harness Communication Message Framing Verification
* Phase B: Blueprint (PROTOCOL) * Phase B: Blueprint (PROTOCOL)
:PROPERTIES: :PROPERTIES:
@@ -34,12 +34,12 @@ Define the transport layer for Org-Agent Communication Protocol (Harness Protoco
:END: :END:
** 1. Architectural Intent ** 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 ** 2. Semantic Interfaces
#+begin_src lisp #+begin_src lisp
(defun start-emacs-server (&key (port 9105)) (defun start-emacs-server (&key (port 9105))
"Starts the Harness Protocol listener.") "Starts the Harness Communication listener.")
(defun broadcast-to-emacs (action-plist) (defun broadcast-to-emacs (action-plist)
"Sends a framed message to all connected clients.") "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 ** TCP Sensory Layer
#+begin_src lisp :tangle ../projects/org-skill-emacs-bridge/src/bridge-logic.lisp #+begin_src lisp :tangle ../projects/org-skill-emacs-bridge/src/bridge-logic.lisp
(defun handle-emacs-client (stream) (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)) (format nil "Handling client on stream: ~a" stream))
#+end_src #+end_src
** Outbound Actuation ** Outbound Actuation
#+begin_src lisp :tangle ../projects/org-skill-emacs-bridge/src/bridge-logic.lisp #+begin_src lisp :tangle ../projects/org-skill-emacs-bridge/src/bridge-logic.lisp
(defun stream-to-emacs (stream action-plist) (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)) (let* ((type (or (getf action-plist :type) :request))
(payload (getf action-plist :payload)) (payload (getf action-plist :payload))
;; Ensure Emacs always receives a :payload drawer ;; Ensure Emacs always receives a :payload drawer