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

must pass make gate
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.

02 / RULE

Close a capability gap

Implement a field one engine still rejects, in this order: schema, implementation, fixture, matrix row, independent recomputation, docs.

03 / RUNTIME

Bring a language

The contract is JSON on stdin. A new runtime is held to the same corpus as every existing one, and passing it is the acceptance test.

04 / DOCS

Make the contract readable

The reference is precise but dense. Explaining one field well is a first-class contribution.

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.

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.

PROJECT HEALTH

The rules are visible before your first issue.

README, LICENSE and CONTRIBUTING already live in the repository. Support, security and governance expectations are documented here as the canonical source. Every published runtime package's repository also carries a CONTRIBUTING and SECURITY file, checked live against GitHub rather than assumed.

01README.mdrequired before launch
02LICENSErequired before launch
03CONTRIBUTING.mdrequired before launch
04CODE_OF_CONDUCT.mdrecommended
05SECURITY.mdrecommended
06SUPPORT.mdrecommended
07GOVERNANCE.mdrecommended
08Issue / PR templatesrecommended