> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/code-directory/cd.ews.04-message_type.md).

# CD.EWS.04 message\_type

Indicates the type of CAP message being sent.

**Reference:** CAP v1.2 Section 6.1.2

<table><thead><tr><th width="168.2672119140625">Code</th><th>Description</th></tr></thead><tbody><tr><td>Alert</td><td>Initial or primary alert message.</td></tr><tr><td>Update</td><td>Updates or corrects an earlier alert.</td></tr><tr><td>Cancel</td><td>Cancels a previous alert.</td></tr><tr><td>Ack</td><td>Acknowledges receipt of a previous alert.</td></tr><tr><td>Error</td><td>Indicates an error in a previously sent alert.</td></tr></tbody></table>

{% hint style="info" %}

While `msgType=Cancel` exists, an upstream alert cancellation cannot automatically reverse a downstream financial or operational action once the Social Protection (SP) system has approved or executed a response. Implementations must handle cancellations across three distinct phases and explicitly declare their technical and operational **point of no return**:

* **Void Before Approval:** If a cancellation arrives before formal SP approval, the pending activation is immediately voided and halted.
* **Escalate After Approval (Pre-Execution):** If a cancellation arrives after approval but before resource distribution, the system must freeze the execution queue and immediately escalate the event to human operators for manual intervention.
* **Record Post-Execution (No Automatic Reversal):** If a cancellation arrives after aid is executed, the transaction remains an immutable historical fact. The event must be logged as a "false activation" or "cancelled activation" for audit purposes, without implying automated financial reversals or clawbacks.
* **Declaration Requirement:** Implementations are normatively required to document their specific **point of no return**—the exact structural milestone where a message cancellation can no longer halt resource execution.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/code-directory/cd.ews.04-message_type.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.