Message examples and traces

Select a message to inspect its complete CloudEvents JSON. These examples cover all 14 core types in draft-01.

Messagedasp.v1.session.opendasp.v1.session.openeddasp.v1.commanddasp.v1.receiptdasp.v1.update · command.accepteddasp.v1.update · applicationdasp.v1.update · command.outcomedasp.v1.progressdasp.v1.view.readdasp.v1.viewdasp.v1.updates.readdasp.v1.updatesdasp.v1.outcome.readdasp.v1.outcomedasp.v1.resync.requireddasp.v1.failure

CloudEvents ⓘ: what is this message format?

CloudEvents is an open, widely used standard for event messages. DASP uses its common envelope for event identity, source, type, and data. DASP adds the session and recovery rules.

Why DASP uses CloudEvents →

{
  "specversion": "1.0",
  "id": "event-3",
  "source": "urn:example:client:one",
  "type": "dasp.v1.command",
  "datacontenttype": "application/json",
  "data": {
    "session_id": "session-counter",
    "command_id": "command-add-1",
    "name": "counter.add",
    "input": {
      "amount": 3
    }
  },
  "requestid": "request-add"
}

Download the evidence

Artifact	Contents
Counter event set	Full examples of every core type
Counter profile	Commands, state, outputs, and completion rules
Recovery trace	Lost receipt, equal retry, conflict, and two client cursors
WebSocket delivery transcripts	Normal live delivery, fixed-boundary reconnect, and resync with a late cancelled-read reply
Capability-discovery flow	Complete list, detail, exact resource-read, and release controls
Capability-discovery scale fixture	Paging, limits, profile identity, schema resources, connection loss, and 1,000 generated capabilities
Compound input schema	Full JSON Schema 2020-12 resource with references to shared and Boolean resources
Signed authority grants	Reusable and exact-command grants, complete core command, original signature bytes, and invalid grant shapes using a public test key
Authority decision traces	Many admissions across sessions, scope failures, expired/revoked retries, optional budgets, and direct approval; no host execution
Invalid events	Messages rejected by validation
Encrypted carrier	Synthetic carrier shapes; no valid cryptography
Encrypted raw headers	Exact integer tokens, Unicode, and duplicate header keys; no setup or cryptography

The event set is a catalog. The recovery trace is ordered. Both are recorded artifacts, not a live host.

Follow the trace or run the checks.