Thank you for your interest in contributing to WERR (Waves & Errors) — the open-source zero-memory, machine-native System-One fractal decision engine!
We welcome contributions ranging from edge optimizers, hardware porting (C/Rust/EVM), and new domain gates to empirical benchmark replications and documentation enhancements.
WERR operates under strict foundational contracts. Any proposed pull request must adhere to these non-negotiables:
-
Zero-Memory Tensor Contract: Core decision loops must NOT allocate persistent multi-megabyte matrix weights or tensor parameter arrays. Coordinates are parameterized by a 24-byte tuple
$\Theta = (c_x, c_y, \text{zoom})$ . - Sub-Millisecond Execution: Edge reflexes and domain gates must execute in low-millisecond/sub-millisecond timeframes on commodity CPU architectures.
- Deterministic Reproducibility: Given identical state inputs and coordinate seeds, decisions must evaluate identically across all platforms and operating systems.
- Strict Air-Gap Capability: The core engine must function with zero network access and zero external cloud dependencies.
git clone https://github.com/pCwOrM/werr.git
cd werr
git checkout -b feature/your-feature-nameWe recommend Python 3.10, 3.11, or 3.12:
python -m venv .venv
# On Linux/macOS:
source .venv/bin/activate
# On Windows (PowerShell):
.venv\Scripts\Activate.ps1
# Install package in editable mode with dependencies:
pip install -e .
pip install flake8 pytest PillowEnsure all isolated tests pass cleanly before submitting your changes:
# Run unit test suite:
python -m unittest discover tests -v
# Run isolated WindTunnel WebMCP benchmark:
python -m unittest tests.test_windtunnel_webmcp_isolated -v
# Run isolated Jevenator 2 visual localization benchmark:
python -m unittest tests.test_jevenator2_isolated -v
# Run Snake reflex gameplay benchmark:
python benchmarks/snake/benchmark_snake.py --steps 300 --mode compare- Issues First: For non-trivial architectural changes or new gate proposals, please open an issue or check existing issues to discuss the implementation strategy.
- Code Standards:
- Adhere to PEP 8 standards.
- Vectorize numerical loops with NumPy.
- Keep external dependencies minimal (standard library + NumPy preferred).
- Commit Standards:
We follow conventional commit format:
feat:New decision gate, primitive, or runtime featurefix:Bug fix or calibration adjustmentperf:Throughput acceleration or latency reductiondocs:Documentation and benchmark updatestest:New test cases or benchmark scenarios
- Pull Requests: Ensure PRs fill out the PULL_REQUEST_TEMPLATE.md completely.