Skip to main content
Adaptive Policies update online from structured observations and return the current structured prediction immediately.

Route sequence

The result is read from:
Do not read this result from predicted_observations, POST /api/v1/domains/{domain_id}/query, or POST /api/v1/domains/{domain_id}/explain. Those belong to the Domain Reasoning and audit contracts.

The adaptive template

The currently exposed interval-policy integration is configured under the exact key:
The template declares how to read the application’s observation and how to name the returned rows: The field mapping is the integration boundary. It translates schemas; it does not solve the task.

Generic integration pattern

The same public route returns a richer object than a downstream consumer may require. A thin adapter can select accepted fields while leaving the adaptive reasoning in Adapt-1.

State and ordering

The policy is online and stateful per domain/session. Send observations in order and use one writer unless interleaving is intentional. Call POST /api/v1/domains/{domain_id}/adapt/reset to start a new policy history. Also call this route to rebuild state from a known observation record. Use POST /api/v1/domains/{domain_id}/adapt/predict to read current state without adding an observation. Policy thresholds determine when an item appears in the output. Do not document a universal number of observations unless the selected template configuration guarantees it.

Scope

adaptive_interval_policy is one exposed public policy template. Its interval-shaped fields are not the boundary of Core or Adapt-1. The architecture is the self-contained substrate behind the gateways; this page documents one concrete structured-output contract.