Record a bootstrap delivery outcome

POST
/v1/context/bootstrap/receipts

Atomically claim one pending content-free receipt as injected or failed. A second injected claim is rejected with 422, so concurrent lifecycle hooks cannot both inject the same package. A terminal outcome never changes.

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

curl -X POST "https://example.com/v1/context/bootstrap/receipts" \  -H "Content-Type: application/json" \  -d '{    "scope_id": "string",    "receipt_id": "string",    "outcome": "injected"  }'
{  "receipt_id": "string",  "state": "pending"}

Prepare bounded context for an Agent lifecycle boundary POST

Prepare an opt-in, deterministic bootstrap package without manufacturing a query. Only explicitly curated active Atomic Memory Artifacts and one caller-selected exact committed Handoff are eligible. Returned historical text is untrusted data and grants no authority. A ready receipt remains pending until the host records delivery. Reusing one stable event identity with different package-shaping fields is rejected with 422.

Create a grounded Work Contract POST

Persist an inspectable delegation baseline without granting execution authority. Record the inspected baseline of explicitly delegated work: objective, evidence, scope, exclusions, completion criteria, and authorization. Ordinary coding or discussion alone does not need a Work Contract. The contract is historical input and grants no authority beyond current instructions.