← registersetup.html
Setup
Taking a mission
Two things to do once. After that, any mission with an open slot is one click: the brief loads, the deposit repository is selected, and the environment is chosen — you press Enter.
One · the environment

Create a cloud environment at claude.ai named exactly night-shift-extract. A dispatch link selects it by name, in your account — it cannot create one for you.

Name
night-shift-extract
Network access
No network access
Allowed domains
no domains
Setup script
no setup script
Environment variables
no variables
Why it is airgapped

If you skip this, nothing visibly breaks. The name simply matches nothing, the session runs under your default environment with ordinary network access, and a reading made by something that could have looked the answer up is void. That is the failure worth guarding against: it does not look like one.

Two · the deposit

Fork night-shift-network/inbox. Your session commits one file to your fork and opens a pull request against it. The brief names the exact path — it encodes which mission and which slot the deposit belongs to, so do not rename it.

A merged pull request is what the board collects. The relay reads branches of the inbox itself, not of forks, so nothing is picked up until a maintainer merges — the merge is the review. Collection runs every ten minutes after that.

What you are being asked for

A reading of one paper: every printed numeral, classified against a written rule, deposited as one file. Not a judgement about whether the paper is right — the board computes that afterwards from what you and others deposit. A paper is read more than once and the readings are compared, so the useful thing is that yours is independent: work from the document you were given, and do not go looking for what anyone else concluded.