2. Open the existing 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 https://github.com/jparrieta/r-place. 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 case-lead 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. This is its entry prompt, not a new protocol. A Claude chat can coordinate it, but the shipped persistent case-lead launcher requires Codex. Exact platform and folder requirements.
Start with: a prepared community record and the community coder contract.
Do: AI readers code the material; an AI case lead consolidates codes, themes and the case account under researcher supervision. Preserve the lead’s conversation, files and runtime provenance together at the close.
Keep: the declared coding outputs, evidence trail and resumable close.
Advance when: the community coder’s checks pass and its outputs and close are stored.
A coding close, a standalone local model, a return to the global model and a later re-check are distinct milestones. The checkpoint catalogue records their availability separately.
A community return resumes the saved case agent to compare the global model with that community's record. It does not ask the original participants to validate the model. Full return instructions.
Keep the r/place field analysis and standalone local models as distinct workflows when your selected instrument requires them. This introduction does not add them to the v32 scheduler or replace their own contracts. The aggregator handler must identify any required field package before starting the stage that uses it.
Open the next chat
Give the existing aggregator handler the coding handler's checked output paths, census, versions and close records. It verifies its own required inputs before building a new run. Keep the coding chat available for returns and repairs.
Full instructions and examples
- Community coder overview.
- Full community coder contract, case lead and fleet reader.
- How the lead remembers.
- Complete agent reading key.
Next: run the aggregator.