Product gains can remain isolated
A useful finding in one product may not inform another product’s work.
Recursive Engine is the family’s meta-system for cross-product improvement.
Synthesis / Layer 3 / KSPINFORGE / A GARMO LABS COMPANY
Recursive Engine
The synthesis meta-system through which its eleven products improve one another.
Customer outcomeDesign and discover ↗
THE PRODUCT, IN PRACTICE
One system.
Improvement across its parts.
Recursive Engine is Layer 3 of the existing synthesis family. Its stated role is the meta-system connecting the products so they improve one another. It is not a new name for Discovery Core, a standalone annealing schedule or a generic replacement for every existing runtime.
- BUILT FOR
- Teams using the synthesis family as a connected computational-improvement system.
CHALLENGES → PRODUCT RESPONSEThe problem you face.
The problem you face.
What the product changes.
YOUR CHALLENGEWITH RECURSIVE ENGINE
Different products improve different things
Schedules, algorithms, physical models and candidate evaluations have different responsibilities.
Retain those product identities while coordinating improvement across the synthesis system.
A feedback loop needs accepted outcomes
Generated changes and improved customer results are not the same event.
Scope which relationships are active and which numerical, empirical or mathematical checks govern acceptance.
WHAT YOU GETA defined capability.
A defined capability.
A useful result.
A synthesis meta-system
Layer 3 of the eleven-product family.
Cross-product improvement role
Connect the family’s products rather than treating them only as isolated tools.
An explicit architecture
Five Layer 1 products, five Layer 2 products and Recursive Engine itself.
A qualified deployment scope
State the active integrations, permitted changes and acceptance responsibilities.
EXAMPLE CUSTOMER WORKFLOW
Operate a connected improvement campaign
A team wants selected synthesis products to inform one another’s work.
Illustrative customer use—not a new benchmark or completed customer deployment.- 01→
Choose the relevant products and active relationships.
- 02→
Operate the meta-system under agreed budgets and change permissions.
- 03→
Evaluate accepted improvement for each affected product and the end-to-end task.
FIT & ACCEPTANCEStart with the task.
Start with the task.
Agree the useful outcome.
- What you bring
- The selected synthesis products, objective, integration map, change authority and acceptance policy.
- What a useful evaluation measures
- +End-to-end accepted improvement
- +Preserved product and domain requirements
- +Cost of coordination and evaluation
- Delivery
- License the selected capability, commission an implementation, or agree an operated service. Infrastructure and additional engineering are specified separately.
QUESTIONS BEFORE BUYINGA clear scope.
A clear scope.
A clear relationship.
What is the important boundary?−
The eleven-product family and Recursive Engine are existing products by the owner’s confirmation. The supplied table does not enumerate every runtime connection or establish a universal improvement rate. Cross-family additions require their own integration scope.
How is it priced?+
No new standalone price is supplied for this product; request a scoped proposal. The platform plans buy qualified workflows and capacity, not a second charge every time a compatible method is selected. Existing bundle inclusions do not expand automatically.
How do we get access?+
An existing product in the SpinForge portfolio. Request the release, available invocation interfaces and setup for your selected workflow; this publication does not invent executable commands or MCP tool names.
PUT THE PRODUCT TO WORK
Tell us what needs to improve.
Bring a task, an accepted outcome and the environment in which the product needs to work.
PRODUCT RELATIONSHIPS
Related, not interchangeable.
Gödel Optimizer
A self-evolving optimizer that improves its optimization algorithms.
Neural Schedule
Learned temperature schedules for annealing through a Fourier neural operator.
GARMO Scientist
An autonomous discovery product organized around perceive → hypothesize → experiment → learn.
SpinForge Discovery Core
The shared computational engine behind AMDE and SpinForge Bio.
ONE PLATFORM
Choose a qualified workflow.
Select the capability you need directly or include its compatible role in a qualified platform workflow. Production scope identifies release, environment, capacity and support; a product count is not an entitlement.
Explore monthly plans See the system connectionsSTART WITH THIS PRODUCT
Use the software directly or ask us to scope the implementation.