TensorCraft-HPC is maintained as a stabilizing reference project. Contributions are welcome, but the bar is intentionally biased toward correctness, clarity, and maintainability.
Good contributions usually do one of these:
- fix correctness, build, packaging, or documentation issues
- tighten the project surface so it is easier to understand and maintain
- improve tests, validation, or workflow reliability
- align implementation with OpenSpec requirements
Changes that add broad new scope should start with a strong OpenSpec rationale.
- Review the relevant files in
openspec/specs/. - For behavior, architecture, workflow, or documentation-surface changes, create or update an
active change under
openspec/changes/. - Keep the implementation tied to that change.
- Run the minimum meaningful validations before opening a PR.
- Use
/reviewbefore merge for structural or governance changes.
specs/ remains in the repository as historical context only.
cmake --preset cpu-smoke
cmake --build --preset cpu-smoke --parallel 2
cmake --install build/cpu-smoke --prefix /tmp/tensorcraft-install
python3 -m build --wheelcmake --preset dev
cmake --build --preset dev --parallel 2
ctest --preset dev --output-on-failurepython3 -m pip install pre-commit
pre-commit installThe recommended baseline is:
clangdfor C++/CUDA navigationcmake --preset devto generatebuild/dev/compile_commands.json- the checked-in
.vscode/recommendations if you use VS Code
Every PR should:
- reference the active OpenSpec change when relevant
- explain what was removed, consolidated, or fixed
- list the validations that were run
- keep docs, workflows, and repo metadata aligned
Merge quickly after review. Avoid long-lived branch drift.