Contributing

Build on the source, verify behavior and make evidence reviewable.

Production boundary & delivery status

Authored Warlock production code uses Elm and Haskell only: every GUI element uses Elm, Haskell owns the backend and reviewed native/runtime integration, and no Python runtime ships (see Production boundary). At snapshot 6e6ad828c (2026-11-02 canonical ledger), 19 of 242 whole EARS requirements and 42 of 417 scenarios hold historical source-bound acceptance alongside published Store foundation a327c8f7f and persistent custody component 6e6ad828c; browser demonstrations never qualify native Wayland behavior or release readiness.

Work from the source

Use the GitHub contribution guide for the project workflow, source entry points and checks. This external reference opens only when selected.

Ground changes in evidence

Use the original requirements and source as behavior authority. Record the scenario and observed result, and distinguish native evidence from browser fixtures and frozen catalog specimens. Run checks appropriate to the change and report remaining verification.

Run static & admission checks

Verify static documentation, contract registries, and acceptance unit checks locally without network access before handing off changes:

python3 -B site/tools/check-site.py --root site
python3 -B site/tools/test-browser-acceptance.py
python3 -B plugins/warlock-contributor/scripts/warlock.py check --project-only

Admission checks verify contributor slice hygiene only; Root-serialized tools/qa_cpu.py suites and stock Omarchy Wayland guest campaigns are separate verification tracks (see reproducible MVP tracks).

Contribute to the design language

Study the foundations and component guidance alongside the current implementation. Preserve accessible names, keyboard access, stable targets and outcome boundaries when changing a surface.