Prepare bounded context for an Agent lifecycle boundary

POST
/v1/context/bootstrap

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.

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/context/bootstrap" \  -H "Content-Type: application/json" \  -d '{    "scope_id": "string",    "lifecycle": "startup",    "integration": "string"  }'
{  "schema": "powercontext.bootstrap-context.v1",  "status": "ready",  "reason": "disabled",  "profile": "powercontext.scope-bootstrap.v1",  "content": "string",  "content_bytes": 0,  "package_digest": "string",  "items": [    {      "kind": "atomic-memory",      "scope_id": "string",      "artifact": {        "family": "string",        "artifact_id": "string",        "revision": 1      },      "content_digest": "string",      "truncated": true    }  ],  "truncated": true,  "receipt": {    "receipt_id": "string",    "state": "pending"  }}

Prepare bounded context for an Agent turn POST

Prepare final, ephemeral context from Runtime-owned sources without persisting or injecting it. Retrieve bounded, query-specific PowerContext when additional assembled context is needed. Automatic recall already attempts this on supported lifecycle events; do not repeat it routinely or to satisfy an explicit save. A returned context value is not proof of host injection. Empty context is normal; use only the evidence actually returned.

Record a bootstrap delivery outcome POST

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.