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 Workshop Console

๐Ÿ–ฅ๏ธ The Workshop Console

node tools/console.mjs โ†’ http://127.0.0.1:4242 โ€” a localhost window onto any harness instance. A window, not a hand: the server is GET-only by construction (there is no route that writes, folds, mints, or publishes), and it holds no state โ€” every poll re-reads the run directories and re-derives every Gap seed with node:crypto, rendering MATCH in cyan and MISMATCH as a coral ROUND VOID (Law L5: never trusted, only re-derived).

The three instruments

  • The Loop โ€” the six phase stations as a ring with the keystone at center and the door drawn as a literal gap in the ring. Stations light purely from file appearance: violet sparks per proposal, chords to the Gap (solid cyan on MATCH, broken coral on MISMATCH), verdict colors per assay, the chronicle station on its draft. The keystone glows only when computed โ€” frontier best โˆฉ the round's levers.
  • The Frontier โ€” the moving ceiling: baseline hairline, the best-line stepping down through closed targets, the open target as a violet dashed ceiling, and MIRAGE ticks sitting in amber below it โ€” the multiplicative gate made visible (T5: a zero collapses the product).
  • The Lattice โ€” only when the universe/ seam is present: โ„ค/64โ„ค as seven popcount rings, axis glyphs read from universe.json (never hardcoded โ€” the E-7 lesson), seated XOR-63 pairs as literal diameters, vacancies as dashed vertices, and the axiom coin stepping succ while bnotโˆ˜neg traces the same step.

Instructional monitoring

Click any station and its seat card opens beside the geometry; the six trusts render as chips that claim only what was mechanically checked (T2/T5/T6 from the config and the conformance gate; T3/T4 as honest grey "topological / documented"). A "run every gate" button prints tools/check.mjs verbatim โ€” the console never summarizes a gate it didn't run. Point it at any instance anywhere: node tools/console.mjs --root <dir> discovers by the same rule as the gate (a directory carrying harness.config.mjs).

Artefacts and the door

node tools/mint_artefact.mjs <instance> <runId> seals a run into artefacts/<id>/ โ€” a ฮบ-labelled record (sha256 over canonical JSON, the label excluded from its own preimage โ€” the same content-addressing as the City Key), byte copies of all evidence with a hash manifest, and a DOOR.md listing the outward actions the software did NOT take. It refuses a tampered seed (GR-4), a red conformance gate (G0), or a verdict-less run (GR-5). When the universe layer is present the artefact carries drafts that track into the universe โ€” a spellweb node draft, a FedWiki page draft, a Gatehouse-eligible flag, a seated-vertex hint โ€” and the edge rule travels with them: a validated round PROPOSES an edge; only a signature MINTS it. The console's door panel re-derives every ฮบ on display and shows the copy-paste commands. Nothing on the page executes any of them.

Navigation

โ† Welcome Visitors ยท Workflows And Runtimes ยท The Setup Pathway

the wiki is a projection; ~/dual-agent-harness (git) is the source of truth ยท (โš”๏ธโŠฅโฟปโŠฅ๐Ÿง™)๐Ÿ˜Š = neg โŠ• bnot โ†’ succ