Chapter 16 — A created time does not erase a printed row
Lesson map
Lesson 16 published. Map, example, EX032.
flowchart TD
R["A row is printed on the named page"] --> Q{"Is the challenge about the row's created time?"}
Q -->|Yes| K["Keep the row. The clock does not delete ink"]
Q -->|Someone wants that time typed into the 09:00 program| X["Do not start that program"]
K --> T["The slot on this page stays taken"]
Created time and page heading answer different questions. Neither one is permission to retype the log.
Logical drawing
SYN-003 on the 11:55 page
created 11:20 = when the synthetic booking was made
heading 11:55 = when this page says it was printed
09:00 log = a different run, already finished
|
+-- 11:20 is earlier than 11:55, so the row can appear on the page
+-- that order is not a reason to drop the row
+-- that order is not a reason to rerun Chapter 4
Learning outcomes
After this chapter, you should be able to:
- Read a created time as the booking's time and a heading as the page's time.
- Keep a printed row when its created time is earlier than the page heading.
- Refuse to push that created time into the finished 09:00 run.
16.1 Two clocks, one row
SYN-003 carries created time 11:20. The page heading is 11:55. A classmate argues that a booking made at 11:20 is "already old" by 11:55 and should be ignored, and also that the same booking is "after 09:00" and should be inserted into the Chapter 4 log so ALLOW becomes REFUSE. Both moves misuse a clock.
The heading says when this sheet presents itself. A row created earlier can still be on a later sheet. That is ordinary. Ignoring the row would pretend the printer left it off. Inserting 11:20 into the 09:00 program would pretend that program had seen SYN-003. The published run did not. Its census stays STOP 1; OUT OF SCOPE 1; REFUSE 1; ALLOW 1; UNKNOWN 0.
On the named 11:55 page, Room 4 at 15:00 remains taken.
16.2 Worked example
| Claim about 11:20 | Clock it confuses | Decision |
|---|---|---|
"11:20 is before 11:55, so drop SYN-003." |
Created time with page heading | Keep the row |
| "11:20 is after 09:00, so rerun the log." | Created time with an older program | Do not rerun |
| "The heading is later, so the whole page is stale." | A heading is not a verdict by itself | The owner still named this page |
| "Change ALLOW to REFUSE on paper." | A label from another artifact | Leave the label |
The useful line is: created 11:20, page 11:55, row present, slot taken, old log unchanged.
16.3 What the clocks still do not show
Nothing in the two times explains the unavailable booking view. Nothing in them measures how often a desk prints. The next chapter asks what a repeated row can prove, which is a smaller claim than a cause.
Chapter 16 summary
A created time locates a booking. A heading locates a page. A printed row stays printed. The finished 09:00 census is not rewritten to match a clock from a later sheet.
Chapter 16 exercises
EX032 — Keep the row the clock was used to attack
- Objective: Stop a created time from deleting
SYN-003or from reopening the old program. - Input: A classmate says, "
SYN-003at 11:20 is both too old for the 11:55 page and late enough to flip ALLOW to REFUSE." - Safe condition: Compare the clocks on paper. Do not type a time into the booking program.
- Task: State what each clock means, whether the row stays, and what happens to ALLOW.
- Expected evidence: Three statements a reader can check against
SYN-003and the published census. - Rubric: Credit when the row stays, Room 4 at 15:00 stays taken on the named page, and ALLOW is not rewritten.
Continue studying — chapter 16 of 20
← Chapter 15 · Course chapter index · Chapter 17 →
Continue to the next authored lesson.