Activate Handoff generation at a Source boundary

POST
/v1/handoff/activate

Evaluate the standard Handoff Trigger and synchronously execute any emitted PrepareHandoff Action. Start a requested work transfer from an existing exact boundary Source and objective. Inspect a generated Draft before finalizing it. An ignored boundary does not establish a new handoff; do not claim a committed milestone. Conceptual or preview-only requests do not authorize this write.

Authorization

BearerAuth
AuthorizationBearer <token>

Bearer credential resolved to an opaque authenticated Principal by the Server deployment.

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/v1/handoff/activate" \  -H "Content-Type: application/json" \  -d '{    "scope_id": "string",    "boundary_source": {      "name": "string",      "source_id": "string"    },    "objective": "string"  }'
{  "status": "generated",  "boundary_source": {    "name": "string",    "source_id": "string"  },  "previous_position": 0,  "current_position": 0,  "draft": {    "generation": {      "receipt": "string"    },    "objective": "string",    "state": [      {        "text": "string",        "citations": [          {            "kind": "source",            "source_ref": {              "name": "string",              "source_id": "string"            }          }        ]      }    ],    "disposition": "continuable",    "next_action": {      "text": "string",      "citations": [        {          "kind": "source",          "source_ref": {            "name": "string",            "source_id": "string"          }        }      ]    },    "omissions": [      {        "text": "string",        "citation": {          "kind": "source",          "source_ref": {            "name": "string",            "source_id": "string"          }        }      }    ]  }}

Record a completion-aware Task Outcome POST

Preserve one attempt's status and checks, optionally linked to the exact accepted Handoff Receipt that the result covers. Record observed results at a real completion or interruption boundary. Preserve failed, skipped, timed-out, unavailable, and unknown checks accurately. An ordinary turn ending does not mean the task is complete. Recording an Outcome does not approve an Experience or grant execution authority.

Generate an inspectable Handoff Draft POST

Requires exact returned Source or Artifact citations, never raw facts or invented references. If none exists, capture the inspected facts as a Source first. Prepare an inspectable PowerContext Handoff Draft from exact evidence for a requested transfer. Inspect facts, omissions, and the next action before finalizing. The Draft is temporary and grants no authority; preparation is not a durable commit or proof that a receiver continued the work.