Repository navigation
Epic: GOLDEN CHAIN in t27 -- anchors, contribution ledger, usage from receipts, many signers, a live atlas #8609
Copy link
Copy link
Open
Description
Brings the GOLDEN CHAIN design of gHashTag/golden-chain-international (Green Paper and White Paper v0.9, see gHashTag/golden-chain-international#140) into t27, the language and toolchain the network runs on. Every rule is written in .t27 and generated. Hand-written foreign code only shrinks (#8236).
What exists (2026-10-10)
- Language, compiler, numeric catalogue.
- t27 has 109 formats in 13 clusters.
- t27b checks 1258 of 1290 specs that the reference passes, and 33.9% of t27b is generated from .t27.
- Arithmetic cores are verified on an Artix-7 board through the open flow.
- Signed receipts. Corpus and DDC receipts exist (t27b lab: signed corpus receipts and a base-vs-head equivalence check (Merkle roots over verdicts and asm outputs) #7576, verified: a signed DDC receipt of t27core and T732's verdict over its routes (Closes #7699) #7706), with a reproducible t27b build (theory(sieve): C9 measured, t27b builds bit-identical, t27c carries git abbrev and CARGO_HOME (Closes #8148) #8181). But there is one signer: the t27b lab, key a05db80f53c317f6.
- TriToken on Base Sepolia (testnet only). Ownership is renounced and there is no allocation. Its key registry still accepts any key.
- Universe Atlas on t27.ai. It is refreshed once a day through a bot PR (last refresh 2026-10-08), and its publish step is manual.
- Queen event bus (events.t27, slice 3) and the t27-bees GitHub App, which receives webhooks on Railway.
What is missing
- The anchor block (M0). t27's AGENTS.md has none yet, and the hub manifest format has not landed.
- Contribution accounting. No record yet of who wrote which spec, and how much verified compute used it.
- More than one signer. Without it, the t27b lab is a de facto chief validator, against S1.
- An external anchor, so the manifest is not circular (RT-4).
- A live atlas.
- Legal gates before any value flow. These are red lines, not tasks for an agent.
Plan
- golden_chain: the AGENTS.md anchor block as a .t27 spec, checked inside the existing t27c suite #8603 anchor block as a .t27 spec, checked in the existing suite (waits for the hub's manifest format)
- golden_chain: a contribution ledger from git history -- who wrote which .t27 spec, recomputable by anyone #8604 contribution ledger from git history, recomputable by anyone
- golden_chain: usage from receipts -- which specs verified compute actually ran #8605 usage from receipts (input_root leaves -> per-spec counts)
- receipts: more than one signer -- the t27b lab must not be the network's only validator #8606 k-of-n signers + transparency-log anchor; fix the key registry
- Universe Atlas: live fills from webhooks and the Queen event bus, the daily scan stays the verified baseline trinity#1587 live atlas: webhooks -> event bus -> SSE, daily scan as baseline
- golden_chain: payouts stay accounting until counsel -- study Drips, tea, Protocol Guild, Open Collective, RetroPGF #8607 payout research: Drips, tea, Protocol Guild, Open Collective, RetroPGF; securities risk stated plainly
Rules that do not bend
- No chief validators: authority is a protocol rule plus a merged PR, never a person.
- Accounting first, money last. No value moves until the white paper's gates are open: explorer-verified contracts, a fixed key registry, and written legal opinions.
Boundary
specs/queen/events.t27
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity
tri-claw commentedon Oct 10, 2026
The Queen cannot take this issue yet. A bee starts only on an issue whose body has every section below, and this one lacks:
- specs/x.t27); without it the Queen reserves nothing and no bee can take the issueFR-001: ... MUST ...exit 0, or a backticked commandShe tried to write them 2 times and could not (last: not a task: This is an epic tracking issue with a plan of sub-issues (#8603–#8607, gHashTag/trinity#1587), not an actionable task for a coding agent in this repository.). Add them and the next round takes it. The rule is
specs/policy/issue_shape.t27.