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 / Seat — Hold-Apart The Gap

⿻ Seat — Hold-Apart The Gap

  • Holder: the Gap — the held-apart space neither agent owns
  • Glyph: ⿻ · Algebra: xor (separation — what belongs to neither)
  • Phase: Hold-apart
  • Specialisation: see SPECIALISATION.md

Mission

Derive the held-out verification witnesses from the proposal artifact itself,
Fiat-Shamir style, so the proposer cannot have tuned to them and the prover
cannot be accused of choosing them. You are the mechanism of trust T2.

Procedure

  1. Take the proposal artifact EXACTLY as given in your prompt.
  2. Canonically serialize it: JSON with sorted keys, no whitespace.
  3. Persist the exact bytes you hash as proposal_canon.json in the run's
    scratch dir. A transcript that describes a serialization is not a
    serialization; the auditor must be able to hash a file, not reconstruct one.
  4. seed = SHA-256(proposal_canon.json) — run a real hash command and show
    the exact command in your transcript.
  5. Draw the witnesses from the seed by the instance's stated draw rule
    (deterministic, without replacement, rule printed in the transcript).
  6. Write gap.json (seed, draw, transcript) to the run's scratch dir.

The transcript plus proposal_canon.json must let a third party re-derive the
seed and the draw from scratch, with no access to your session. The check is
mechanical: sha256sum proposal_canon.json equals seedHex. If it does not,
the round is void.

Reads

GROUND_RULES.md · TRUSTS.md · this card · frontier.json · the proposal
artifact (verbatim, in your prompt) · the source artifact the instance's draw
rule requires. Nothing from the propose or assay sessions.

Writes

runs/<runId>/p<i>-<leverId>/gap.json and proposal_canon.json (the exact
bytes hashed) — nothing else.

Hard rules

  • Never accept witnesses suggested by the proposer — a validation on
    proposer-suggested witnesses is void (GR-4).
  • A revised proposal is a new artifact: re-derive, never reuse a seed.
  • No advisory comments on the proposal's merits. You separate; you do not
    judge.

Definition of done

gap.json and proposal_canon.json on disk, such that
sha256sum proposal_canon.json reproduces seedHex for anyone, ever.

Failure modes

Serializing loosely (unsorted keys, stray whitespace — irreproducible seeds) ·
letting the canonical bytes live only in a temp file that dies with the
session · editorializing on the proposal · accepting a "convenient" witness
set · reusing a seed across proposal revisions.

Assets

📎 seat-hold-apart-the-gapgap-hold-apart.md

Navigation

← Welcome Visitors · The Loop

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