Skip to main content
Build a small process-output predictor. Supply completed observations, let Adapt-1 discover an input projection, and query again with the output withheld. The included data is a synthetic fixture, not a real physical process or a benchmark. No database, simulator, SDK, or additional Python package is needed.

Run the example

Use Python 3.10 or later and an API key from the quickstart. Running this script creates one fresh Domain and sends the observations below. It never clears existing state.
Environment
The requests use Transition Discovery. The script saves your actual responses so you can inspect admission, predictions, and retained state. Save this complete file as first_learned_result.py:
first_learned_result.py

Read your actual responses

The script prints three frames and saves the complete responses. Read the saved prediction and support fields for your run. Early events may report projection_accumulating while Discovery forms a usable projection. They can be buffered and rebuilt when the projection becomes ready. Review learner_eligibility in each saved receipt; a stored event alone is not proof of learner admission. Only consume predicted values when transition_prediction.status is predicted. Keep the returned prediction object and its support information. Extract the target value using the response contract for your configured target. The final comparison checks exposed transition sample counts and model versions. It is a limited retained-use check, not proof that every subsystem is frozen. See Choose a learning setup for the full evaluation boundary.

What you supplied, and what Adapt-1 formed

No input path list, predictive rule, formula, or answer for the query is supplied to Adapt-1. There is no reward call because this example learns an observable target, not the utility of a selected action.
Keep the printed Domain ID and the same authenticated owner to reconnect to retained state. Running this script again intentionally creates a new Domain. It never resets or deletes the old one. Remove a tutorial Domain only through an explicit, ID-scoped deletion after deciding its state is no longer needed. The local response files can contain application data; protect them accordingly.

Use your own records

Replace the fixture with completed application records and the query with current measurements. Keep the target unavailable at query time. A new target path or type requires a matching event contract. Keep evaluation records separate before ingestion; successful integration does not establish real-world prediction quality.

Other prediction and Discovery patterns

Use categorical outputs, structural discovery, or before/after observations.

Learn from an executed decision

Bind the measured outcome to a policy and inspect the later preference.