FOR DEVELOPERS AND CODING ASSISTANTS

One engine.
A clear path into the network.

Describe the contract once. Generate its native route, MCP schemas and catalogue entry. Keep the numerical method and its evidence under review.

Read the complete AI authoring guide →

1. Define the question and its boundaries

State inputs, units, outputs, assumptions, uncertainty and a maximum amount of work. Start from a reproducible reference, not an attractive demo.

2. Scaffold, implement, validate

npm run engine:init -- my_engine
npm run engine:validate
npm run engine:generate
npm run engine:check
npm run test:engine-kit

The generated scaffold is a draft and cannot be called in production. Implement the Rust method and independent tests before explicitly activating its manifest. A declared review status is not a scientific certificate.

3. Choose optional orchestration

Direct MCP access remains independent. A planner binding can advertise a complete request and result. Combining results from different engines still requires a reviewed adapter with correct units, models and uncertainty; JSON compatibility alone is insufficient.

4. Show the evidence

Run native and real MCP checks, preserve reference comparisons and document limitations. Demonstrations and 3D scenes remain curated. The kit does not invent scientific guarantees or publish unfinished methods.

The first migrated engine is compute_orbit; legacy tools are being migrated progressively. The initial manifest format supports bounded CPU engines.

Have a calculation in mind? Submit a suggestion · Connect to the existing tools