|
| 1 | +# Contributing to RecurQuant |
| 2 | + |
| 3 | +RecurQuant is an alpha research package with a deliberately narrow supported |
| 4 | +surface. Contributions are most useful when they include a small reproducer, a |
| 5 | +regression test, and an explicit statement of what the result does **not** show. |
| 6 | + |
| 7 | +## Set up and check a change |
| 8 | + |
| 9 | +The repository baseline is Python 3.11. On Windows, the same setup used by the |
| 10 | +project is: |
| 11 | + |
| 12 | +```powershell |
| 13 | +uv venv --python 3.11 .venv |
| 14 | +uv pip install --python .venv\Scripts\python.exe -e ".[dev,eval]" |
| 15 | +.venv\Scripts\python.exe -m pytest |
| 16 | +.venv\Scripts\python.exe -m ruff check . |
| 17 | +``` |
| 18 | + |
| 19 | +On Linux or macOS, replace `.venv\Scripts\python.exe` with |
| 20 | +`.venv/bin/python` in the last three commands. |
| 21 | + |
| 22 | +The full-model experiments are separate from the unit suite and download public |
| 23 | +model weights. Do not run them merely to validate a small code change. If a |
| 24 | +change affects Qwen3.5 integration, also run the smallest relevant smoke path |
| 25 | +documented in [compatibility and support](docs/compatibility.md), and report the |
| 26 | +exact model revision, device, dtype, attention implementation, and Transformers |
| 27 | +version. |
| 28 | + |
| 29 | +Before submitting a change: |
| 30 | + |
| 31 | +- add or update a focused test for changed behavior; |
| 32 | +- run the complete unit suite and Ruff command above; |
| 33 | +- keep generated evidence separate from hand-written interpretation; and |
| 34 | +- do not include access tokens, authentication files, private prompts, |
| 35 | + proprietary model data, or local machine secrets in code, logs, artifacts, or |
| 36 | + issues. |
| 37 | + |
| 38 | +## Evidence and claim boundary |
| 39 | + |
| 40 | +Use the terminology in [the project claim boundary](research/CLAIM_BOUNDARY.md). |
| 41 | +In particular: |
| 42 | + |
| 43 | +- report packed **resident recurrent-state bytes** separately from model |
| 44 | + weights, attention KV caches, activations, allocator overhead, and the one |
| 45 | + state materialized during a layer call; |
| 46 | +- do not turn byte accounting into a speed, latency, peak-CUDA-memory, or |
| 47 | + whole-model-memory claim; |
| 48 | +- do not describe recurrent-state quantization itself as new, and do not call a |
| 49 | + result a breakthrough from a diagnostic trace or a development split; |
| 50 | +- attach the command, pinned revisions, environment, metric definition, and |
| 51 | + machine-readable artifact for a new numerical claim; and |
| 52 | +- preserve failed gates and negative results instead of silently replacing |
| 53 | + them. |
| 54 | + |
| 55 | +The current supported package boundary is recorded in |
| 56 | +[docs/compatibility.md](docs/compatibility.md). A new model, Transformers minor |
| 57 | +release, execution backend, generation mode, or hardware target is unsupported |
| 58 | +until it has a regression test and clearly scoped full-model evidence. |
| 59 | + |
| 60 | +## Keep pull requests reviewable |
| 61 | + |
| 62 | +Keep each change to one testable behavior. In the description, state the |
| 63 | +problem, the exact verification commands, any new evidence file, and the claim |
| 64 | +boundary affected. Documentation-only corrections should identify the source |
| 65 | +artifact or code path that makes the replacement wording factual. |
0 commit comments