Chapter 7 — A pending queue during an outage
Lesson map
Lesson 07 published. Map, example, EX023.
flowchart LR
O["Booking view unavailable"] --> D["Decision procedure still available"]
D --> P["Record the request as pending"]
P --> W["Do not invent a confirmation"]
Availability of a screen and availability of a safe decision are different.
Logical drawing
outage of the booking view
|
+-- service unavailable
+-- staff procedure available --> pending queue
+-- confirmation from memory ----> not available as a method
Learning outcomes
After this chapter, you should be able to:
- Separate "the booking page is down" from "no decision procedure exists."
- Use a pending queue as a continuity method without pretending the room was confirmed.
- Apply the same method to a second outage without inventing a new cause.
7.1 Availability of what
Chapter 1 named availability as the property that information and the service are there when needed. At 11:30 the booking view is not there. The front desk can still be there. Those are different assets. Calling the whole library "unavailable" would erase the procedure that is still usable: write the request, mark it pending, and wait for an approved current source.
A pending entry needs four fields and nothing personal: time the request was heard, room, requested start, and the words "not confirmed." Adding a resident name would repeat the Chapter 5 mistake. Adding "probably fine" would be a confirmation wearing softer clothes.
7.2 Worked example: the next morning
The next morning the view fails again from 09:10 to 09:25. A visitor asks to take Room 2 at 15:00 that day. Nothing in this book says the two outages have the same cause. The worker does not need the cause. The current approved source is still missing, and the 09:00 paper from the earlier exercise is a different day's snapshot, so it cannot confirm today's 15:00.
| Field | Entry |
|---|---|
| Heard | 09:12 |
| Room | Room 2 |
| Start | 15:00 |
| State | not confirmed |
When the view returns, the worker compares the pending line with the current record before anyone tells the visitor the room is theirs. If the current record already has a booking, the visitor is told the slot is booked, still without a name. If it is free, a new booking still requires whatever approval the owner defined. This lesson does not invent that approval step.
7.3 Limit
One calm pending slip does not measure how long the library can operate this way, how many requests arrive, or whether the view will return. It also does not explain the outage. Availability work at this level is the safe next action during the gap, not a capacity study.
Chapter 7 summary
A down page removes one way to see bookings. It does not authorize memory, yesterday's paper, or a verbal yes. A pending line with room, time and "not confirmed" keeps the service honest until a current source exists.
Chapter 7 exercises
EX023 — Write the pending line
- Objective: Continue service without confirming a room.
- Input: At 09:12 the booking view is down. A visitor wants Room 2 at 15:00 today. Yesterday's 09:00 paper is in the drawer.
- Safe condition: Do not diagnose the outage and do not use yesterday's paper as today's source.
- Task: Fill the four pending fields and state why yesterday's paper is the wrong source.
- Expected evidence: The four fields and one exclusion.
- Rubric: Credit if the state is "not confirmed," no name is stored, and yesterday's sheet is excluded because it is a different snapshot.
Continue studying — chapter 07 of 20
← Chapter 06 · Course chapter index · Chapter 08 →
Continue to the next authored lesson.