Repository navigation
docs(t27f): T27F is the visual spec of .t27, not the topic-to-value engine (Closes #10016) - #10017
Merged
Merged
Conversation
…ngine (Closes #10016) T27F is defined by gHashTag/trinity#1648 and RFC #1649: every .t27 spec gets one synchronized model and many views, each node labelled exact, derived, suggested or unknown and linked to its source span. The topic-to-value map of trinity#1677 and the reels are applications on top of it. - .claude/skills/t27f/SKILL.md: renamed to "T27F Visual Spec"; one section "What T27F is" holds the definition, a table separates the missing core (spec -> graph IR, renderer) from what exists, a manual "show a spec" procedure, and the topic-map procedure kept as an application section. - specs/skills/t27-t27f.t27: name, summary, specs and tags follow. - specs/OWNERS.md, CLAUDE.md, topic_engine.t27 header: point to that section instead of calling T27F the topic engine. Railway lab: t27-t27f.t27 1/1 and topic_engine.t27 14/14 under t27c test-report and t27b --check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
gHashTag
enabled auto-merge (squash)
October 17, 2026 16:39
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.
Closes #10016
What changes
T27F is defined by gHashTag/trinity#1648 and RFC gHashTag/trinity#1649: every
.t27spec gets one synchronized model and many views, each node labelled exact / derived / suggested / unknown and linked to its source span. The repo called it the topic-to-value engine of gHashTag/trinity#1677, which is an application on top..claude/skills/t27f/SKILL.md-> "T27F Visual Spec". One section, "What T27F is", holds the definition. A table separates the missing core (spec -> graph IR, a renderer in the Trinity UI) from what exists (ui_plan.t27, honeycomb geometry,t27f_viewstills, the feat(igla): Wave Loop 864 — module-scope [547][2]^6 Pt non-power-of-two outer-dimension array-of-struct variable from call with indexed signed writes #1677 application). There is a manual "show a spec" procedure (node/edge table with spans and labels, marked as a manual reading). The topic-map procedure is kept unchanged in substance as an application section.specs/skills/t27-t27f.t27: name, summary, specs (ui_plan.t27,topic_engine.t27) and tags follow; its test is updated.specs/OWNERS.md(t27f row),CLAUDE.md(pointer section),specs/t27f/topic_engine.t27(header comment only): point to the skill section instead of restating it.No function or constant of
topic_engine.t27changes. No non-t27 code.Evidence (Railway lab, sha256 of the files matches the branch)
specs/skills/t27-t27f.t27specs/t27f/topic_engine.t27grep for "T27F topic-to-value engine" over
*.mdand*.t27: 0 lines.Not in this PR
The core itself: a spec -> graph IR spec (typed nodes and edges, inference labels, source spans, deterministic output) and its tests. That needs its own issue.
🤖 Generated with Claude Code