Files
memex/system/plans/flight-plan-neuro-microkernel.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.7 KiB

Flight Plan: Neuro Microkernel Architecture

Overview

Decouple HTTP request logic from the core neuro kernel (`neuro.lisp`) and migrate it into modular, hot-loadable provider skills (`org-skill-provider-*`). This ensures absolute modular sovereignty.

Phase A: Demand (PRD)

  • Current state: `neuro.lisp` contains HTTP logic for Groq, OpenRouter, and Gemini.
  • Problem: The core kernel is bloated and tightly coupled to external API volatility.
  • Solution: Move HTTP logic to `org-skill-provider-*` modules. The kernel's `ask-neuro` becomes a pure interface.

Phase C: Success (Quality - Analyst Phase)

  • TDD Requirement: Create `projects/passepartout/tests/neuro-test.lisp` containing assertions for the new `ask-neuro` contract.
  • The tests MUST be executed and PROVE failure before any code is modified.
  • Tests will assert that:

    1. `ask-neuro` fails gracefully when the `*neuro-backends*` registry is empty.
    2. `ask-neuro` succeeds when a mock provider is registered and correctly delegates the prompt to the mock function.

Phase D: Build (Engineering - Coder Phase)

  • Strip `execute-openrouter-request`, `execute-groq-request`, and `execute-gemini-request` from `projects/passepartout/docs/README.org`.
  • Draft `notes/org-skill-provider-openrouter.org`.
  • Draft `notes/org-skill-provider-groq.org`.
  • Draft `notes/org-skill-provider-gemini.org`.
  • Tangle updated `README.org` and new skills.

Phase E: Chaos (Chaos Phase - Final Verification)

  • Hot-load the refactored core and new provider skills.
  • Run `neuro-test.lisp` and PROVE it passes.
  • Inject a complex chat stimulus and monitor `opencortex-repl.log` for successful autonomous execution.