🗺️ The Harness Paths

This catalogue is not the harness. It is the origin operator's fleet —
work done with the harness, kept here as evidence and pedagogy the way
universe/ keeps one project's corpus behind a seam. The system you adopt
is the engine, the constitution, and the tools; delete this file and every
gate still passes.

The fleet is divergent on purpose, and the divergence serves one
construction: trust-graph creation, the agentprivacy way. Each entry —
circuits, grammars, consent records, registries, wikis — is a working piece
delivered toward that purpose, and the harness is what gives every one of
them the same verifiable shape: a gated result sealed as a κ-addressed node,
a relation that a signature mints as an edge (GRAPH.md). Bodies diverge;
the graph they feed is one. What these entries buy you is sight: what a filled
config looks like at full weight — and, just as usefully, what a partial
embodiment looks like — before you build your own. None of their code lives
here. Each began as a skeleton like this one and diverged only through its
config, its seat cards, and its gate.

Ten instances specialised this harness; an eleventh seat — once held open by
invitation — was signed on 2026-07-14; a twelfth carries the skeleton whole
as a standalone sibling; two later runtimes carried the hold-apart into an
agent-operated acceptance flow and into literature review, and the sixteenth
accession is the first descendant lane — no loop at all, but the
constitution inherited whole. Fifteen entries stand; numbering is by
accession and never reused, so one number sits empty (withdrawn before its
counterpart work published — the door decides what is named here, and when).
Grouping is by weight.

They are grouped by how much of the loop they run, because that is the
most useful thing to see. 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
instances that lack a Fiat-Shamir Gap or an advancing frontier are marked as
such, deliberately — reading an honest partial teaches the bar better than
reading a complete one.

instance	domain	objective	the Gap	weight
shor_mage	quantum circuits	product: qubits × Toffoli, ↓	9,024 witnesses hashed from the circuit's own op stream	full
tigzkp_mage	ZK constraint count	R1CS constraints, ↓	held-out points, Fiat-Shamir per round	full + specialised
V6 rehydration	research documents	fidelity across audiences	adversarial reviewer who never sees the canon	full, non-numeric
privacy_pools_v2_mage	ZK, real upstream target	R1CS constraints, ↓	as above, per-rewrite certificates	full, mechanically fitted
lexon_pvm	controlled-grammar semantic base (Lexon × PVM)	coverage-debt, ↓	5 held-out census terms + 3 regression entries hashed from the proposal	full, mechanically fitted
MyTerms / IEEE 7012	consent agreements	Φ product over a bilateral record	registry + unlock lattice + constellation hash	loop built, mock-only
FedWiki flow + Gatehouse	publishing	presence/absence gap-count	(no witness draw) — integrity gate + human	discovery loop
the dream cycle	universe upkeep	(no metric) — gap surfacing	(none) — the measure seat at fleet scale	measure-only
Game of 42	the structure itself	(none) — a visualization	(none) — checks structure, not results	structure layer
universe-builder	a map of a corpus	words, ↓	a sampled draw it never needed	RETIRED — read this one
hearthold_mage	household sovereignty stack	disclosure-debt, ↓ (baseline 2049 canonical bytes)	FULL-mode bundle satisfies all 23 frozen census requirements + one negative fixture per requirement	FILLED 2026-07-14 — the House of Archon, signed
hh_workshop	workshop facilitation (babblefish translation)	translation-debt, ↓ (baseline 32)	census over a 31-claim frozen register; the probe FORM drawn Fiat-Shamir from the triptych; assayer blind to canon	full, mechanically fitted — standalone (vendored engine, local-model driver)
the DTG verification registry	ZK ceremony suite acceptance	registry rows, honestly accepted	digest-manifest byte-match; the decision consumes only `pinned`	acceptance flow, human-gated — first external run accepted
the litreview runtime	prior-art novelty (Programme WP-14)	residues surviving refutation	context isolation: refuters never see the prover's argument (D3)	full, non-numeric — sweep ⊥ refute ⊥ judge
uor_kappa_mage	upstream substrate convergence (kappa-registry)	(no metric) — a P-gated research lane	(inherited, not drawn) — TRUSTS + GROUND_RULES govern every session	descendant lane — the constitution inherited whole

Each instance page carries an At a glance config card — objective, gate, hard constraint, the Gap, lenses, canary, weight, lesson — the same columns as the mapping table in Adopting The Harness: read a card, then read your own use case across the same columns.

The fifteen, grouped by loop weight

Full loops

⚛️ Harness Path — Shor Mage
🔐 Harness Path — Tigzkp Mage
📄 Harness Path — The V6 Rehydration Pipeline
🌊 Harness Path — Privacy Pools V2 Mage
✒️ Harness Path — Lexon PVM
🚪 Harness Path — Accession Thirteen Withdrawn

Adjacent embodiments

🤝 Harness Path — MyTerms IEEE 7012
🏰 Harness Path — FedWiki Flow And The Gatehouse
🌙 Harness Path — The Dream Cycle
🗂️ Harness Path — The DTG Verification Registry
📖 Harness Path — The Litreview Runtime

The structure layer

🎲 Harness Path — Game Of 42

The negative result

🪦 Harness Path — The Universe Builder Retired

Invited vacancies

🏠 Harness Path — Hearthold

Standalone siblings

🐟 Harness Path — HH Workshop

Descendant lanes

🔗 Harness Path — UOR Kappa Mage

What travels, what stays, and how the fleet syncs

Read these fifteen and you will notice the same skeleton under fifteen
unrecognisably different bodies: an objective (or an honest absence of one), a
hard constraint, a gate the proposer cannot choose, a ledger only one seat
writes, and a door only a person opens. And one body carries no skeleton at
all — only the constitution, which turns out to be the part that travels
furthest.

They also sync into one universe, and that is not decoration — it is the
fractal claim of SPECIALISATION.md §2 made real:

One inscription, in all of them. (⚔️⊥⿻⊥🧙)😊 = neg ⊕ bnot → succ is
stamped on shor_mage's chronicles, tigzkp's harness algebra, MyTerms'
boundary code, the Gatehouse door, and every Game-of-42 seal. Proving that
identity rather than asserting it is the same gate idiom everywhere.
One cast. Personas are role classes from a shared skills corpus, bound
per seat. The support seats of shor_mage and tigzkp are literally the same
City-of-Mages keepers. A new instance claims a vertex on an axis rather than
inventing a new shape — tigzkp holds the compute axis.
One anchor law. The complement pair whose vertices XOR to 63 — Aletheia
(V38) ⊕ Lethe (V25) — is the same pair in the Game of 42's lattice and in
tigzkp's conformance gate: bnot made structural, checked in two places
that never import each other.
One sharing surface. When an instance has something to send, it goes
through the Gatehouse — and sending is always the door, the First Person's
alone.

So the fleet is held apart exactly the way the seats are: each instance
publishes a frontier, none writes another's ledgers, and what travels between
them passes a gate it did not choose. The First Person is the keystone of
the fleet, exactly as the keystone is the pair of the workshop.

The lemma travels; the corpus stays home. Your harness path is a config, not a
fork — and when it earns a persona and a vertex, it joins the lattice without
drifting, because the structure is checked, not asserted.

Assets

📎 the-harness-pathsHARNESS_PATHS.md

Navigation

← Welcome Visitors · The Dual-Agent Harness · Workflows And Runtimes

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