3 KiB
Contributing
Thank you for contributing to this repository.
This project is maintained with a focus on inspectable work, verifiable references, and clear scope boundaries.
To reduce ambiguity and avoid overstated claims, contributions are routed into a small number of reviewable lanes.
At the current stage, there are two primary contribution lanes. Most accepted PRs are expected to fall into one of them.
Priority lane A: Tension Universe MVP Experiments
The highest priority contribution path is expanding and improving the Tension Universe MVP experiment layer.
This lane focuses on adding or improving MVP experiment pages under the TensionUniverse/Experiments/ collection.
An MVP experiment here does not mean a solved claim, a final proof, or a complete benchmark. It means a narrow, inspectable page with explicit assumptions and a reproducible or at least reviewable protocol.
Typical contributions in this lane include:
- adding a new MVP experiment page for an open Tension Universe problem
- improving an existing MVP experiment page with clearer structure, tighter scope, or better protocols
- attaching small supporting artifacts that belong to the MVP page, such as notebooks, Colab links, screenshots, or structured notes
Start here:
Priority lane B: Recognition Map updates
The second priority lane is maintaining a verified, public recognition record of where WFGY has been cited, integrated, adapted, or discussed across the ecosystem.
If you find a public repository, benchmark, article, doc page, course page, or discussion that includes WFGY, you are welcome to help keep this list accurate.
You can contribute by:
- adding a missing entry
- updating an outdated description
- attaching a better proof link
- correcting categorization
- submitting a PR with a new citation or integration
Forks and PRs are welcome. If your project includes WFGY in any public form, feel free to add it to this recognition list with a short description and a verifiable link.
Recognition Map:
Other contributions are also welcome
In addition to the two priority lanes above, other forms of contributions are welcome, for example:
- wording and clarity improvements
- typo fixes
- broken link fixes
- navigation and formatting improvements
- small documentation refinements that reduce confusion for readers and automated tools
If you are unsure which lane your contribution belongs to, open a short issue first and describe the intended change and the target file.
Review expectations
To keep contributions aligned with scientific practice and public auditability:
- keep scope narrow and assumptions explicit
- avoid exaggerated claims, especially for early MVP work
- prefer verifiable links and reproducible steps over broad statements
- for recognition entries, include a public proof link whenever possible