01 / FIXTURE
Pin a case
A request that produces a wrong or unexplained answer is worth more than a bug description. Added to the corpus, it holds every engine to it forever.
must pass make gate
CONTRIBUTE / THE MOST USEFUL THING IS A FIXTURE
Bring a case the engines get wrong.
Determinism makes contribution cheap: a reproducible disagreement is a file, and the gate can tell whether your change fixed it.
Ways in
02 / RULE
Close a capability gap
Implement a field one engine still rejects, in this order: schema, implementation, fixture, matrix row, independent recomputation, docs.
must pass make gate
03 / RUNTIME
Bring a language
The contract is JSON on stdin. A new binding is a new implementation held to the same corpus, not a port of an existing one.
must pass make gate
04 / DOCS
Make the contract readable
The reference is precise but dense. Explaining one field well is a first-class contribution.
must pass make gate
05 / CARRIER
Add a connector
The connector contract is versioned and lives outside the engines. Rating data is the caller's; no solver acquires a network call.
must pass make gate
06 / EVIDENCE
Measure something
Any performance claim needs pinned datasets, competitor versions, limits and raw artifacts. Producing those is real work and it is welcome.
must pass make gate
PROJECT HEALTH
The rules are visible before your first issue.
Contribution, support, security and governance expectations live in the repository. The site links to the canonical files instead of maintaining a second set of rules that can drift.
01README.mdrequired before launch
02LICENSErequired before launch
03CONTRIBUTING.mdrequired before launch
04CODE_OF_CONDUCT.mdrecommended
05SECURITY.mdrecommended
06SUPPORT.mdrecommended
07GOVERNANCE.mdrecommended
08Issue / PR templatesrecommended