The contributor path

For someone changing ignis — a fix, a feature, a kernel, a page of this guide. The owner works with coding agents, and the rules they follow are the rules here.

1. Contributing — the ground rules and the repository’s layout.
2. Building from source — the kernel leaf, the Rust workspace, the CPU mock that needs no card.
3. Testing — the default suite, the GPU profile, the Playground’s and the guide’s checks.
4. Working with make — the targets, the daemon mode agents use, the GPU guard.
5. How ignis serves a request and the glossary — the vocabulary the code and the issues use.
6. How work is tracked — issues and their labels, specs, ADRs, contracts, findings, this guide, commits.
7. Cutting a release — the version, the changelog, the tag, and what the workflows publish.

Caution

The card runs one GPU job at a time, across every worktree and agent session. make gpu-status before the GPU profile, a bench run or a single --ignored test: two runs on one card means one of them dies with no diagnostic.

Tip

A user-visible change is not done until this guide says what the code now does, in the same commit. The pages under reference/ are generated: change the code and run make docs-reference.