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

## Chapter 17 — Monday is not Friday

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

Lesson 17. Map, example, EX063.

```mermaid
flowchart TD
  M["Monday: read and log"] --> T["Tuesday: check logs"]
  T --> W["Wednesday: warn if needed"]
  W --> F["Friday: feedback and update the log"]
  F --> Q{"Is the monthly paragraph a fifth weekday?"}
  Q -->|No| K["The chair added a month, not a day"]
```

Four weekdays are the routine. Thursday is not one of them. The month is a separate ask.

### Logical drawing

```text
weekdays in the routine
  Monday
  Tuesday
  Wednesday
  Friday
not in the routine
  Thursday
added beside it
  a monthly paragraph for the chair
```
<!-- open-cyber-academy:lesson-figures:end ch-17 -->

### Learning outcomes

After this chapter, you should be able to:

1. Name the four routine days and their jobs.
2. Leave Thursday out.
3. Keep the monthly paragraph off the weekday list.

### 17.1 Each day has one job. The script has none of the days.

Monday is for reading CCC and the advisories and for logging items. Tuesday is for checking mail and sign-in logs against indicators already in hand. Wednesday is for warning volunteers when the check gives a reason. Friday is for feedback to CCC and for updating the log. Thursday is not assigned. A routine that "fills Thursday so the week looks full" has invented a day Sam did not write.

The chair asked for a monthly one-paragraph summary. Sam adds that ask to the routine. A month is not a fifth weekday, and it does not move Friday's feedback. Deputies are meant to be able to run the written rhythm, and one observed run is logged before leave. This book does not print the date of that run, so a note cannot invent one.

Neither lab prints a weekday. `lab_sources.py` prints dependencies. `lab_rapid.py` prints an invalid value, a length, hits, and a community list. A line such as `Monday: donate-elmfield.example` would be a fusion. The days stay on the scope page. The values stay in the fixture.

| Day | Job |
|---|---|
| Monday | Read and log |
| Tuesday | Check logs |
| Wednesday | Warn if needed |
| Friday | Feedback and update the log |
| Thursday | Not in the routine |

### 17.2 Worked example

| Offered calendar | Fit | Decision |
|---|---|---|
| "Monday, Tuesday, Wednesday, Friday, with those four jobs." | The routine | Keep |
| "A monthly paragraph sits beside the week." | The chair's ask | Keep |
| "Thursday is indicator-hunting day." | Not written | Refuse |
| "The lab print is dated Monday." | No weekday column | Refuse |

> **Synthetic case.** The rhythm is written for EFBN deputies.

### Errors and limits

Do not invent Thursday in order to make a seven-name week.

### Apply

- **EX063 — Four days.** Which days are in the weekly routine, and what did the chair add that is not a weekday? *Rubric:* 3 = Monday read and log, Tuesday check logs, Wednesday warn, Friday feedback; Thursday is absent; the chair added a monthly paragraph; neither lab prints a day;; 2 = the four days and a separate monthly ask;; 1 = one day;; 0 = none.

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

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

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

## Worked answers

<a id="answer-ex063"></a>
**EX063.** Monday is read and log, Tuesday is check logs, Wednesday is warn, and Friday is feedback. Thursday is absent. The chair added a monthly paragraph. Neither lab prints a day.