Skip to content

feat(queen): TOKEN tab, and spec authors ranked by GitHub account only - #1237

Merged
gHashTag merged 3 commits into
mainfrom
feat/tri-tab-github-leaderboard
Oct 2, 2026
Merged

gHashTag merged 3 commits into
mainfrom
feat/tri-tab-github-leaderboard

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 2, 2026 •

Copy link
Copy Markdown
Owner

Why

The owner asked for a token tab with its leaderboard, and asked why the spec-authors board (app.t27.ai/game/leaderboard) did not show every .t27 author while it did show "Claude Code (agent)", which is not a GitHub account.

What was actually wrong with the spec-authors board:

  • it was a static snapshot of 4 hand-listed repositories, while .t27 files live in 13 public gHashTag repositories;
  • a row was keyed by the git name whenever the commit email was not linked to an account, so "Claude Code (agent)", "Trinity Bee" and "trios-consolidation" stood as people;
  • the agent emails GitHub does resolve point at unrelated accounts: claude@anthropic.com resolves to github.com/claude (registered 2009), and the gh CLI's noreply@users.noreply.github.com resolves to github.com/noreply.

What changes

Spec authors (scripts/spec-authors.mjs, regenerated JSON, QueenPeople)

  • Sources are discovered: every public, non-fork gHashTag repo, the minimal set of directories holding .t27 (published mirrors and vendored copies excluded), and commits deduped across repos. That gives 53 spec paths in 13 repos and 3,393 commits.
  • Commits are credited only to a GitHub account, in this order: the commit author, then whoever opened the merged PR carrying the commit, then the committer. Agent emails and the logins claude, noreply, web-flow and [bot] are never trusted.
  • Commits that no account answers for (47 of them: bot pushes without a PR) appear as one number under the list, never as a row.
before after
gHashTag 1066 · Trinity Bee 274 · Claude Code (agent) 67 · mxfill77 18 · dmitrii-f-t27 11 · trios-consolidation 4 · Claude Agent 1 · T27 Agent 1 gHashTag 3235 (624 via merged PRs) · mxfill77 74 · dmitrii-f-t27 36 (5 via PRs) · Karim13014 1 · 47 credited to nobody

TOKEN tab (key k, QueenToken, lib/triToken.ts)

  • The minter's get_tri_state is read live from TON testnet: minted, cap, epoch and quorum. It shows 27 TRI minted, cap 10,460,353,203 TRI, epoch 1, 2 of 3 signers.
  • The board is the Queen's /queen/public-earnings ledger, ranked one row per GitHub account. A lane with no valid login is summed into an "unclaimed" line.
  • That endpoint is not deployed yet (404, feat(queen): record what accepted .t27 work has earned, append-only BrowserOS#516). Until it is, the board says so instead of guessing.
  • The first line on the tab is the status: testnet only, V1, signer quorum, NOT trustless, no market and no price.

public/tri/jetton.json

  • The deployed minter's content URI is https://t27.ai/tri/jetton.json, which returned the SPA 404. Wallets would therefore assume 9 decimals.
  • This adds the file with decimals: "3", matching tri_minter.fc. A contract pins it to MTRI_PER_TRI and to the TESTNET ONLY lead.
  • Note: trinity-fpga specs/trinet/mint_on_acceptance.t27 says DECIMALS 18, which disagrees with the contract. That needs a separate fix.

Verified

  • tsc --noEmit is clean.
  • qa/agents-spec-contract, tri-screens-contract, queen-contrast-contract and queen-wars-contract pass. The key string is now 1234567890tprbwmlxk, and there is a new TOKEN module assertion.
  • Checked in a local dev server:
    • the tab renders the live chain read;
    • a stubbed ledger renders GitHub-only rows, with an invalid login summed into "credited to nobody";
    • pressing k opens the tab.

Reaching app.t27.ai needs a QUEEN_REF bump in 999 after this merges.

{
  "version": 1,
  "head_sha": "211e82f4cb0e91aedbe6d5b4162c84881ffb02b6",
  "summary": "The /game leaderboard listed agent identities such as Claude Code as people, and missed spec authors outside two repositories. Spec authors are now GitHub accounts found across every public gHashTag repository holding .t27 files, and a new TOKEN tab shows the TRI testnet minter state and who earned TRI, by GitHub login.",
  "changes": [
    "scripts/spec-authors.mjs credits a commit to a GitHub login by author, then merged-PR author, then committer, then exact name; agent and noreply identities are never people, and anything left is counted as unattributed.",
    "public/roadmap/spec-authors.json regenerated: 53 spec paths in 13 repositories, 3393 commits, four GitHub accounts and 47 unattributed commits.",
    "QueenPeople shows GitHub rows only, how many commits came through merged pull requests, and the unattributed count.",
    "New QueenToken view (key k, glyph ¤) reads get_tri_state from the TON testnet minter and the Queen /queen/public-earnings ledger, and says testnet only.",
    "Queen.css: below 920 px of height the command rail uses 4 px gaps so nineteen commands fit above COLLAPSE at 1272x806."
  ],
  "tests": [
    {
      "command": "npx tsc --noEmit (apps/website)",
      "status": "passed",
      "result": "Type check exited 0 on commit 946071c73 before the CSS-only follow-up.",
      "evidence": "Local run in the PR worktree, exit code 0."
    },
    {
      "command": "node qa/agents-spec-contract.mjs; node qa/tri-screens-contract.mjs; node qa/queen-contrast-contract.mjs",
      "status": "passed",
      "result": "All three contracts exited 0 with the TOKEN module, key k and the new stylesheet registered.",
      "evidence": "Local runs in the PR worktree, exit code 0 each."
    },
    {
      "command": "node qa/queen-viewport-contract.mjs",
      "status": "not_run",
      "result": "The CI run on 946071c73 failed only at 1272x806 wars, COLLAPSE 4 px above the last command; the gap fix is in this head and its full run is left to CI because the local machine ran out of memory.",
      "evidence": "https://github.com/gHashTag/trinity/actions/runs/36969256171"
    },
    {
      "command": "Vite dev server, manual check of the TOKEN tab",
      "status": "passed",
      "result": "Live chain read rendered 27 TRI minted, epoch 1, 2 of 3 signers; ledger 404 showed the empty-ledger notice instead of guessed balances.",
      "evidence": "Browser check against the local dev server on port 5191."
    }
  ],
  "limitations": [
    "The earnings board stays empty until gHashTag/BrowserOS#516 deploys /queen/public-earnings.",
    "TRI is a testnet token under a signer quorum; nothing here gives it a price or market.",
    "The spec in trinity-fpga mint_on_acceptance.t27 still states 18 decimals while the jetton uses 3."
  ],
  "tags": [
    "Queen",
    "TRI",
    "GitHub"
  ],
  "blog": {
    "title": "A leaderboard of people has to be keyed by accounts, not by names",
    "summary": "Ranking spec authors by commit name let agent identities in and left real authors out; keying by GitHub login fixed both.",
    "outline": [
      "Agent emails such as claude@anthropic.com resolve to unrelated GitHub accounts, so name-based credit put an agent on a board of people.",
      "Credit now walks author, merged-PR author, committer and exact name, and counts the rest as unattributed instead of guessing.",
      "The earnings ledger is not live yet and the token is testnet only, so the TOKEN tab says exactly that instead of showing a number."
    ]
  }
}

🤖 Generated with Claude Code

gHashTag and others added 2 commits October 2, 2026 12:26
The "who wrote the specs" board read a static snapshot of four hand-listed
repositories and keyed a row by git name whenever the commit email was not
linked to an account, so "Claude Code (agent)" and "Trinity Bee" stood as
people while 9 of the 13 public repositories holding .t27 files were never
counted.

- discover sources: every public, non-fork gHashTag repository, the minimal
  set of directories holding .t27 files (published mirrors and vendored
  copies excluded), commits deduped across repositories
- credit a GitHub account only: commit author, else whoever opened the merged
  pull request carrying the commit, else the committer; agent emails that
  GitHub maps to unrelated accounts (github.com/claude, github.com/noreply)
  are never trusted
- what no account answers for is one number under the list, never a row
- the page states how many commits came through merged pull requests and
  which repositories were counted

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A nineteenth view on k. Every number is read, none written here:

- the minter's get_tri_state on TON testnet (toncenter v3 runGetMethod):
  minted, cap, epoch and the signer quorum, with the minter on tonviewer
- the Queen's /queen/public-earnings ledger: specs earned per lane, ranked
  one row per GitHub account; a lane tied to no valid login is summed into
  one "credited to nobody" line, never drawn as a person
- until the Queen publishes that ledger (404 today) the board says so
  instead of guessing

The status line leads: testnet only, V1, signer quorum, NOT trustless, no
market and no price. Withdrawing stays in the app profile.

Also publish public/tri/jetton.json, the content URI the deployed minter
already points at (t27.ai/tri/jetton.json, 404 until now), so wallets read
decimals 3 instead of defaulting to 9. A contract pins those decimals to
MTRI_PER_TRI and the TESTNET ONLY lead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added the status:in-progress 🔵 Agent working label Oct 2, 2026
TOKEN made the nineteenth command. At 6 px gaps the last one sat 4 px
under the sticky COLLAPSE (viewport contract, 1272x806 wars). Below
920 px of height the rail now uses 4 px gaps, which gives back 36 px.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@gHashTag
gHashTag merged commit 73d4779 into main Oct 2, 2026
27 of 33 checks passed
@gHashTag
gHashTag deleted the feat/tri-tab-github-leaderboard branch October 2, 2026 08:03
@github-actions github-actions Bot added status:completed Done and removed status:in-progress 🔵 Agent working labels Oct 2, 2026
github-actions Bot added a commit that referenced this pull request Oct 2, 2026
feat(queen): TOKEN tab, and spec authors ranked by GitHub account only (#1237)

* fix(queen): spec authors are GitHub accounts, found in every public repo

The "who wrote the specs" board read a static snapshot of four hand-listed
repositories and keyed a row by git name whenever the commit email was not
linked to an account, so "Claude Code (agent)" and "Trinity Bee" stood as
people while 9 of the 13 public repositories holding .t27 files were never
counted.

- discover sources: every public, non-fork gHashTag repository, the minimal
  set of directories holding .t27 files (published mirrors and vendored
  copies excluded), commits deduped across repositories
- credit a GitHub account only: commit author, else whoever opened the merged
  pull request carrying the commit, else the committer; agent emails that
  GitHub maps to unrelated accounts (github.com/claude, github.com/noreply)
  are never trusted
- what no account answers for is one number under the list, never a row
- the page states how many commits came through merged pull requests and
  which repositories were counted

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(queen): TOKEN tab - TRI on TON testnet, and who earned it by GitHub

A nineteenth view on k. Every number is read, none written here:

- the minter's get_tri_state on TON testnet (toncenter v3 runGetMethod):
  minted, cap, epoch and the signer quorum, with the minter on tonviewer
- the Queen's /queen/public-earnings ledger: specs earned per lane, ranked
  one row per GitHub account; a lane tied to no valid login is summed into
  one "credited to nobody" line, never drawn as a person
- until the Queen publishes that ledger (404 today) the board says so
  instead of guessing

The status line leads: testnet only, V1, signer quorum, NOT trustless, no
market and no price. Withdrawing stays in the app profile.

Also publish public/tri/jetton.json, the content URI the deployed minter
already points at (t27.ai/tri/jetton.json, 404 until now), so wallets read
decimals 3 instead of defaulting to 9. A contract pins those decimals to
MTRI_PER_TRI and the TESTNET ONLY lead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(queen): nineteen rail commands fit above COLLAPSE at 1272x806

TOKEN made the nineteenth command. At 6 px gaps the last one sat 4 px
under the sticky COLLAPSE (viewport contract, 1272x806 wars). Below
920 px of height the rail now uses 4 px gaps, which gives back 36 px.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant