Contributing¶
Thanks for your interest in Structural Isomorphism. This project welcomes contributions from researchers, engineers, students, and anyone curious about cross-domain validation of self-organized criticality.
The canonical source for the contribution guidelines is CONTRIBUTING.md in the repository root. This page summarizes the workflow.
Code of Conduct¶
This project adheres to the Contributor Covenant. By participating you agree to uphold its terms.
Ways to contribute¶
- Report bugs via GitHub Issues.
- Suggest features or new validation phases.
- Improve documentation, tutorials, or translations.
- Submit pull requests for bug fixes or features.
- Replicate existing phases on new datasets.
- Propose adversarial test cases (pre-registered exponent bands).
Setup local development¶
git clone https://github.com/dada8899/structural-isomorphism.git
cd structural-isomorphism
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev,tutorials]"
Run the tests:
pytest v4/tests/sanity -m sanity -v # unit tests
pytest v4/tests/integration -v # integration tests
make test-all # full suite
Pull-request workflow¶
- Fork the repository and create a topic branch:
git checkout -b feat/<short-desc>. - Make your changes with clear commit messages following Conventional Commits.
- Add or update tests for your changes.
- Run the full test suite locally and ensure it passes.
- Open a PR against
mainwith a clear description of what changed and why. - Address review feedback promptly.
Style¶
- Python: PEP 8 enforced by
ruffandblack. Type hints encouraged. - Commit scope:
feat(soc-pipeline):,fix(d1):,docs:,test:,chore:. - Documentation:
YYYY-MM-DDdate format in markdown. - One semantic change per commit; one feature per PR.
Reporting research issues¶
If you spot a methodological problem with a phase verification or paper:
- Open an issue with the
researchlabel. - Cite specific files/lines and the relevant literature.
- We treat scientific concerns at the highest priority.
Questions¶
- General: GitHub Discussions.
- Maintainer contact: see
GOVERNANCE.md.