[SUPERSEDED] Parallel DeepSeek Harness frontend backed by Prolog-RLM semantics #124

New issue

Closed

opened 2026-08-19 14:37:18 +00:00 by lost-rob0t · 2 comments

lost-rob0t commented

2026-08-19 14:37:18 +00:00

(Migrated from github.com)

Build a parallel downstream PrologAgent implementation from the official MIT-licensed deepseek-ai/deepseek-harness surface while keeping prolog-rlm authoritative.

Required invariants:

DeepSeek Harness is a frontend/host/client substrate, not a second generic agent runtime.
Prolog owns the coding loop, tools/capabilities, authority, effects, context compilation, persistence, and tracing.
Conversation history is durable and append-only. Do not summarize/compact away historical turns. Provider-visible context may be bounded, but omitted history remains losslessly accessible through the Prolog-RLM conversation context handle.
Disable/bypass DeepSeek Harness compaction semantics for canonical Prolog-backed sessions.
Preserve and persist user/project settings, including provider/model selections and Prolog-RLM session/runtime options.
Support DeepSeek and OpenRouter provider routes. Reuse existing OpenRouter support where available rather than introducing a parallel provider implementation.
Preserve upstream DeepSeek MIT attribution and pin the imported upstream revision.
Keep this implementation parallel to the existing native agentProlog renderer work; do not regress prolog_agent_ui_v1.

First slice should establish the pinned upstream boundary, a Prolog bridge protocol, durable settings/session ownership, no-compaction contract, provider routing, tests, and documentation. Follow-up slices can deepen UI coverage and tool/approval presentation.

Build a parallel downstream PrologAgent implementation from the official MIT-licensed `deepseek-ai/deepseek-harness` surface while keeping `prolog-rlm` authoritative. Required invariants: - DeepSeek Harness is a frontend/host/client substrate, not a second generic agent runtime. - Prolog owns the coding loop, tools/capabilities, authority, effects, context compilation, persistence, and tracing. - Conversation history is durable and append-only. Do not summarize/compact away historical turns. Provider-visible context may be bounded, but omitted history remains losslessly accessible through the Prolog-RLM conversation context handle. - Disable/bypass DeepSeek Harness compaction semantics for canonical Prolog-backed sessions. - Preserve and persist user/project settings, including provider/model selections and Prolog-RLM session/runtime options. - Support DeepSeek and OpenRouter provider routes. Reuse existing OpenRouter support where available rather than introducing a parallel provider implementation. - Preserve upstream DeepSeek MIT attribution and pin the imported upstream revision. - Keep this implementation parallel to the existing native `agentProlog` renderer work; do not regress `prolog_agent_ui_v1`. First slice should establish the pinned upstream boundary, a Prolog bridge protocol, durable settings/session ownership, no-compaction contract, provider routing, tests, and documentation. Follow-up slices can deepen UI coverage and tool/approval presentation.

lost-rob0t commented

2026-08-25 02:13:22 +00:00

(Migrated from github.com)

ADARD checkpoint

Plugin-only DeepSeek Harness core research/design is now recorded in #184: https://github.com/lost-rob0t/prolog-rlm/issues/184

#184 is AWAITING APPROVAL. It narrows the first milestone to the official unmodified Harness Web/headless surfaces + one out-of-tree Prolog-backed AgentFactory plugin + a narrow Prolog bridge + Nix integration. It explicitly rejects treating the current broad #125 implementation as automatically approved scope.

RAGE must not begin on this redesign until #184 is explicitly approved.

## ADARD checkpoint Plugin-only DeepSeek Harness core research/design is now recorded in **#184**: https://github.com/lost-rob0t/prolog-rlm/issues/184 #184 is **AWAITING APPROVAL**. It narrows the first milestone to the official unmodified Harness Web/headless surfaces + one out-of-tree Prolog-backed `AgentFactory` plugin + a narrow Prolog bridge + Nix integration. It explicitly rejects treating the current broad #125 implementation as automatically approved scope. RAGE must not begin on this redesign until #184 is explicitly approved.

lost-rob0t commented

2026-08-25 03:10:38 +00:00

(Migrated from github.com)

Superseded by the approved plugin-only Harness architecture in #184 and cleanup/cutover work in #186. This older parallel-Harness direction should not be used as implementation authority.