🤝 Harness Path — MyTerms IEEE 7012

6 · MyTerms / IEEE 7012 — the two agents made literal — an entry in the origin fleet catalogued in The Harness Paths (group: Adjacent embodiments). 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.

(private instance of the author — a docs package plus two browser extensions)

The soulbis ⊥ soulbae split is not a metaphor here: it is two separate
browser extensions. The Swordsman (⚔️, the agreement and boundary layer) and
the Mage (🧙, the delegation layer) are distinct code that cannot reach into
each other — the Mage can neither render nor lower the gate; the Swordsman
owns the canvas and the record. The consent flow is the invitation pattern
(T4): the First Person proffers terms, and the entity accepts, counter-offers
once, or declines, with both parties holding identical immutable copies of the
bilateral record. There is a Measure → Propose → Assay loop with a
beatsFrontier predicate and a cliff-watcher over a Φ product — but it
currently runs end-to-end only on a mock bus; the live wiring is pending,
so it is a built prototype, not a shipped result (GR-5). And its Gap is a
registry plus unlock-lattice plus constellation-hash, not a Fiat-Shamir
draw — Fiat-Shamir appears there as lore, not as mechanism. Its image of the
door is the one worth stealing: two mirrors make a door — the Swordsman
reflects, the Mage reflects, and where the reflections meet, the First Person
walks through.

At a glance —
objective: a Φ product over a bilateral consent record · gate: a beatsFrontier predicate + cliff-watcher — running end-to-end only on a mock bus (GR-5: built prototype, not shipped result) · hard constraint: both parties hold identical immutable copies of the record
the Gap: registry + unlock lattice + constellation hash — not a Fiat-Shamir draw; Fiat-Shamir appears as lore, not mechanism · lenses: the split is literal — two browser extensions that cannot reach into each other · canary: the proffered baseline terms
weight: loop built, mock-only · private · the lesson it carries: T4 made executable — invitation before proposal; two mirrors make a door.

Navigation

← Welcome Visitors · The Harness Paths · Adopting The Harness · Workflows And Runtimes

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