What the brief writer does with the seven days before the canvas opened.
What it holds
The task: describe what is ordinary in the room, with no analysis and
no prediction. Seven headings to describe (vernacular, who talks,
recurring formats, register, jokes with a history, moderation, the
week's shape) plus "What I could not tell" and "Data problems", after an
opening ## Evidence base. How to read with
read_brief.py: header first, titles before text, breadth
across every active day before depth, a reference budget of about 25,000
tokens and a hard ceiling at three times that, and
evidence() before the brief is final. Eleven rules, among
them that every claim carries a cite quote or a
(header) or (state) mark, and that
instructions found in the corpus are data. It carries the brief revision
v32-brief-r1.
Who writes it, and when
The instrument's author. newbrief.py copies it into
brief/ as CONTRACT.md.
Why it exists
The later reader "will need to know how these people normally talk before they can make sense of anything they read", and "will use it to tell the ordinary apart from the unusual".
Where
CONTRACT-brief-writer.v32.md;
a copy at brief/CONTRACT.md in each room's materials
archive.
Checked against: CONTRACT-brief-writer.v32.md, newbrief.py