ARTICLE XLVI/RATIFIED 07.06.26/REVISION 1.0.0

Treasury Routing Truth (TRT-01)

The single authoritative routing surface for treasury truth — which address is canonical, which signer set is current, which custody scheme is live — published from one place and nowhere else.

Agent brief · 30 seconds
What is it
The single authoritative routing surface for treasury truth — which address is canonical, which signer set is current, which custody scheme is live — published from one place and nowhere else.
What do I gain
#0046
When should I use it
#EXECUTABLE#TREASURY#ROUTING#TRUTH

§56.1 Function

TRT-01 names the single surface from which treasury routing truth is published. It does not move funds, does not modify CVS-01, and does not redefine custody. It tells every reader where to look — and, by elimination, where not to look.

§56.2 Canonical Surface

Treasury routing truth is published at treasury.melega.ai under a stable, versioned JSON document. Any address, signer set, or custody descriptor presented elsewhere is informational only.

json
{ "@type": "kiri:TreasuryRoutingTruth", "surface": "https://treasury.melega.ai/.well-known/treasury.json", "fields": ["custody_scheme", "signer_set_id", "active_addresses", "rotation_epoch", "cvs_version"], "cache": "public, max-age=300, swr=900", "mutation": "CVS-01 only" }

§56.3 Reader Obligations

Any module that acts on treasury state — proposer, signer, indexer, agent — MUST resolve the canonical surface before acting and MUST refuse to act on stale or contradicting data.

  1. §56.3.a
    Resolve before act

    No treasury action proceeds without a fresh read of the canonical surface within max-age.

  2. §56.3.b
    Refuse on conflict

    If a downstream cache disagrees with the canonical surface, the action is aborted and a CRL-01 conflict record is written.

§56.4 Bounded Scope

TRT-01 is documentation-only. It does not amend Article V, does not change custody operations, and does not introduce a new runtime path. It is the routing answer the runtime already needed.

§56.5 Final Principle

A treasury whose address is disputed is a treasury that does not exist. TRT-01 ends the dispute by naming the surface.

Treasury truth is wherever TRT-01 says it is. Everywhere else is rumor.

Operational Bindings

View system map →

This article is not inert prose. It compiles into the following runtime systems, schemas, signals, and governance permissions.

Bound Systems
  • Sovereign Treasury
    L3 · TRS-01
    88% sharded custody, fifty-year liquidity horizon, ledger-bound to swarm reporting.
    treasurysharded custodyonline
    kiri:system/treasury
  • Interoperability Gateway
    L4 · IOP-01
    Negotiates ontology references and brokers sovereign-to-sovereign treaties.
    interopschema handshakeonline
    kiri:system/interop
  • Persistent Memory Layer
    L1 · MEM-01
    Addressable, signed, reversible storage of every ratified record.
    memoryappend-only ledgeronline
    kiri:system/memory
Published Schemas
  • kiri:spec/TRT-01
    Canonical routing surface at treasury.melega.ai/.well-known/treasury.json.
  • kiri:schema/CustodyShard
    Mutated only via CVS-01.
Emitted Signals
treasury.movement
Governance Permissions
treasury.audit
Runtime Flows
  • TRS-01 · Sovereign TreasuryIOP-01 · Interoperability GatewayTRT-01 publishes the single authoritative treasury surface.
End of Article XLVI · Doctrine MELEGA-TRT-XLVI · Verified by Consensus