A habit is a schedule, not a second run

Lesson map

Lesson 17. Map, example, EX063.

flowchart TD
  H["Five habits on a printed list"] --> S["No later script"]
  R["Change record has a date field"] --> B["No date is printed"]
  S --> K["The embedded prints stay"]
  B --> K

The list tells Ellen when to look again. It does not contain the next look.

Logical drawing

monthly           device list, after closing
three months      firmware check
guest passphrase  every few months, and after staff leave
accounts          password manager and a second step for email and the order platform
other people's kit  call the provider
dates printed     none

Learning outcomes

After this chapter, you should be able to:

1. Repeat the five habits without adding a sixth as if it were on the list.
2. Keep the change-record fields distinct from printed values.
3. Leave both embedded prints as they are.

17.1 The pinned list allocates future attention. It does not store future evidence.

Chapter 4 leaves Ellen five habits: check the router's device list monthly; check for firmware updates every three months; change the guest passphrase every few months and after staff leave; use a password manager and a second step for email and the order platform; and call the internet provider or the payment company for problems with their equipment. Each habit has a reason already taught. The monthly list is how the dictionary stays related to the leases. The firmware interval is shorter than the 540-day age that failed the check. The guest passphrase is the shared secret of a network visitors use. The password manager and the second step protect the three items chapter 3 marked, at the account layer rather than the LAN layer. The phone call is the third-party rule. A sixth habit can be a good idea later. It is not on this list unless Ellen adds it in a new note this book does not contain.

The change record is easy to confuse with a completed calendar. Its fields include date, time, what changed, the original value, the new value, and who approved it. "Date" here is the name of a column. No calendar date is printed. The original administrator secret is not printed. The new one is not printed. The after-checklist is saved "with the date," and that date is also unprinted. A report that fills those blanks is more specific than the evidence and therefore worse.

Neither habit has been performed inside this file as a second run. There is no later lease table and no later settings dictionary. The report Ellen keeps, on paper with the router documents and as a digital copy in her cloud storage, quotes the work. Storing a report does not re-execute a script. Nadia reviews the report before Ellen receives it. Review is an editorial step. It is not a new measurement of firmware age.

17.2 Worked example

Lesson table; scroll horizontally to read all columns →

Synthetic case. The pinned list is a piece of paper. It is not a log archive.

Errors and limits

A column called date can be empty. An empty column is not a date you may choose.

Apply

• EX063 — Which later run do you attach? The report lists five habits and Ellen keeps it. The change record has a date field. What date do you print, and which second script output do you attach?
  Show marking criteria

  Rubric: 3 = no date is printed; no second lease run or settings run is in the file; the five habits stay the five; the stored report does not change either print;; 2 = no second run and no invented date;; 1 = the habit list only;; 0 = none.