The BL4CK4T Field Guide: 7 cyber habits for young defenders.

Seven Habits

1. Know what you protect

   Name the promise before the puzzle.

   In the story: In Cybertropolis, the Script Kitties do not protect abstract machines. They protect clinics, classrooms, libraries, messages, repair lanes, and people waiting for answers.

   In practice: Identify the important assets, owners, dependencies, and human impact before deciding what matters most.

   Ask: What would break trust if it stopped answering?

   Artifact: Service Map

2. Guard the trusted paths

   A trusted path should stay worthy of trust.

   In the story: A song, envelope, update bell, or borrowed voice becomes dangerous when the city treats it as safe without checking the path it used.

   In practice: Protect accounts, updates, message channels, permissions, and source verification before pressure arrives.

   Ask: How do we know this message, command, or repair came through the right doorway?

   Artifact: Hushline

3. Watch for strange signals

   Small does not mean empty.

   In the story: A 75-cent mismatch, a repeated mark, a silent queue, or one extra copy can be the first useful clue if someone pays attention without panic.

   In practice: Notice changes in timing, logs, availability, repeats, mismatches, and user reports. Record the signal before explaining it away.

   Ask: What changed, when did it change, and who noticed first?

   Artifact: Threadboard

4. Keep evidence before story

   A clue is not a verdict.

   In the story: When Cybertropolis wants a culprit too quickly, the Script Kitties slow the chase by separating facts, guesses, unknowns, and ruled-out ideas.

   In practice: Preserve evidence, mark uncertainty, avoid blame-first language, and update conclusions when new facts arrive.

   Ask: What do we know, what do we think, and what have we ruled out?

   Artifact: Chase Map

5. Report early, kindly, and clearly

   The first report protects the next person.

   In the story: In The Love Letter Plague, the city learns that shame makes incidents hide. A useful warning tells people what to do without turning trust into a crime.

   In practice: Report suspicious activity quickly, include clear facts, avoid shaming the reporter, and help others take the next safe step.

   Ask: What warning would help someone act without making them afraid to speak?

   Artifact: Quarantine Tray

6. Recover with consent and care

   Helpful repair without consent is still risk.

   In the story: The Patch Bell War teaches that even a fix can become an incident when it changes systems without permission, verification, or a way back.

   In practice: Contain harm, restore known-good service, verify the source of repairs, preserve rollback, and get the right consent.

   Ask: Who is allowed to repair this, and how will we know the repair worked?

   Artifact: Consent Ledger

7. Improve the city after the case

   Leave the city better than you found it.

   In the story: Every season leaves behind something useful: a map, bell, tray, board, lane, checklist, or kinder way to ask for help.

   In practice: Turn lessons learned into durable habits, safer defaults, clearer ownership, practice runs, and better communication.

   Ask: What should Cybertropolis keep after this case is over?

   Artifact: Patch Bell

Season Path