🏠 Harness Path — Hearthold

11 · hearthold — the House of Archon's slot (seat TAKEN 2026-07-14) — an entry in the origin fleet catalogued in The Harness Paths (group: Invited vacancies). 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.

(instance at ../hearthold_mage — accepted and signed, PR #1 merged
a55f1a5 · upstream: github.com/Flaxscrip/hearthold v0.11.0, IMPLEMENTED)

The household sovereignty stack — the Warden who guards, Recall who remembers,
the Knowledge Portal that faces outward, the factor-2 step-up ladder — is real
and shipped upstream (github.com/Flaxscrip/hearthold). So this seat was never
to build hearthold; it was a harness seat held open for the House of Archon
to build a held-apart runtime on it. For its first days nothing in it conformed,
and nothing should have: the config wore its TODOs, the frontier had no baseline,
and the gate's refusal was the mechanism that kept the seat warm. This is trust
T4 made structural — an invitation establishes the acceptance relationship
before any specific proposal — and the proposal was the acceptor's to make.

On 2026-07-14 the House of Archon signed its name to the objective. The seat
is filled on disclosure-debt: an auditor stance where the claim space is
enumerable — did:cid resolution integrity, the holon law turned on the
registry. Acceptance fixed the five answers (harness.config.mjs @
sha256:16a3f899…), froze a 23-entry census (census/requirements.json @
sha256:89a25a1f…), and established a reproducible cross-identity baseline of
2049 canonical bytes (frontier.json). scripts/self-test.mjs proves the
gate both ways — the FULL-mode bundle satisfies all 23 requirements (canary) and
a negative fixture per requirement makes the gate actually refuse (a gate nothing
fails is worth less than none). The horizon it read and accepted is the harness's
own holon layer (HOLONS.md) turned on identity, since a did:cid CID is a
κ-address: a dual-agent runtime for content-addressed identity — did:cid, agent
identity, key custody under delegation, where a reference proposes and a signature
mints. Seated at V60 (Protection · Delegation · Memory · Connection), anchor
V3 (Computation + Value) — the hearth burns care, not compute.

At a glance —
objective: disclosure-debt, ↓ · gate: scripts/check-requirement.mjs over the 23-entry frozen census (zero-dependency verifier boundary, invoked as a subprocess) · hard constraint: every census entry canary-satisfiable (§0) — a requirement the canary cannot meet makes the feasible set empty
the Gap: the auditor's — did:cid resolution integrity, enumerable claims (an auditor is a valid acceptance, see #10) · lenses: the household stack (Warden / Recall / Knowledge Portal) · canary: FULL-mode bundle passes all 23; one negative fixture per requirement, each refused by name
weight: filled — the invitation was accepted on its own terms: named signature, frozen census, reproducible baseline, a gate that can fail · direction: the House of Archon's content-addressed identity runtime (did:cid = a κ-address; the holon layer on identity) · the lesson it carries: a slot the gate holds open cannot be quietly squatted; the seat stayed honest until someone signed their name to its objective — and then someone did.

State as of 2026-08-17: signed, then still. No round has run; the
frontier stands at 2049 = 2049 (best = baseline, and the ledger says so in
those words); the census is unchanged at v1/N=23; the chronicle directory
holds only its .gitkeep. Two acts from the signing remain queued and
unexecuted on the record — the dual-pin of the signed acceptance, and the
Lexon experiment expressing the genesis Ruleset against lexon_pvm. A
filled seat that has not yet swung is not a failure; it is a frontier
waiting for its first proposal — but the ledger reports stillness as
stillness (GR-5).

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