Contributing
Most contributions add or revise knowledge entries. The CLI router does not need to change for a new model, harness, or task to appear.
Where to work
knowledge/models/— model entriesknowledge/harnesses/— harness entriesknowledge/tasks/— task entriestemplates/— task prompt templates (one per task, same id)
Use a globally unique lowercase kebab-case id, classify every claim as official, tested, community, or legacy, and record last_verified dates. Then run pnpm validate:knowledge and the release gates.
Core principle
Existence alone is not enough reason for an entry. A model or harness should have useful, maintainable, sourceable guidance. If a claim cannot be sourced, classify it honestly — including as community. Never present preference or an unscoped ranking as fact.
What a good entry includes
- A short, factual summary that does not rank or promote.
- Recommended practices grounded in documented or tested behavior.
- Cautions that name specific failure modes.
- Structured evidence entries with a class, a source, and verification dates.
- Model behavior kept in model entries; harness behavior (instruction files, permissions) in harness entries.
- No invented numbers, benchmarks, or adoption claims.