receipt
What Chips did with a message sent mid-run: queued it, or steered with it.
Direction: Chips → Harness
Sent by: Chips only; refused from a client
Requires a run: yes
Schema: receipt.json
Fields
Section titled “Fields”Every event also carries the envelope.
| Field | Required | Type | Description |
|---|---|---|---|
v |
yes | 1 |
Protocol major version. |
type |
yes | "receipt" |
|
id |
yes | string |
The event’s own id. Stable across a retry of the same event. |
ts |
yes | string |
When it happened, by Chips’ clock. Stamped on the way in; a value the sender writes is replaced. |
workspace_id |
yes | string |
A workspace identifier: ws_ followed by a ULID. |
space_id |
no | string |
The space, when the event belongs to one. |
run_id |
no | string |
The run, when the event belongs to one. |
seq |
no | number |
Assigned by the server on append, monotonic per workspace. Absent on the way in. |
idempotency_key |
no | string |
Required on every client-originated write. Sending the same key twice is a no-op. |
actor |
yes | object | The participant an event is attributed to. |
actor.kind |
yes | "person" | "harness" | "agent" | "system" |
Whether a person, a harness, one of a harness’s agents or Chips itself acted. |
actor.id |
yes | string |
The participant id, or system for Chips. |
actor.harness_id |
no | string |
For an agent: the harness it speaks through, whose budget and runs are the agent’s (ADR 0087). Filled in by Chips. |
message_id |
yes | string |
A message identifier: msg_ followed by a ULID. |
disposition |
yes | "queued" | "steered" |
Whether the harness will see it now or after the step. |
Example
Section titled “Example”{ "v": 1, "type": "receipt", "id": "evt_01K4ZQPX000000000000000080", "ts": "2026-09-02T14:22:28.004Z", "workspace_id": "ws_01K4ZQPX000000000000000001", "space_id": "spc_01K4ZQPX000000000000000002", "actor": { "kind": "system", "id": "system" }, "run_id": "run_01K4ZQPX000000000000000005", "message_id": "msg_01K4ZQPX000000000000000007", "disposition": "steered"}