Record a completion-aware Task Outcome

POST
/v1/work/outcomes/record

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.

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

application/json

curl -X POST "https://example.com/v1/work/outcomes/record" \  -H "Content-Type: application/json" \  -d '{    "scope_id": "string",    "source_id": "string",    "outcome": {      "schema": "powercontext.task-outcome.v1",      "trust": "untrusted_observation",      "objective": "string",      "status": "succeeded",      "summary": "string",      "observations": [        {          "text": "string",          "basis": "declared",          "evidence": [            {              "kind": "source",              "source_ref": {                "name": "string",                "source_id": "string"              }            }          ]        }      ],      "checks": [        {          "name": "string",          "status": "passed",          "basis": "declared",          "evidence": [            {              "kind": "source",              "source_ref": {                "name": "string",                "source_id": "string"              }            }          ]        }      ],      "produced_artifacts": [        {          "family": "string",          "artifact_id": "string",          "revision": 1        }      ],      "remaining_work": [        "string"      ]    }  }'
{  "kind": "work-contract",  "source": {    "name": "string",    "source_id": "string"  },  "position": 1,  "content_digest": "stringstringstringstringstringstringstringstringstringstringstringstrin"}

Resolve and acknowledge a Handoff POST

Re-resolve one prepared or exact Handoff, check evidence, and capture the receiver's explicit live-state, capability, and authorization checks. Record the receiver decision for an exact prepared or committed Handoff after checking readable evidence, live state, capabilities, and authorization. Never acknowledge an unresolved latest selector or report accepted while required checks are unknown. Acknowledgement does not execute or complete the task.

Activate Handoff generation at a Source boundary POST

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.