Configure the stable-history reference criteria, default relative-current route, optional frequency/context specializations and frequency-return verification. The same execution routine is used for standalone and stationary recovery. No branch map is required.
Without perturbations the output is a proposal only. With explicitly approved perturbations the card first verifies the reference, then records each displacement, recovery path and fresh return evidence. Qualification covers only the recorded conditions; it is not proof that every branch can be recovered.
Set execution_mode to agent for task-model parameter proposals or to
deterministic to use the configured route unchanged. Select the gateway with
agent_card_id; model and effort follow the admitted card profile, optionally overridden with
execution_profile. The card gathers a fresh baseline before proposing or testing.
The task model authors the explanation from the actual host receipts.
Agent proposals are untrusted data. The host validates their schema and admitted excursion corridor; agents cannot expand safety authority, replace operation epochs or label untested parameters verified. Task-model explanations and host receipts must be retained separately.
The artifact records the algorithm revision, parameter values, applicability and trial results. Archived v1 map-derived artifacts remain readable but are not executable policies for the new recovery card.