Why
Layer four of the ladder Specs → Skills → Crons → Agents. The 27 agents of docs/agents/AGENTS_ALPHABET.md (A…Z + Ti) exist today as prose (the alphabet table, docs/agents/AGENTS.md, .claude/agents/*.md) and as experience logs under .trinity/experience/. Nothing states an agent as a spec, so t27.ai cannot generate an agent card from the compiler the way it now does for skills (#3544) and crons.
What
specs/agents/<letter>.t27 × 27 (module agent_<letter>, KIND = "agent", ID = "t27/<LETTER>"): LETTER, ORDINAL, LETTER_NAME, NAME, DOMAIN, ARCHETYPE, REGISTER, LAYER, SUMMARY_EN, SOUL = "SOUL.md", AGENTS_DOC = "AGENTS.md", ALPHABET = "docs/agents/AGENTS_ALPHABET.md", KEY_FILES, ENTRY_INVARIANT, EXIT_INVARIANT, CLARA_ROLE ("" when the table shows —), SKILLS + SKILLS_NOTE, optional TOOLS + TOOLS_NOTE, EXPERIENCE_LOG, ENABLED. English-only (LANG-EN). Transcribed from the alphabet's FULL TABLE and per-agent schema sections, nothing invented.specs/agents/README.md: schema, the four-layer ladder, the skill-binding rule (a skill is bound only when a source evidently binds it — OWNERS rows, .claude/agents/<x>.md naming a skill, alphabet Key files pointing at a skill; otherwise SKILLS = [] and a note), the experience-attribution rule the site uses, and the source inconsistencies found while transcribing (Ti register r20/TAW vs R19; F and U both φ; OWNERS "R-Reasoning" vs alphabet R = Runtime).specs/i18n/agents-ru.t27: SCOPE gains specs/agents so the RU summaries travel through the existing translation contract and bundle.specs/OWNERS.md: row agents/ → T-Queen.docs/now/ entry.
Witness
- All 27 modules typecheck ok under the vendored compiler wasm on the site (sha256
4d9c0447b5ca2887…); the site's generator (gHashTag/trinity) resolves every SKILLS id against specs/skills/ and fails on an unknown one.
- Skill bindings today: only T (
.claude/agents/trinity.md names phi-loop and tri-pipeline). All other letters carry SKILLS = [] with a SKILLS_NOTE.
- Experience snapshot on the site: 386 episodes read from
.trinity/experience/** (trinity + t27), 0 attributed to any letter — no episode carries an agent letter field. The specs do not claim otherwise.
Not claimed
No agent is "launched" by this; the spec states the letter, its documents and its invariants. No new agent, no renamed register: the specs follow the alphabet as written and record its inconsistencies rather than resolving them.
Why
Layer four of the ladder Specs → Skills → Crons → Agents. The 27 agents of
docs/agents/AGENTS_ALPHABET.md(A…Z + Ti) exist today as prose (the alphabet table,docs/agents/AGENTS.md,.claude/agents/*.md) and as experience logs under.trinity/experience/. Nothing states an agent as a spec, so t27.ai cannot generate an agent card from the compiler the way it now does for skills (#3544) and crons.What
specs/agents/<letter>.t27× 27 (moduleagent_<letter>,KIND = "agent",ID = "t27/<LETTER>"): LETTER, ORDINAL, LETTER_NAME, NAME, DOMAIN, ARCHETYPE, REGISTER, LAYER, SUMMARY_EN, SOUL = "SOUL.md", AGENTS_DOC = "AGENTS.md", ALPHABET = "docs/agents/AGENTS_ALPHABET.md", KEY_FILES, ENTRY_INVARIANT, EXIT_INVARIANT, CLARA_ROLE ("" when the table shows —), SKILLS + SKILLS_NOTE, optional TOOLS + TOOLS_NOTE, EXPERIENCE_LOG, ENABLED. English-only (LANG-EN). Transcribed from the alphabet's FULL TABLE and per-agent schema sections, nothing invented.specs/agents/README.md: schema, the four-layer ladder, the skill-binding rule (a skill is bound only when a source evidently binds it — OWNERS rows,.claude/agents/<x>.mdnaming a skill, alphabet Key files pointing at a skill; otherwiseSKILLS = []and a note), the experience-attribution rule the site uses, and the source inconsistencies found while transcribing (Ti register r20/TAW vs R19; F and U both φ; OWNERS "R-Reasoning" vs alphabet R = Runtime).specs/i18n/agents-ru.t27: SCOPE gainsspecs/agentsso the RU summaries travel through the existing translation contract and bundle.specs/OWNERS.md: rowagents/→ T-Queen.docs/now/entry.Witness
4d9c0447b5ca2887…); the site's generator (gHashTag/trinity) resolves every SKILLS id againstspecs/skills/and fails on an unknown one..claude/agents/trinity.mdnames phi-loop and tri-pipeline). All other letters carrySKILLS = []with aSKILLS_NOTE..trinity/experience/**(trinity + t27), 0 attributed to any letter — no episode carries an agent letter field. The specs do not claim otherwise.Not claimed
No agent is "launched" by this; the spec states the letter, its documents and its invariants. No new agent, no renamed register: the specs follow the alphabet as written and record its inconsistencies rather than resolving them.