Skip to main content
Use the documented interval/scalar policy when ordered observations should update a structured output. Configure the template once, then ingest and read using its exact field mapping. The policy updates its retained state from ordered observations. Each response exposes the current structured result under the configured output key.
Machine-actionable result
The application consumes the contract-defined policy result directly.
No generated language required
response
prediction
<output_key>
structured policy result
adapt/events
Updates policy state from the submitted observation and returns its current prediction.
adapt/predict
Reads the same output contract without adding another observation.
Downstream boundary
Validate, display, route, or execute the object in application code.

​
Workflow

declare domain → reset known state → send ordered observations → read prediction → validate or act → continue

​
Gateways

​
Input mapping

When the application’s input fields differ from the domain’s declared observation fields, an optional mapping can translate them. If the fields already match, the application can send the observation directly. Adapt-1 updates the policy state and returns the contract-defined structured prediction; another optional mapping can select or rename output fields for the consumer’s schema.
Keep mappings limited to schema conversion so Adapt-1 receives the observations used to update policy state.

​
Validation

Assert on the object under prediction.<output_key>. Check schema validity, the required business condition, and whether reset followed by the same ordered observations reproduces the expected result. Use the adaptive response to inspect the interval-policy result. Domain reasoning audit data is available through /explain.

​
Route contracts

  • POST /api/v1/domains/{domain_id}/adapt/events updates policy state and returns a structured prediction.
  • POST /api/v1/domains/{domain_id}/adapt/predict reads the current prediction without adding an observation.
  • POST /api/v1/domains/{domain_id}/events records a normal domain event.
  • POST /api/v1/domains/{domain_id}/query and POST /api/v1/domains/{domain_id}/explain return domain reasoning and audit fields.
  • POST /api/v1/domains/{domain_id}/feedback reports an outcome.
The Adaptive structured predictions guide describes the interval-policy template fields. Structured transition learning uses a different Domain contract. This contract predicts an observable consequence from configured inputs and an optional action or intervention. Domain query and explanation routes return support and abstention. Read Design Domains for transition learning before you select event boundaries, evidence geometry, grouping, targets, or support controls.