ADR 0005: the test corpus and the published examples are separate artifacts - #49
Merged
Merged
Conversation
Decides #44, which blocked #26. Three things settled it, and the numbers are in the record so it does not get re-argued from intuition: the two artifacts need incompatible compiler pins (a regression corpus must track main, published examples must track a release), 36 of 36 commits touching test_scripts in 90 days also touched compiler source, and the fixtures are internals notes rather than teaching material. The consequences section is explicit about what this costs - two corpora that will diverge, and no release-level guarantee for the examples until the release jobs are written - so the follow-up work is visible rather than implied.
This was referenced Aug 14, 2026
|
| Filename | Overview |
|---|---|
| docs/decisions/0005-test-corpus-and-examples-are-separate.md | Adds ADR 0005 with supporting evidence, the selected artifact boundary, and its operational consequences. |
| docs/decisions/README.md | Adds ADR 0005 to the architecture-decisions index. |
Reviews (2): Last reviewed commit: "Qualify every cross-repo issue reference..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
A bare '#51' after 'muxlang/mux-runtime#50' does not inherit the qualifier - it resolves against mux-context, so most of the defects cited as evidence pointed at the wrong repo. They are the argument for the examples repo existing, so they have to be followable. Raised by Greptile on #49.
|
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.
Decides #44, which blocked #26.
Records that
mux-compiler/test_scripts/andmux-examplesare two artifacts and that the corpus does not move.The three findings that settled it, with the numbers, so it is not re-argued from intuition later:
main; published examples must track a release or they teach syntax the playground rejects. No single corpus satisfies both.test_scripts/in 90 days also touchedmux-compiler/src/.*mut Valueslots and capture cells.Drift, the main argument for merging, had not materialised: 9 of 224 named website snippets shared a filename with a fixture, and those were deliberately different.
The consequences section is deliberately unflattering about the costs: two corpora that will diverge on purpose, mux-compiler taking a CI dependency on mux-examples, and no release-level guarantee for the examples until the release jobs exist. It also records that authoring the first corpus found nine defects, which is the strongest argument for the repo existing.
Implemented by muxlang/mux-examples#1.