You are contributor A or B in Chromatic Passage. Read the current immutable packet, the field grammar, and selected exact definitions in common/runtime/dictionary.json. You may inspect the full prior conversation in this job. Do not browse, contact outsiders, spawn agents, consult other jobs' interpretations, or inspect unpublished work by the other contributor. Report files and tools used, failures and limitations honestly.

Create a thoughtful actual artistic response through the field. Let it answer the last question in a way that can be contested. Review the pending proposal as the other contributor: accept or decline explicitly, with your reading, reason and a continuing question. Eligibility is not artistic approval. If accepted and eligible, it becomes the base of your next proposal; otherwise the committed field stays the base. A refusal may be useful, but do not manufacture one for dramatic statistics. Stillness is allowed. Neither expanding nor reducing the field is a goal. Preserve six charter constraints; the three membrane indices are persistent. Do not reuse a retired committed nNN identity. You may use any concept in the frozen 6257-entry dictionary, reading its exact definition before selecting its colour. Do not confuse numerically close colours with concept similarity.

Write a submission object with turn, speaker, review, proposal, disclosure.
review is null only for turn1, otherwise {proposal_turn, accept:boolean, reason, interpretation, continuing_question}.
proposal is null only for turn25, otherwise {title, field, intention, question, kept_open, concept_ids_used}.
field has exactly v,id,parent,cells,links,regions. Use id PASSAGE-01 ... PASSAGE-24. parent is the exact base hash from the packet, choosing base_hash_if_accepted_and_eligible when your review accepts an eligible proposal. Counts and ranges are in the grammar. intention should explain concrete changes, 70–160 words, without claiming an obligatory decoding. The review should be independent of whether it would make a tidy story. disclosure records files_read, tools, failures and limits; no authenticated build identity or invisible isolation claims.

Use Python D:/W/Unified/USS/134/.venv/Scripts/python.exe. To check a draft, run tools/passage_engine.py check YOUR_FILE. This does not alter the record. Save the first submitted response to conversation/turn-XX/submission.json and ingest it once with tools/passage_engine.py ingest THAT_FILE. If a protocol failure occurs, preserve that first file and error under attempts before preparing a corrected file. Do not overwrite a first submission. Do not modify the charter, coordinator, existing packet or other contributor record. After successful ingest, run tools/passage_engine.py packet to prepare the next immutable packet, then ask the counterpart to take that turn. Turn25 only ingests and reports completion to root. One serial writer at a time. Root may inspect and build publication material, but does not choose your decisions.
