INDEPENDENT RESULT VERIFICATION
Check a supported candidate or proof against the original model—even when another system produced the answer. Understand what passed, what failed and what remains unresolved.
Available products. A customer-specific workflow.
CLI · MCP · Headless
Optimization teams, engineering-software vendors and integrators that need a second checking path before using a result.
A useful implementation has a specific job. The scope is built around your original requirements, environment and acceptance criteria.
A successful solver run does not, by itself, explain whether the candidate satisfies the original requirements.
SpinForge checks the supported candidate and objective against the agreed source model and returns a report with separate integrity, solution and mathematical-completion states.
Changing an established solving workflow can be a larger project than the checking task itself.
Start with a read-only checking step. Keep the existing producer and qualify the format and evidence adapter that connects its output to the selected SpinForge checker.
A changed model, objective convention or numerical assumption can make two apparently similar answers incomparable.
Bind the evaluation to the original inputs and accepted arithmetic or tolerance rules. Compare candidates on that common basis and retain incomplete outcomes.
The final order identifies the selected products, integration work and operating responsibilities. Included components and work are not charged again.
A defined checking workflow for the admitted model, candidate and evidence combination, with unsupported inputs identified before acceptance.
Separate integrity, candidate and supported proof results, plus the objective and any limitations that affect interpretation.
Model/revision identity and the selected product’s checking artifacts, with export and retention arrangements agreed for the deployment.
CLI, MCP or headless access for the selected product, with an optional adapter and written handover for your environment.
Your current solver proposes an allocation. You want to check the original capacity restrictions and objective before a planner uses it. This is an illustrative workflow, not a customer case study.
Explanation only—not a live product run or a claimed customer deployment.Provide the supported original model, candidate and available evidence. Agree which properties must be checked and how much verification work is authorized.
Agree the supported models, execution environment and acceptance measures before committing to the delivery.
Choose the relevant capability.
Not every workflow needs every product.
Eligible software can use the existing monthly plans. A custom producer adapter, operated checking service, larger proof budget or private rollout is quoted separately. Basic result labels and required checks are not withheld as an upgrade.
Yes. The engagement can focus only on checking a supported output. An adapter may be needed, and third-party format compatibility is established before work is accepted.
Only the stated properties of the accepted model are checked. Your team must confirm that the model represents the real requirement and that the evidence is sufficient for its intended use.
No. The admitted checker and proof class are explicit. Unsupported proofs and incomplete checks are reported, not promoted to a successful proof.
UNISOLVE latest supplied inventory keeps solution, optimality, infeasibility, unboundedness and original-source trust separate. Its configured SCIP/VIPR route applies to exact linear-MIP certificates, not ordinary numerical status.
Commission the model, integration and acceptance work needed for your task. Existing products stay independently available.
Commission one supported decision model, a scoped conflict analysis and a comparison of permitted repairs.
02 / Scoped customer programCommission a revision-aware workflow that keeps models, assumptions, results and evidence connected as inputs change.
One capability. A connected workflow.
A team to put it into practice.