yogthos/samizdat

A self modifying agentic harness for Clojure

29

stars

9

commits

Clojure

primary language

Sep 11, 2026

updated

README

samizdat logo

A self-hosting agentic harness for Clojure development, written in Jolt (Clojure on Chez Scheme). The defining idea: the harness is a live image, the agent's output space is the harness's code space, and the agentic loop itself is data — a workflow manifest the agent can inspect and, behind a validate/soak/rollback gate, rewrite while it runs.

Three rings:

  • kernel — the durable journal, event bus, store, secrets, and executor lifecycle. Agent-immutable.
  • executor — the mycelium workflow layer (vendored, running on a jolt port of maestro). The loop is an EDN manifest; cells are the plugin unit and declare whether they are pure or effectful.
  • capabilities — nREPL, clojure-lsp, and shell surface as plugins; every plugin is a cell in the workflow graph.

Multiple agents work each non-trivial task: work is grounded in a kanban tasks table, decomposition hands subagents a contract plus tests as the spec, and collaborators share a feature workspace (artifacts, failures, messages) while keeping private working context.

Descended from veriframe, a claim-first verification harness for mathematics; the proof engines (Lean, Z3, SWI-Prolog, Octave) left, the durable-journal core, resume-by-replay, gate/arbiter loop, and beam scheduler stayed.

Running

jolt serve      # HTTP + nREPL, parks
jolt test       # full suite
jolt smoke      # platform probes (sqlite, https, server)

State lives in samizdat.sqlite3 (moving to dolt via doltera); a run survives restart and resumes from its journal.

Contributors

yogthos

9 commits

yogthos/samizdat

A self modifying agentic harness for Clojure

29

stars

9

commits

Clojure

primary language

Sep 11, 2026

updated

README

samizdat logo

A self-hosting agentic harness for Clojure development, written in Jolt (Clojure on Chez Scheme). The defining idea: the harness is a live image, the agent's output space is the harness's code space, and the agentic loop itself is data — a workflow manifest the agent can inspect and, behind a validate/soak/rollback gate, rewrite while it runs.

Three rings:

  • kernel — the durable journal, event bus, store, secrets, and executor lifecycle. Agent-immutable.
  • executor — the mycelium workflow layer (vendored, running on a jolt port of maestro). The loop is an EDN manifest; cells are the plugin unit and declare whether they are pure or effectful.
  • capabilities — nREPL, clojure-lsp, and shell surface as plugins; every plugin is a cell in the workflow graph.

Multiple agents work each non-trivial task: work is grounded in a kanban tasks table, decomposition hands subagents a contract plus tests as the spec, and collaborators share a feature workspace (artifacts, failures, messages) while keeping private working context.

Descended from veriframe, a claim-first verification harness for mathematics; the proof engines (Lean, Z3, SWI-Prolog, Octave) left, the durable-journal core, resume-by-replay, gate/arbiter loop, and beam scheduler stayed.

Running

jolt serve      # HTTP + nREPL, parks
jolt test       # full suite
jolt smoke      # platform probes (sqlite, https, server)

State lives in samizdat.sqlite3 (moving to dolt via doltera); a run survives restart and resumes from its journal.

Contributors

yogthos

9 commits

Languages

Clojure

100.0%