Chapter 17 — Matching rows are not a cause
Lesson map
Lesson 17 published. Map, example, EX033.
flowchart TD
M["SYN-002 appears on two later pages"] --> W["The exercise printed that row twice"]
W --> N["The outage cause is still unrecorded"]
N --> R["Do not call the match an attack, a vulnerability, or proof of safety"]
Agreement of one synthetic row is a comparison of pages. It is not a diagnosis.
Logical drawing
11:40 page: SYN-002 Room 2 15:00
11:55 page: SYN-002 Room 2 15:00
|
+-- supported: both sheets show that row
+-- not supported: why the booking view failed
+-- not supported: an attack occurred
+-- not supported: the library is safe because the rows match
Learning outcomes
After this chapter, you should be able to:
- State the limited fact when the same synthetic row is on two pages.
- Refuse to promote that fact into an attack, a vulnerability, or an incident.
- Leave Chapter 8's class, a weak confirmation procedure, where it was.
17.1 What the repeat can carry
Put the 11:40 page beside the 11:55 page. SYN-002 is on both, with the same room, start, created time, and confirmed status. The careful sentence is that this exercise printed that row on two later sheets. The 11:55 page also has SYN-003, which the earlier sheet lacks. Sameness and difference can both be listed. Neither list contains a cause for the unavailable view.
Chapter 8 already refused to call the stale-paper habit a proven software weakness or an incident. A second copy of SYN-002 does not add the missing demonstration. It does not add an owner's incident declaration. A classmate's word "attack" is a new claim with no new evidence. A classmate's word "safe," drawn from the match, is the opposite overclaim. Matching rows do not measure harm or likelihood, so they also do not revive the score rejected in Chapter 9.
17.2 Worked example
| Sentence offered for the pair of pages | Evidence it would need | Decision |
|---|---|---|
"Both later pages show SYN-002 for Room 2 at 15:00." |
The two sheets | Keep |
| "The match shows the outage was an attack." | A demonstrated hostile action | Reject |
| "The match shows a vulnerability in the booking site." | A demonstrated weakness | Reject |
| "The match shows the library is safe." | An evaluation this exercise did not perform | Reject |
| "Raise the tally's UNKNOWN, because the cause is unknown." | UNKNOWN counts unmatched log actions | Reject. The cause was never one of the four actions |
The class of the exercise problem stays a weak confirmation procedure. The census stays the census of the 09:00 log.
17.3 The open cause
Staff can still write "cause not established" under the comparison. That phrase blocks a false ending. It does not assign blame, and it does not authorize a live investigation. The following chapter is about whether the older sheets may be destroyed once a newer sheet exists.
Chapter 17 summary
Two pages that share SYN-002 support that shared row and nothing causal. The outage stays unexplained. The older labels of procedure, tally, and score stay in their earlier lessons.
Chapter 17 exercises
EX033 — Take the diagnosis off the matching row
- Objective: Keep a repeated synthetic row from becoming an attack story or a safety claim.
- Input: A classmate writes, "The pages agree on
SYN-002, therefore the outage was an attack and the exercise can close as safe." - Safe condition: Compare the two synthetic pages. Do not investigate a real site.
- Task: Replace the note with the fact the pages support, the two claims you reject, and the class Chapter 8 already allowed.
- Expected evidence: Four sentences a reader can check against the pages and Chapters 8 and 9.
- Rubric: Credit when the shared row is stated, attack and safety are both refused, the procedure class is unchanged, and the census is unchanged.
Continue studying — chapter 17 of 20
← Chapter 16 · Course chapter index · Chapter 18 →
Continue to the next authored lesson.