Conversation
86 of 92 tool cards and 23 of 26 skill cards carried a note saying, truthfully, that docs/agents/AGENTS_ALPHABET.md, specs/OWNERS.md and .claude/agents/*.md did not name them. That was an honest record of an absence, and it left the ladder Specs -> Skills -> Crons -> Agents -> Tools with a rung nothing stood on: the Queen held 3 tools of 92 and could not reach tri/verdict, tri/cell or tri/experience -- the VERIFY, EVOLVE and LEARN steps of her own nine-phase loop, bound to V, W and E and not to her. AGENTS_ALPHABET.md now carries the source those notes were looking for, as two independent rules. One: the Queen orchestrates the loop, so every tool and every skill is hers. Two: each card also has a domain lead -- the bee whose subject it is, read off what the card states it does (ABOUT, ACTIONS, SOURCE, SUMMARY_EN) and never off its name. Six tool cards get no domain lead and say why: four are external MCP servers whose cards record only that they are registered in .mcp.json, and two state a subject too thin to place -- tri/doctor starts and stops a state file, and tri/dashboard says "Sacred dashboard". They are the Queen's alone until a card says what they are for. Nothing here invents a capability: every added line names who is responsible, not what a tool can do. The bindings are written on both sides, as the generator requires: a tool's AGENTS names the letter and that agent's TOOLS names the tool. Checked with gHashTag/trinity's scripts/agents-from-specs.mjs against a vendored copy -- 0 problems, typecheck 27/27 agents and 92/92 tools, tools with an agent 92 (was 6), agents with tools 20 (was 5), agents with skills 20 (was 3). Каждый инструмент и скил теперь принадлежит Королеве, и у каждого есть домен-лид — пчела, чья это тема, определённая по тому, что карточка о себе пишет, а не по её названию. Шесть карточек остаются без домен-лида, и там сказано почему: внешние MCP-серверы не сообщают, для чего их здесь используют. Привязка записана с двух сторон, как того требует генератор. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
PR DashboardGenerated at: 2026-09-15 17:45:06 UTC
Summary
Seal Status
|
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
This was referenced Sep 15, 2026
This was referenced Sep 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
86 of 92 tool cards and 23 of 26 skill cards carried a note saying, truthfully, that
docs/agents/AGENTS_ALPHABET.md,specs/OWNERS.mdand.claude/agents/*.mddid not name them. Honest, and it left the ladder Specs → Skills → Crons → Agents → Tools with a rung nothing stood on: the Queen held 3 tools of 92, and could not reachtri/verdict,tri/cellortri/experience— the VERIFY, EVOLVE and LEARN steps of her own nine-phase loop, bound to V, W and E and not to her.AGENTS_ALPHABET.mdnow carries the source those notes were looking for, as two independent rules:ABOUT,ACTIONS,SOURCE,SUMMARY_EN) and never off its name.Who got what
Skills went the same way — 26 cards to 19 bees, the Queen over all of them.
Six tool cards get no domain lead, and say why. Four are external MCP servers whose cards record only that they are registered in
.mcp.json(mcp/gitbutler,mcp/neon,mcp/notebooklm,mcp/railway-mcp-server); two state a subject too thin to place —tri/doctorstarts and stops a state file,tri/dashboardsays "Sacred dashboard". They stay the Queen's alone until a card says what they are for. Nothing here invents a capability: every added line names who is responsible, not what a tool can do.How it was checked
Each assignment was proposed from the card's own text and then re-read by a second pass whose job was to refute it; 17 of 91 tool assignments and 6 of 26 skill assignments were corrected that way — typically a letter guessed from a name ("R was inferred from the word VM, but R's KEY_FILES are the compiler runtime, which the card never names").
The bindings are written on both sides, as the generator requires: a tool's
AGENTSnames the letter and that agent'sTOOLSnames the tool. Verified with gHashTag/trinity'sscripts/agents-from-specs.mjsagainst a vendored copy:One companion change is needed in gHashTag/trinity and is filed separately: its generator emitted the "unbound" group only while some command had no agent, so the day every command gained one the bucket vanished and its own contract read
undefinedwhere it asked for a list.