Skip to content

docs: adding a language now includes its keyword-rosetta control folder #2559

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
squid-protocol merged 1 commit into from
Aug 31, 2026
Merged

docs: adding a language now includes its keyword-rosetta control folder #2559

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 18 additions & 1 deletion gitgalaxy/standards/how_to_add_a_language.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -442,4 +442,21 @@ to a handful of languages, define it here the same way: a short name, its `re.co
pattern, and a one-line INCLUDES description, listed under a new `### <Name> Extension Pack`
heading naming which languages carry it. Keep extension keys out of the baseline schema above —
that schema is the one every language is expected to implement to Strict Feature Parity (Rule
4); extension packs are deliberately the exception, not the rule.
4); extension packs are deliberately the exception, not the rule.
## After the language lands: the control-corpus folder (keyword-rosetta)

Every language in `LANGUAGE_DEFINITIONS` has a matching control folder in
[keyword-rosetta](https://github.com/squid-protocol/keyword-rosetta) (built for issue #1096):
the same 12-probe program shell expressed in that language, planted with exactly known
signal-keyword counts and gated end-to-end by that repo's `tools/verify_language.py`. It is
the project's cross-language measurement-consistency instrument — the gitgalaxy README's
bias-variance chart regenerates from it.

Adding a new language here without authoring its control folder there reopens the blind spot
that corpus exists to close, so treat the folder as part of the language addition, not an
optional follow-up. Author it per that repo's
[`SPEC.md`](https://github.com/squid-protocol/keyword-rosetta/blob/main/SPEC.md) (canonical
shell + decoy rules + workflow) and
[`docs/GATING.md`](https://github.com/squid-protocol/keyword-rosetta/blob/main/docs/GATING.md)
(deviation-ledger lifecycle); its CI runs the verifier on any changed `data/` folder. Corpus
integration on the gitgalaxy side (pinned-tag CI gate) is tracked in #2557.
Loading