The Fusion of symbolics and a ui
  • JavaScript 91.9%
  • Nix 8.1%
Find a file
nsaspy bd3df85b6d
Some checks failed
CI / flake (push) Failing after 2s
Zara Runtime Profile / profile-contract (push) Successful in 25s
Merge pull request #37 from lost-rob0t/fix/zara-profile-closed-set
fix(runtime): validate AgentProlog profile advertisement set
2026-09-19 09:20:34 -04:00
.github/workflows ci(zara): test optional AgentProlog profile 2026-09-18 11:22:09 -04:00
docs docs: design DeepSeek Harness plugin bridge 2026-08-25 01:14:54 -04:00
packages fix(runtime): validate advertised profile identities 2026-09-19 09:19:11 -04:00
flake.nix chore(zara): pin AgentProlog profile to merged Prolog-RLM bridge 2026-09-18 13:20:21 -04:00
README.md docs(zara): document optional AgentProlog runtime profile 2026-09-18 11:28:01 -04:00

AgentProlog

AgentProlog is the standalone coding-agent product built on lost-rob0t/prolog-rlm.

The repository owns product composition and UX. prolog-rlm remains the reusable SWI-Prolog runtime/library.

AgentProlog
  -> DeepSeek Harness / Cordis integration
  -> AgentFactory / frontend adapters
  -> product configuration and defaults
  -> coding workflow + coding tool packs
  -> public prolog-rlm APIs
  -> Prolog-RLM runtime

Dependency direction is strictly:

agentProlog -> prolog-rlm

Current state

The standalone packaging and persistent DSH/Prolog bridge substrate are on main.

Current DSH work is tracked in:

  • issue #7 — plugin-only DeepSeek Harness AgentFactory;
  • PR #8 — active executable AgentFactory slice.

The current integration uses the official DeepSeek Harness/Cordis surface as the workspace and presentation layer while keeping Prolog-RLM authoritative for provider/model calls, context compilation, tools, capabilities, authority, effects, conversations, agents/subagents, Spec/Plan/Verify, tracing, and usage.

The old nested prolog-rlm/agentProlog/ product harness has been removed upstream. Generic prolog_agent_ui_v1 protocol/facade behavior remains reusable runtime infrastructure in prolog-rlm.

Repository responsibilities

AgentProlog owns:

  • DeepSeek Harness / Cordis integration;
  • AgentFactory and frontend/session adapters;
  • product configuration and defaults;
  • headless coding workflow composition;
  • filesystem, Git, process, and test tool packs;
  • DSH/TUI/editor UX;
  • product-specific skill refinery and evolutionary-agent integrations.

Generic runtime changes belong upstream in prolog-rlm rather than being duplicated here.

Optional Zara runtime profile

AgentProlog can be exposed to Zara as a profile of the Prolog-RLM runtime. It is not a second runtime implementation and it does not make Zara depend on AgentProlog.

Zara -> ZARA-RUNTIME/1 -> Prolog-RLM
                         ^
                         |
                  profile: agentprolog

The Nix output agentProlog-zara-runtime starts the upstream prolog-rlm-zara sidecar with --profile agentprolog:

nix run .#zara-runtime -- --port 18765

Zara discovers the runtime as prolog-rlm and may render agentprolog in the descriptor's profile list. Provider/model calls, planning, recursive execution, budgets, cancellation and trace semantics remain owned by Prolog-RLM. Zara remains the host for chat/project context, plugins, approvals and platform integration.

This profile is optional. Normal AgentProlog usage and normal Zara usage do not require it.

Cross-repo authority: lost-rob0t/zara#1046; upstream bridge: lost-rob0t/prolog-rlm#448.

Development

nix develop
nix flake check

The repository consumes prolog-rlm through its Nix flake dependency.

Architecture authority

  • AgentProlog product epic: issue #1
  • DSH AgentFactory implementation: issue #7 / PR #8
  • upstream repository boundary: lost-rob0t/prolog-rlm#141