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 / Harness Path — Game Of 42

🎲 Harness Path — Game Of 42

9 · Game of 42 — the lattice the fleet is seated on — an entry in the origin fleet catalogued in The Harness Paths (group: The structure layer). The catalogue is the operator's work WITH the harness, not part of the system you adopt; none of its code lives in the harness repo. This is the map entry, so you can see what a filled config looks like at this weight.

(public: github.com/mitchuski/game42)

Not an optimization loop at all, and it says so. It is a visualization of the
6 axes × 7 faculty-stations = 42 pattern that SPECIALISATION.md
describes in the abstract — here made concrete and, more importantly,
checked. The lattice is ℤ/64ℤ = {0,1}⁶; each axis is a basis vertex
(protection 32, delegation 16, … value 1); the faculty cube is {head 1, heart
2, hands 4} and its seven non-empty subsets are the seven stations. The three
operators — neg(x) = (64−x) mod 64 (the Swordsman), bnot(x) = 63−x (the
Mage), and succ(x) = (x+1) mod 64 — satisfy neg(bnot(x)) = succ(x) as
stated canon: the same identity engine/conform.mjs proves here. Its build
gate asserts the structure rather than trusting it — 42 slots, 6 heptads, the
class split, the per-slot axis vertices, the anchor sums — with a watchdog
that fails if the runtime table drifts from the gate's independent copy. What
it does not have is a solver: the fold scalar is a readout, never a
control, and the dual agents are depicted (Sword ⊥ Mage) rather than
executed. It is the picture of the structure the other seven are seated in.

At a glance —
objective: none — a visualization of the structure itself · gate: the build gate asserts 42 slots, 6 heptads, the class split, per-slot axis vertices, and the anchor sums, with a runtime watchdog against an independent copy · hard constraint: the fold scalar is a readout, never a control
the Gap: none — it checks structure, not results · lenses: depicted (Sword ⊥ Mage), not executed — there is no solver, and it says so · canary: the stated canon identity neg(bnot(x)) = succ(x) itself
weight: structure layer · public · the lesson it carries: structure you cannot check is decoration; the lattice is structure because a gate can fail on it.



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