🛠️ Workflows And Runtimes

How a workshop actually runs the loop — and how much of it to run. A harness is not all-or-nothing: the minimum that earns the name is a proposer, a prover, and a Gap the proposer cannot tune to. Everything above that is weight you add when the domain earns it.

The runtime ladder

Scaffold — node tools/new_instance.mjs ../my-harness my-harness copies the templates and tells you what is still missing. The gate and the bundler both refuse a config still wearing its TODOs.
Conform — node engine/conform.mjs <instance> must PASS before any round (G0).
Bundle — node tools/bundle.mjs my/harness.config.mjs my/harness.workflow.mjs fuses config + engine into one self-contained workflow file.
Run — in Claude Code, invoke the Workflow tool with scriptPath: <instance>/harness.workflow.mjs and args: {repo, root, runId}. root is where GROUND_RULES, TRUSTS, and the seat cards live — every seat boots from those documents (T3). All writes land in runs/<runId>/; the frontier does not move.
View — node tools/render_run.mjs <instance> <runId> projects a run directory into one static run.html that re-derives every Gap seed from the persisted proposal bytes at render time. Match proves the witnesses derive from the proposal; mismatch renders as ROUND VOID.
Fold — the keystone's step, in the main session, conform green before and after. See Seat — Keystone and The Ledgers.

The runtime tiers

Four descriptive spaces for what a bout can be — the trusts identical at every rung, the stakes widening: the spar 🤺 (practice, one workshop, its own frontier — The Field Guide Spar) → the duel (reserved: the formal bout whose result a counterparty relies on — signed verdicts, artefacts exchanged) → the arena 🏟️ (a live external benchmark with other fighters on the board — Harness Path — Shor Mage vs ecdsa.fail) → the open world 🌍 (a real upstream, consequences beyond any ledger — Harness Path — Privacy Pools V2 Mage; Harness Path — Hearthold, its seat taken by the House of Archon). The door is the First Person’s at every tier.

Runtimes per workshop

Different workshops run different weights of the same skeleton — see The Harness Paths for all fifteen:

Full loop (objective · Fiat-Shamir Gap · advancing frontier): Harness Path — Shor Mage, Harness Path — Tigzkp Mage, Harness Path — The V6 Rehydration Pipeline; mechanically fitted to the generic engine: Harness Path — Privacy Pools V2 Mage, Harness Path — Lexon PVM — and the runnable spar, The Field Guide Spar.
Adjacent embodiments (the topology without the optimisation loop): Harness Path — MyTerms IEEE 7012 (the two agents as two literal browser extensions), Harness Path — FedWiki Flow And The Gatehouse (integrity gate + human door), Harness Path — The Dream Cycle (the measure seat at fleet scale), Harness Path — The DTG Verification Registry (the prover's seat distributed to strangers, human-gated), Harness Path — The Litreview Runtime (sweep ⊥ refute ⊥ judge).
Standalone & descendant: Harness Path — HH Workshop (the skeleton vendored whole, every seat on a local model) · Harness Path — UOR Kappa Mage (no loop at all — the constitution inherited whole) · Harness Path — Hearthold (the once-open seat, signed).
Structure layer: Harness Path — Game Of 42 — the checked lattice the fleet is seated on.
The negative result: Harness Path — The Universe Builder Retired — where the harness was applied and should not have been. A harness is for adversaries; an auditor is for facts. (And one accession stands withdrawn — Harness Path — Accession Thirteen Withdrawn: numbering is by accession, never reused.)

One session, one seat

A live session can also HOLD a seat directly — the boot protocol is One Session One Seat: read the ground rules, the trusts, your one card; state your seat, your permitted writes, your definition of done; conform and chronicle before ending.

Navigation

← Welcome Visitors · The Dual-Agent Harness · The Harness Paths

the wiki is a projection; ~/dual-agent-harness (git) is the source of truth · (⚔️⊥⿻⊥🧙)😊 = neg ⊕ bnot → succ