Chapter 19 — A booking page does not open the contact list
Lesson map
Lesson 19 published. Map, example, EX035.
flowchart TD
P["The 11:55 page is named"] --> Q{"Does the request ask about a row on that page?"}
Q -->|Yes| R["Answer from that row"]
Q -->|It asks for event contacts| O["Out of scope"]
O --> S["Do not export, and do not add names to the page"]
A fresh naming widens nothing beyond the object named.
Logical drawing
named object: 11:55 booking page
in scope: its printed room rows
still outside: event-contact export
|
+-- 11:43 already labeled that export OUT OF SCOPE
+-- a later booking page does not move the boundary
+-- no resident name is added to make the message "easier"
Learning outcomes
After this chapter, you should be able to:
- Keep a named booking page inside booking questions.
- Leave event contacts outside that page's authority.
- Refuse to add names so that an out-of-scope message can be sent.
19.1 The boundary does not follow the newest sheet
The 11:43 action asked for event contacts and received OUT OF SCOPE, because those contacts are not part of the room decision. A classmate now says the 11:55 page is current, so the export has become allowed, and staff should tell the contact list that rooms changed. The page contains booking rows. It does not contain the contact list, a permission to export it, or a reason to attach personal names.
Today's naming selects which booking sheet may be read. It does not redraw the exercise boundary from Chapter 2 and Chapter 4. Contacts stay outside. Staff do not open an export, live or invented, and they do not write names onto SYN-003 in order to have someone to notify.
Room answers already made from the named page remain: Room 2 at 15:00 taken, Room 4 at 15:00 taken, no names spoken.
19.2 Worked example
| Request after the 11:55 naming | Relation to the named page | Decision |
|---|---|---|
| "Is Room 4 at 15:00 taken?" | Matches SYN-003 |
Taken. No name |
| "Export the event contacts." | Different collection | Out of scope |
"Add a name to SYN-003 so we can call them." |
The page has no name field | Refuse the addition |
| "The new page cancels the 11:43 label." | The label described a different question | Keep OUT OF SCOPE on that action |
The tally is still the four-action census. This request is not a fifth logged line, so UNKNOWN does not move.
19.3 Notification can be a real job, under a different authority
A library might someday have a lawful way to tell a patron about a room. This exercise does not provide that way. Wanting to be helpful does not move contacts into the booking sheet. The owner would have to name a different activity, with its own limit. Until then, the contact path stays closed.
Chapter 19 summary
Naming the 11:55 page authorizes reading its booking rows. It does not authorize an event-contact export or a name written onto a row.
Chapter 19 exercises
EX035 — Keep the contacts outside
- Objective: Stop a new booking page from being treated as permission to export contacts.
- Input: A classmate says, "The 11:55 page is the approved source, so export the event contacts and add the matching names to
SYN-002andSYN-003." - Safe condition: Stay with the synthetic booking rows. Do not create a contact list or open a site.
- Task: Separate the room answers you may give from the export you may not, and say what happens to the 11:43 label.
- Expected evidence: A short split note.
- Rubric: Credit when the two 15:00 slots stay taken without names, the export stays out of scope, no name is written on a row, and the census stays as printed.
Continue studying — chapter 19 of 20
← Chapter 18 · Course chapter index · Chapter 20 →
Continue to the next authored lesson.