- 1
Open an issue
Say what is wrong or missing, and for which architecture. Use the template that matches: a correction to an architecture, a new architecture, a compatibility verdict you disagree with, or a problem with the site.
- 2
Open a pull request linked to it
Change the data file, run the validation command, and open a pull request whose description contains
Closes #followed by the issue number. A pull request without a linked issue is not merged.- Architectures live in
data/architectures/, one YAML file each, checked againstschema/architecture.schema.json. - Compatibility verdicts live in
data/compatibility/. They are produced by raters followingtools/matrix/rubric.md. To contest one, argue from the rubric in the issue. npm run validatemust pass. The same command runs on every pull request.
- Architectures live in
What the site will not take
- A variant presented as a new architecture: another model, prompt, domain or parameter, or two existing architectures used together. See how an architecture gets in.
- Text, code or images copied from another project.
- Anything that makes the site call a server or a model. It is static by design.