Files
memex/system/plans/flight-plan-emacs-bridge.org
Amr Gharbeia 4f34969224 rename: opencortex → passepartout across memex
- .gitmodules: update submodule paths (projects/opencortex → projects/passepartout,
  projects/opencortex-contrib → projects/passepartout-contrib)
- gtd.org, README.org: update project references and display names
- check.lisp, gemini-vision.org, agora/TODO.org: update file paths
- dotemacs: update agenda paths and template config
- system/plans/: update all flight plan references
- system/backups/: update monolithic backup references
2026-05-03 11:47:52 -04:00

1.1 KiB

Flight Plan: Emacs Harness Protocol Outbound Bridge

Analyst Phase

The current opencortex kernel is a "one-way" sensory system. It receives stimuli from Emacs via Harness Protocol but lacks the physical plumbing to send responses back over the same socket. To fix this, we must:

  1. Modify the kernel (literately) to pass the client TCP stream through the cognitive loop.
  2. Implement the skill-emacs-bridge logic to capture this stream and perform framed Harness Protocol writes.
  3. Update the skill-chat to utilize the new bridge.

Coder Phase

  • Create inbox/flight-plan-emacs-bridge.org (this file).
  • Update projects/passepartout/docs/README.org (Literate Kernel) with the stream-passing hook.
  • Update notes/org-skill-emacs-bridge.org to implement the Harness Protocol outbound writer.
  • Tangle the updated files.
  • Rebuild the daemon binary.

Tester Phase

  1. Tangle all modified files.
  2. Restart the daemon.
  3. Run the test-chat.lisp script to verify two-way communication.
  4. Verify in Emacs *opencortex-chat*.