One week-match is not two lab hits | Rapid course Threat intelligence and OSINT

Lesson map

Lesson 15. Map, example, EX061.

flowchart TD
  W["First week: one match, one password change"] --> N["A notebook sentence"]
  L["Lab hits: two tuples"] --> P["A script print"]
  N --> Q{"Are the counts the same event?"}
  Q -->|No| K["Keep both numbers"]

The week and the lab are different pages. Their counts do not correct each other.

Logical drawing

week sentence
  3 logged
  1 match
  1 password changed
  1 GREEN feedback
lab print
  two hit tuples
  no password field

Learning outcomes

After this chapter, you should be able to:

Repeat the week's four counts.
Repeat the lab's two hit tuples.
Refuse a merge that turns one match into two, or two hits into a password.

15.1 The notebook counts a week. The script counts a fixture.

Sam's first full week is a sentence: three CCC items logged, one match found, one volunteer password changed, one GREEN feedback note sent. lab_rapid.py prints two hit tuples and no password. Nothing in the fixture says which of those tuples, if either, is the week's single match. Treating the week as a retelling of the lab makes 1 and 2 fight. They are different tallies, from different pages, and both stay.

The password change is also absent from the print. The lab has no account field and no secret. The week's "one password changed" is an action Sam recorded. It does not name the new password, and this chapter does not invent one. vol-07 may be asked, kindly, whether a click or an entered detail happened, and a change plus two-step login follows only if the answer is yes. That question is the case procedure. It is not a column beside the hit tuples.

The chair's monthly paragraph is a further addition to the routine. It is not a third hit and not a second password.

Lesson table; scroll horizontally to read all columns →

Count	Where it lives
3, 1, 1, 1	The week sentence
Two hit tuples	The lab print
A password value	Nowhere in either
A monthly paragraph	The chair's request, not a hit

15.2 Worked example

Lesson table; scroll horizontally to read all columns →

Offered sentence	What it mixes	Decision
"The week recorded one match. The lab printed two hits."	Both, kept apart	Keep
"No password appears in the fixture."	The script	Keep
"The two hits are the week's one match, counted twice."	A merge	Refuse
"The lab stored the new password."	No such field	Refuse

Synthetic case. The week and the fixture are both invented, and they are not the same tally.

Errors and limits

Do not average the two counts into a story that neither page told.

Apply

EX061 — Two tallies. What did the first week count, and what did the hit line count?
Show marking criteria
Rubric: 3 = the week counted 3 logged, 1 match, 1 password change, and 1 feedback; the lab counted two hit tuples and printed no password; the tallies stay separate;; 2 = one week-match and two lab hits, unmerged;; 1 = one number;; 0 = none.