🏰 Harness Path — FedWiki Flow And The Gatehouse

7 · FedWiki core flow + the Gatehouse — a publishing loop, human-gated — 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.

(public site; the loop and Gatehouse are the author's tooling)

The loop is RESEARCH → GATE (human) → BUILD → SNAPSHOT → verify → push,
and its shape instructs precisely because two pieces are deliberately not the
optimization kind:

• The verifier is an integrity gate, not an adversary. It fails the deploy
  on empty pages, broken links, a missing machine-forkable JSON sibling, or a
  dev-host leak — checking the whole emitted artifact deterministically
  rather than sampling held-out inputs. No frontier metric, no witness draw.
  This is what a harness looks like when the prover is pass/fail integrity and
  the real gate is a person.
• The cookie broker is the separation mechanism in miniature. An agent
  receives a scoped capability — a list of host globs it may write — while the
  owner credential that could write the whole farm never enters its context.
  Delegation without disclosure. The broker itself notes it is a hand-rolled
  stand-in for a MyTerms-signed scope, and keeps the seam clean so one can be
  swapped for the other.
• The Gatehouse hides documents encrypted inside the public static site
  behind a two-token ceremony (a sigil and a proverb, stretched to a key,
  decrypted client-side — nothing is sent anywhere). Two gate classes:
  letter-keyed, where the tokens travel only inside a sent letter, so
  opening it proves receipt; and canon-keyed, where both tokens are
  already public, so opening it proves only that you read the canon — a rite
  with zero secrecy by design. Its door voice is the harness cast made visible
  to a visitor: the Swordsman guards, the Mage casts. Its seal: a trust that
  certifies itself is the one you cannot trust. Neither token opens anything
  alone.

At a glance —
objective: presence/absence gap-count — what canon is not yet federated · gate: a deterministic integrity gate (empty pages, broken links, missing JSON siblings, dev-host leaks) — an auditor, not an adversary; the real gate is a person · hard constraint: nothing sealed crosses; git stays the source of truth
the Gap: none, deliberately — the human gate is the whole of the verification · separation mechanism: the cookie broker — an agent receives host-scoped write capability while the owner credential never enters its context; delegation without disclosure · canary: a known-good page through the same build
weight: discovery loop · public site · the lesson it carries: what the architecture looks like when the prover is pass/fail integrity — and why that is correct for this job.

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