Add REST bridge for AtomSpace / CogServer integration demo #38
+228
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a minimal REST bridge module that provides HTTP access to the OpenCog CogServer Scheme shell for external tools and services. The bridge enables remote submission of Atomese/Scheme code into the AtomSpace and returns raw evaluation output, allowing integration with Python scripts, LLM orchesators, and other experimental clients without modifying existing CogServer internals.
The implementation consists of a lightweight FastAPI server maintaining a persistent telnet connection to CogServer, a basic /atomese POST endpoint, and placeholder Scheme helpers for future reasoning workflows. End-to-end functionality has been manually verified by executing atom creation commands through REST and receiving live evaluation results from the AtomSpace. No semantic parsing, agent logic, or post-processing is included — the bridge is intentionally infrastructure-only.
This module establishes the basic external interface needed to support ongoing research into LLM–symbolic co-reasoning and long-term neuro-symbolic memory systems. It is placed under stream/rest-bridge as an experimental component aligned with the directory’s broader streaming infrastructure goals, while leaving all higher-level cognitive control design for future work.