> 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.03-status.md).

# CD.EWS.03 status

Specifies the current operational status of the alert message.\
**Reference:** CAP v1.2 Section 6.1.1

<table><thead><tr><th width="168.2672119140625">Code</th><th>Description</th></tr></thead><tbody><tr><td>Actual</td><td>The alert message pertains to a real-world event.</td></tr><tr><td>Exercise</td><td>The alert is part of a drill or test exercise.</td></tr><tr><td>System</td><td>The alert was generated by an automated system.</td></tr><tr><td>Test</td><td>The alert is a system test and not for operational use.</td></tr><tr><td>Draft</td><td>The alert is a draft and not yet released for dissemination.</td></tr></tbody></table>

{% hint style="info" %}
To ensure safe conformance testing and prevent accidental aid distribution, implementing systems must enforce strict, normative behaviors based on the message status.

Operation Action Limit: only payload marked with **`status=Actual`**  may drive programmatic actions, allocate budgets, or trigger resource execution.

Handling of Test/Exercise messages: Those message should be accepted, validated, and logged for audit purposes
{% 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.03-status.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.