POST /domains/{id}/explain to inspect current learning state:
decision_id for current state. Supplying it explains the saved decision
snapshot instead. This inspection does not issue a new forecast receipt: use
/query for a prediction you intend to resolve later. GET /domains/{id} returns
the declaration and event count, not this live learning-state block.
Inspect these response paths:
resolved_count: completed forecast targets that have been scored.pending_forecasts: issued receipts still awaiting an outcome.calibration_groups: retained conditioning histories.mean_energy_score: score of the issued distributions; lower is better.mean_prior_energy_score: score of the corresponding unconditioned forecasts on the same outcomes; also lower is better.
resolved_count proves forecast/outcome linkage. Useful prediction is
demonstrated by held-out or prediction-before-update scores, and useful planning
by the actual outcomes or costs of the executed decisions.
For a fair application test:
- Fix the data split, target, metrics and action costs before comparing settings.
- Start separate fresh Domains with identical observations for each setting.
- Compare
conditioning: "adaptive","prior"and"kernel"; compare numeric transport on/off separately when the task has numeric targets. - In an online test, save the prediction before exposing its outcome, then learn.
- In a frozen test, train on an earlier partition and issue forecasts on a new partition without sending its outcomes, rewards or configuration changes to the learner. Score externally.
- Compare the same targets with the same scaling. Use energy score for joint distributions, Brier/log loss for categorical probabilities, numeric forecast error and interval coverage, and realized utility/cost for action decisions.
max_pending_forecasts in advance, within
its limit. Do not resolve test targets during the frozen run merely to free space:
resolution changes calibration. Query bookkeeping is distinct from learning.
