Coordination modes: bounded receiver adoption

Use this guide from one immutable target containing compatible conventions, workflows, templates, selected profiles and adapter sources. It applies to updates, attach/repair and unfinished equal-version adoption. Version equality or a copied profile does not prove completion.

Classify before writes

Preserve project purpose/config, task/phase status and journals, grants, original authority epochs, knowledge/history, numeric receipts, custom adapters and unselected neighbors. Compare installed framework rows to their verified prior source. Preview the connected rule/template/profile/ selected-entry group. Custom/ambiguous ownership refuses dependent replacement unchanged for the existing update authority; independent groups may proceed. Do not rewrite active tasks in bulk.

Receiving carrier/action	Disposition
New task/phase	Explicit human-selected coordination_mode plus complete seven-field upstream_route form; validate new issuance and contextual parent
Complete historical five-field owner_gateway, with/without selection pair	Read/continue under unchanged valid authority; preserve exact original semantics
Complete pre-mode seven-field upstream_route	Same unchanged-authority continuation; ordinary lifecycle/time/TRACE updates do not adopt format
No coordination fields	Historical read-only; obtain actual authority before new work
Partial/mixed/downgraded current or old form copied as new	Refuse dependent activation; repair through actual authority, never infer a mode
Deliberate format adoption, unchanged actual choice	At safe checkpoint inspect original human source, scope/roles, holder/parent, effect, reservations and frozen ceiling; populate truthful current fields with the same epoch
Actual mode/route/scope/reporting/dialogue change	Proper human selection/handoff/TS or HL approval; immutable selection event before effective selection_ref

Mode is manual, visible-agents or subagents, independent of delegation/reporting/dialogue and topology. All admit multiple phases. The receiver checks human permission, not just parser success. For a same-holder phase use the task Coordinator as local worker recipient and the real human owner as upward recipient; owner/parent/authority must agree. Finish locally without self-send. A distinct phase holder returns to the actual task Coordinator. Keep phase scope, TS, journal, dependency result and lifecycle separate; root PHASES is not a rollup. Existing carriers keep their valid original route until deliberate adoption; timestamp changes and new trace commits create no consent epoch.

Apply and verify

Install canonical consumers with selected profiles/entries as one accepted connected group. Copy whole canonical command rows exactly; merge only managed persistent blocks, preserving project-owned content. Thin routers stay thin; Cursor remains common-only. Verify exact source/target bytes, selected root pointers, stable repeat and unrelated/custom preservation in an isolated receiver. Record source SHA, applied/preserved/refused paths and limits in the existing init/update result/receipt; no roster, registry, new schema epoch or second state authority.

Ordinary receiver validation — no upstream runtime

Use direct file reads and available repository-object inspection; ordinary lifecycle and adoption require no Python, PyYAML or tools/tfw_state.py. Apply every check below before dependent work:

1. Resolve the exact task/phase in its configured container. Read its own status and journal, then the governing HL/approved TS and exact selection source at their immutable epochs. Check that references resolve inside their permitted scope and that the claimed objects/bytes exist.
2. Interpret the complete YAML fields by meaning, including quoted keys; apply the closed key set, required values, fixed body, lifecycle/outcome relation and transition rules in the status/event templates. Inspect original committed carrier history: a semantically present mode cannot be removed or treated as pre-mode because its key spelling changes. Compare the whole current carrier with its original form, not only the edited field or a timestamp.
3. Classify current issuance, unchanged historical continuation or deliberate adoption using the table above. New issuance needs the explicit actual mode and all seven fields. Complete valid old forms continue only under unchanged authority; absence is read-only. Refuse partial/mixed, downgraded-current or copied-old-as-new forms. Preserve history instead of inferring a mode.
4. Inspect actual human source, scope/roles, effect checkpoint, reservations and frozen ceiling. Verify unit/parent/owner agreement: same-holder phase returns workers to the actual task C and names the real human upward; distinct holder names the actual task C upward. Check phase-local permission and accepted dependencies independently; mode and parser success grant neither.
5. Record adoption/change, preservation/refusal and observed checks in the existing owning result or receipt. Preserve original epoch for verified unchanged-choice format adoption. Actual choice changes use their proper committed selection/approval and checkpoint. Missing or unverifiable facts stop only dependent work with the exact pending actor/condition; no silent validation skip.

This procedure is the complete semantic route for framework-only receivers. Compatible optional maintainer tools may supplement it when already present; they do not replace judgment or create an installation prerequisite. Upstream maintenance uses actual read_status, read_phase_status and validate_new_status for applicable current/historical/refusal checks. These APIs live outside the distributed .tfw payload and are not copied by init/update. Do not enlarge payload or install a runtime to satisfy this guide. A structural route fixture proves no live phase.

Native claims require real role receipts, fresh independent context/fixed Candidate, receiving checks, authorized correction and continuation at the stated P0–P4 level. Fresh Review unavailable keeps acceptance pending its exact mechanism, receipt, phase binding and Candidate access. Never switch provider/mode to turn that into a pass.

This guide changes current issuance/adoption only; it does not migrate history, authorize new work, replace ECFIX accounting, install a scheduler/loop, prepare a release or claim universal provider reliability. Required post-review knowledge/reference effects follow their ordinary owner.