Automation review card

Review the exact work before starting it, and inspect the resulting run after it starts. A saved draft, an approved version, an active schedule and a completed run are different records. Keep their identities beside the decision they support.

Hosted read-route reference

GET /hvy/v1/loops
GET /hvy/v1/loops/{loopId}/versions/{version}/artifact
GET /hvy/v1/loops/invocations/{idempotencyKey}
GET /hvy/v1/loops/runs/{runId}

These are method-and-path references, not complete requests. They do not supply an address or authentication.

Separate governed example

{
  "schema": "ouros.loop-execution.v1",
  "name": "Save a reviewed note",
  "revision": 1,
  "steps": [
    {
      "functionId": "notes.save",
      "functionRevision": 1,
      "args": {
        "title": "Reviewed note",
        "body": "This text was reviewed before preparation."
      }
    }
  ],
  "start": false
}

This prepared note-saving example belongs to a separate governed workflow format. It is not a hosted loop artifact or a universal import file. Reading or downloading it performs no action.

Recovery worksheet

service: SERVICE_NAME
operation_id: OPERATION_ID
idempotency_key: ORIGINAL_KEY
request_body_file: path/to/original-request.json
version: EXACT_VERSION_IF_APPLICABLE
last_observed_state: STATE

Record the original request privately. If a response is uncertain, inspect existing work before making a new request. Do not infer completion from acceptance or infer activation from saved schedule text.