guide to agentprivacy
Browse collections
โœจVisualise
Connect with Star
Your VTA, your chosen perspective

The planned connection uses your VTA and the Trust Spanning Protocol to carry a scoped exchange for you or your agent. You choose what is presented; the receiving service checks the request before a view is shared.

This guide has no VTA connection adapter yet. Opening Star does not connect an identity or send a key.

Open Star โ†— ยท Inspect your City Key โ†—
guide / Harness / The Setup Pathway

๐Ÿšช The Setup Pathway โ€” clone to your own harness

What this is. A verification harness for AI-agent work: one agent proposes, a second independently proves, and the tests that decide are derived by hashing the proposal together with a run secret the proposer never sees โ€” so it could not have chosen or ground them. Config-driven, zero dependencies, every axiom checked at runtime. Built with trust-graph construction in mind: a gated result seals as a ฮบ-addressed node, a signature mints an edge (The Trust Graph Dialect). Full statement: The Dual-Agent Harness.

Where it stands. Debugged by being run โ€” eleven defects found on execution, each fixed and pinned. The spar has a real advancing frontier (see The Field Guide Spar, numbers cited live). Fifteen embodiments catalogued in The Harness Paths โ€” the origin fleet, the operator's work WITH the harness, kept apart from the system you adopt. The skeleton is domain-neutral and stays that way.

Requirements. Node โ‰ฅ 18, nothing else. Multi-agent rounds need a seat driver โ€” Claude Code's Workflow tool is the reference runtime; the engine also accepts any rt = { agent, parallel, pipeline, phase, log } you supply.

The eight steps

  1. Prove the axioms โ€” node tools/check.mjs: the โ„ค/64โ„ค algebra, the engine's failure-semantics tests, conformance of every instance, and the negative test that the blank template fails for the right reasons. See The Engine And Its Gates.
  2. Read the constitution โ€” The Six Trusts, then The Ten Ground Rules. These are the parts you should not change.
  3. Run the spar โ€” a real round against the field guide: Workflow tool, scriptPath: examples/field-guide/harness.workflow.mjs, args: {repo, root, runId}. All writes land in runs/<runId>/; the frontier does not move on its own. See The Field Guide Spar.
  4. Audit and view โ€” node tools/render_run.mjs examples/field-guide <runId> re-derives every Gap seed from the saved proposal bytes; or sha256sum proposal_canon.json = seedHex by hand.
  5. Fold as keystone โ€” conform green โ†’ fold the validated-and-structural lever โ†’ frontier first, prose second โ†’ chronicle โ†’ conform green again. See Seat โ€” Keystone and The Ledgers. Publishing anything is the First Person's alone (T6); where the claim space is enumerable, run the census first (what you can count, count).
  6. Seal what survived โ€” mint_artefact.mjs writes a ฮบ-labelled artefact bundle (content-addressed, never trusted only re-derived) with an evidence hash-manifest and a DOOR.md of the actions software did NOT take; it refuses tampered seeds, red gates, and verdict-less runs. Bundles surface in The Workshop Console.
  7. Scaffold your own โ€” node tools/new_instance.mjs ../my-harness my-harness, fill every TODO (gate and bundler both refuse a config still wearing them), bundle, run like the spar. The Seat Contract is the interface and Adopting The Harness is the map โ€” the harness-vs-auditor decision, the five answers that become your config, and six worked domain mappings. Define the Gap first โ€” no hash-derived witnesses, no harness; you may want an auditor instead (Harness Path โ€” The Universe Builder Retired).
  8. Specialise when it earns it โ€” Specialisation โ€” The Game Of 42 and Mage And Swordsman; The Harness Paths shows fifteen real configs at every weight.

Follow the story

The pathway has been walked end to end under its own gates: the spar's frontier records three audited folds โ€” 730 โ†’ 573 โ†’ 526 โ†’ 472 words, every step at gate 8/8 on hash-drawn witnesses, the last two closed by exhaustive census โ€” numbers cited live on The Field Guide Spar. The loop found eleven of its own defects by running; one round was watched live in The Workshop Console; ฮบ-labelled artefacts sit sealed at the door; the seat once held open by invitation was signed by the House of Archon on 2026-07-14 (Harness Path โ€” Hearthold). The chronicles in the repo are the record, read them in date order โ€” the wiki is the map.

The whole pathway in one sentence

Prove the axioms, read the trusts, run a round you can audit by hash, fold only what two separated agents agreed on, and only then make it yours โ€” your harness path is a config, not a fork.

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