2. Open the coding handler

Open a second Codex or Claude chat in your study's working folder. Name it Coding handler and attach HANDOFF-collection.md from the first chat. Paste:

You are the coding handler for my r/place study. Use the existing handler in the research repository Read FOR-AGENTS.md, coder/FOR-AGENTS.md, coder/handler/CONTRACT-scheduler.md and coder/README.md before operating anything.

Read HANDOFF-collection.md. Obtain any missing instrument folders, record their version, and prepare a separate working yard using the documented folder layout. Check the inputs, model access and native launcher, run the prescribed self-tests, then follow the existing scheduler contract. Keep progress on disk and preserve the required community-coder closes. Hand checked outputs and their provenance to the aggregator handler. Do not replace the existing protocol or use shipped example rooms as my new run.

The coding handler already exists, and this prompt opens it under its own protocol. A Claude chat can coordinate it, but the shipped launcher for persistent community coders requires Codex.

This step starts from a prepared community record and the community coder contract. The community coder codes the material, with fleet coders in communities above 500 items, and brings the codes, themes and case account together under the authors' supervision. At the close, keep the community coder's conversation, files and runtime provenance together, with the declared coding outputs and the evidence trail. Move on when the community coder's checks pass and its outputs and close are stored.

A coding close, a local model (R6), a return to the population model and a later re-check are separate milestones. The checkpoint catalog records which of them are saved.

A return resumes the saved community coder, which compares the population model with its community's record. The original participants are not asked.

Run the Field agent and the local models (R6) as their own workflows, under their own contracts, when your instrument requires them; the v32 coding handler does not include them. The aggregator handler names any required Field package before it starts the stage that uses it.

Open the next chat

Give the aggregator handler the coding handler's checked output paths, census, versions and close records. It checks its own required inputs before it builds a new run. Keep the coding chat open for returns and repairs.

Documents for this handler

• Coder README: the exact platform and folder requirements.
• Community coder contract: what each community coder does, step by step.
• Community coder and fleet coder: the two coders' own instructions.
• Return instructions: how a saved community coder answers the population model.
• Agent reading key: what the handler must read, in order.
• Checkpoint catalog: which coding closes, local models, returns and re-checks are saved.