GUIDE// analyst protocol

/field-guide

The opening should be legible before it becomes difficult.

guidance / spoiler-light

This site is designed for careful reading, not technical exploitation.

Start from /root/, compare timestamps, and notice which states sound too polished. If you become stuck later, return to the clue rails rather than guessing random URLs.

/notes

Accessibility and fallback behavior

quiet clues / low certainty

The archive should remain readable even when features degrade.

  1. No puzzle JavaScript

    CSS handles directory reveals and the first unlock state.

  2. Legacy mode

    Browsers without :has() receive a linear disclosure path and an explicit banner.

  3. Readability first

    Background art is optional. The green-on-black terminal remains readable without it.

First-turn advice

Watch for two kinds of mismatch: wording that is too clean, and timestamps that are too late. The archive is trying to finish its own summary. Your job is to decide which contradictions deserve to remain visible.

What you will not need

You will not need browser exploits, source editing, or external tooling to begin. Later turns may reward curiosity, but the first unlock is grounded in plain reading.