Skip to main content
Choose an Adapt-1 workflow when learning from observations and outcomes, or retaining evidence and corrections, can improve a result your application uses. For work centered on interpreting prose or generating it, use a language model for that part of the application. The use cases show where Adapt-1’s learning and retained state contribute to a workflow. The quickstart checks authentication. First learned result contains a complete observation-to-prediction program.

What should Adapt-1 return?

Choose the scope

State gateway

Use prior evidence and constraints without defining a task grammar. The bearer token determines hosted identity.

Domain

Keep a task contract, its observations, outcomes, and learned state together under a domain_id.
Use State when evidence and corrections retained across requests improve subsequent work. Queries use that evidence in the context of the current request, and corrections update records as their content changes. State accepts these records without a Domain declaration. Use a Domain when the application has a defined prediction, decision, or control task to learn and evaluate. For independent results, use an applicable route with the documented non-retaining behavior. Control query writes with the route’s retention setting; allow_exploration controls exploration. See HTTP and contracts.

Define one useful interaction

1

Name the result

Write what code needs back: a numeric prediction, a selected action, a command sequence, a hypothesis, or an evidence packet. Use the result fields documented for the selected route.
2

Provide the public task contract

Both Discovery and authored setups use a Domain. Define observation and outcome meanings, result type, available choices when needed, and boundaries. Use Discovery when supported learner-facing structure should form from evidence. Author the structure when it must remain explicit and reviewed.
3

Complete the return path

Use the result and return the eligible observation or measured outcome. Prediction tasks learn from completed records; control feedback identifies the executed action.
4

Check the later result

Check learner admission before querying again. Compare the relevant learner diagnostics to determine whether the update was applied.

Configure scope and learning

The learning schedule applies to both Discovery and authored Domains. Either can accumulate experience during use or reuse state acquired earlier with learning frozen.
A Domain declares the task interface. Keep the correct action, hidden mapping, and withheld target out of the pre-result inputs. Use outcome feedback when the application can measure and attribute a consequence. Evidence-only workflows can use the State gateway.Complete the worksheet with one concrete item or action before implementing the full run. Write the query-time input, the result your code will consume, and the evidence returned afterward. For a structured prediction, specify the target shape and units. For an action, specify its parameters, duration or completion boundary, and the outcome attributed to it.Use multistep action setup or structured scene setup to turn these choices into a learning loop. Choose retention and reset boundaries through Learning schedules.

Use cases

Explore forecasting, causal discovery, adaptive workflows, diagnosis, spatial reasoning, and learned control, with concrete inputs and feedback.

Build with an AI agent

Turn the selected workflow into a bounded implementation and test plan.