Path 1 · 9 steps
Representation Forensics
Learn to separate what a human sees from what software can recover across Unicode, DOM structure, metadata, and controlled transformations.
Trace a suspicious artifact across representation layers and describe the exact differential without confusing appearance with machine-readable state.
-
What Is Machine-Readable Hidden Text?
Establish the core distinction between rendered appearance and machine-readable representation before inspecting individual carrier families.
-
CASE 002 — Between the Characters
Inspect a Unicode carrier where apparently ordinary text contains code points a visual read can miss.
-
What Is Invisible Unicode?
Name the Unicode mechanisms behind the previous case and connect them to code-point inspection and normalization sensitivity.
-
Unicode
Consolidate the Unicode carrier family before moving into parsed document structure.
-
How Can HTML Hide Text?
Shift from character representation to parsed structure and learn where source, DOM, and presentation can diverge.
-
CASE 006 — Attribute Echo
Practice recovering machine-readable information from HTML attributes rather than visible body text.
-
What Is Hidden Information in Metadata?
Extend the same representation discipline to descriptive fields that sit outside an artifact's primary visible content.
-
CASE 010 — Head Trace
Apply metadata inspection to a concrete case and distinguish descriptive machine-readable fields from rendered content.
-
Normalization
Finish by treating normalization as a controlled representation change rather than a vague cleanup operation.