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.
Determinism makes contribution cheap: a reproducible disagreement is a file, and the gate can tell whether your change fixed it.
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.
Implement a field one engine still rejects, in this order: schema, implementation, fixture, matrix row, independent recomputation, docs.
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.
The reference is precise but dense. Explaining one field well is a first-class contribution.
The connector contract is versioned and lives outside the engines. Rating data is the caller's; no solver acquires a network call.
Any performance claim needs pinned datasets, competitor versions, limits and raw artifacts. Producing those is real work and it is welcome.
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.