Can your calculations survive an independent check?

A public repository or a non-confidential example; the expected behaviour; the version and environment; and the decision that depends on the result. For a calculation engine, include the written rule and a representative input.

Good starting points include unstable gradients, dtype or boundary behaviour, an unexplained discrepancy, or a rule implemented differently from its specification.

1. A written scope with assumptions and acceptance criteria.
2. Reproduction steps and an executable check where the question permits it.
3. Findings separated into a reproduced mismatch, an unsupported inference, a coverage gap or no defect found within the tested scope.
4. A concise report linking each conclusion to evidence, with possible next checks.

Finding no defect is not a certificate that the entire system is correct. A local numerical check does not establish safety, regulatory compliance or model quality as a whole.

The GERO research journal contains numerical audits, technical notes and source-based analysis. Publication labels distinguish original analysis from reproduced results.

For a concrete service example, see calculation contracts in Apache Fineract: turning a written rule into an executable check and documenting the mismatch inside its stated scope.

Request an initial scoping discussion. A pilot can focus on up to five agreed, non-confidential calculation paths. We confirm whether the problem is checkable, which artifacts are needed, and the deliverable, timing and price before starting.

No customer data is needed for the first conversation. A reduced example is usually the most useful beginning.