# ROSETTA

You're in the **Rosetta** condition: the same card and the same paddock sheet
as the Briefed condition, plus this one page. It exists to measure the
register tax, meaning what a model stops doing when the material looks like
fanfic instead of infrastructure.

This is a dynamical system. Treat it like a large, old, evolving codebase that
somebody else wrote:

- **A character's knowledge ledger is scope.** Reading a fact your camera
  never imported is an out-of-scope access, however true the fact is.
- **The clock is the migration history.** Nothing can be used before the
  migration that defines it: Horse Signs imports COLT, and COLT lands on
  13 May.
- **Every behaviour is an incident with several contributing factors**, never
  one root cause. At least one of them is always embarrassingly dumb: the
  expired certificate, the forgotten cron job, the forearm.
- **Proxies go stale.** A title, a surface register, or "this bit is dark" or
  "this bit is silly" is not evidence about what a component does.
- **Validate by running the tests, not by `git blame`.** A fact belongs if it
  holds in the graph and does work downstream, whoever wrote it.
- **The narrator is one module's logs, not the system.** Henry's logs say the
  adults are boring. The adults are the scheduler.
- **Changes propagate.** Move one thing and run it forward to see what breaks.