The Second Implementation

The Trust Task registry promotes a family from draft to candidate when TWO interoperable implementations exist. Kyra Gate is the first. The second lives beside it and shares nothing with it: a separate implementation in a different language, with its own canonical JSON, its own keys, its own schema validator — and its own admission policy, a risk rubric rather than the sovereignty instrument. The family standardises how a gate speaks, never how it decides.

Interop is proven in both directions, automatically, on every verification run: the second implementation independently verifies the first's live transcript — every signature, every thread, both gates, the travelling event log re-checked from genesis — and the first's validator accepts everything the second mints.

One implementation, three expressions — persona skins that change names and voices, never wire semantics: a risk-assessment authority admitting a portfolio-screening agent; a Warden admitting an Emissary with a Sovereign relying on the result; and a Gatekeeper admitting a traveller whose answer unlocks only if it understands the question. The same six documents carry all three worlds. See The Evidence, or return to Kyra Gate.

upstream: github.com/mitchuski/kyra_gatehouse · the repo is the source of truth; this page is a projection that records its origin · author: Mitchell Travers · (⚔️⊥⿻⊥🧙)😊

← Welcome Visitors