Repository navigation
docs: glossary separates T3 (upstream) from Chromeria (our fork) - #198
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
github-actions
Bot
added
vouch:trusted
lukemaj
added a commit
that referenced
this pull request
Oct 14, 2026
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 14, 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
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.
What: The glossary now says "T3" means upstream T3 Code and "Chromeria" means this fork and everything built from it, including its server on any machine.
Why: The user wants names that show at a glance whether a conversation is about upstream or our code, without renaming code (which would break every rebase).
So what: Merge needs the user's approval; agents then use the two names this way.
Also changes "T3 project" to "Chromeria project" in the Promachos home entry, and realigns the table.
Refs #177.
Elon record
Requirements and who asked: User asked for T3 = upstream, Chromeria = our code, recorded for all agents.
Deleted: Renaming code, folders, database, port or protocol (user dropped it; it breaks rebases and T3 Connect).
Bottleneck: None; one-file docs change.
Checked myself: Rendered diff of
GLOSSARY.md; oxfmt check.🤖 Generated with Claude Code