<a id="ch-13"></a>

## Chapter 13 — The export and the exit plan are requests, not arrivals

<!-- open-cyber-academy:lesson-figures:start ch-13 -->
### Lesson map

Lesson 13. Map, example, EX059.

```mermaid
flowchart TD
  A["If the vendor stops, balances must still be honoured"] --> B["Elena asks for two protections"]
  B --> C["A monthly balance export"]
  B --> D["A contractual exit plan"]
  C --> E{"Is either one shown as received?"}
  D --> E
  E -->|No| F["Both stay requests"]
```

Asking is the step the file records. Receiving is a later step it does not record.

### Logical drawing

```text
need
    a copy of balances
    a way to honour points if the vendor stops
asked for
    monthly balance export
    contractual exit plan
not shown
    an export that arrived
    an exit plan that was signed
```
<!-- open-cyber-academy:lesson-figures:end ch-13 -->

### Learning outcomes

After this chapter, you should be able to:

1. Say why Elena asks for an export and an exit plan.
2. Keep both as requests.
3. Refuse to mark either one received.

### 13.1 The need explains the ask. It does not fill the inbox.

The points live on infrastructure the vendor runs. If that company stops trading, Copperleaf still has customers holding points and needs a copy of the balances plus a way to honour them. Elena therefore asks for a monthly balance export and a contractual exit plan. Chapter 4 then makes both items conditions of the pilot, beside the verified gap fixes and the rule that personal data stays off the ledger. A condition is a requirement the pilot depends on. It is not a document this manuscript attaches. No export file is described as received. No clause is described as signed. The monthly check she adds, comparing points issued with purchases, is her own looking. It is not the vendor's balance export arriving each month. Treating the request as an arrival would let the pilot condition look satisfied while the protection is still only a sentence. The concentration in the previous lesson is why the request matters. It is not evidence that the request has already been met.

### 13.2 Worked example

Keep the verb "asks" until the file uses a verb of receipt.

| Object | Verb the file uses | Decision |
|---|---|---|
| Monthly balance export | Asks for | Stays a request |
| Contractual exit plan | Asks for | Stays a request |
| "The export arrived this month." | No receipt | Refuse |
| "The exit plan is signed." | No signature | Refuse |

> **Synthetic case.** No spreadsheet of balances is included. The exit plan is not quoted because it has not been shown.

### Errors and limits

A wise request can still be outstanding. The pilot's condition names the protection. It does not prove the protection exists.

### Apply

- **EX059 — Asked or received?** Elena wants a monthly balance export and a contractual exit plan so points can still be honoured if the vendor stops. Which of those has the file shown as received? *Rubric:* 3 = both stay requests; neither a received export nor a signed exit plan is shown;; 2 = both are still only asked for;; 1 = one document;; 0 = none.

<!-- open-cyber-academy:chapter-navigation:start ch-13 -->
### Continue studying — lesson 13 (chapter 13 of 20)

[← Chapter 12](#ch-12) · [Course chapter index](../SUBJECTS.md) · [Chapter 14 →](#ch-14)

Continue to the next authored lesson.
<!-- open-cyber-academy:chapter-navigation:end -->

## Worked answers

<a id="answer-ex059"></a>
**EX059.** The monthly balance export and the contractual exit plan stay requests. Neither is shown as received.
