coordination-engine/workplans/COORDINATION-WP-0004-orwell-canon-review.md

id	type	title	domain	repo	status	flavor	owner	topic_slug	created	updated	state_hub_workstream_id
COORDINATION-WP-0004	workplan	OrwellLoggingDiagnostics canon review	communication	coordination-engine	blocked	planning	codex	communication	2026-09-07	2026-09-27	bf08c283-0f43-5a8d-9e63-17c4b96ded11

OrwellLoggingDiagnostics canon review

Operator-approved follow-up to COORDINATION-WP-0003-T04, transferred on 2026-09-07 so canonical review does not block the completed worker runtime. The candidate is docs/orwell-logging-diagnostics-candidate.md; TAMQ is its known consumer and info-tech-canon is the canonical owner.

Reviewed against the current candidate and the owner's documented assimilation process. The candidate exists; no matching registered artifact or explicit owner disposition has been established. This workplan tracks the outstanding obligation without claiming canonical acceptance or authorizing unsafe runtime logging.

Obtain canonical owner disposition

id: COORDINATION-WP-0004-T01
status: done
priority: medium
state_hub_task_id: "c1342268-6e04-5892-a0c9-4dfc3527d466"

Bring the prepared candidate through info-tech-canon's assimilation process and obtain the owner's explicit observe/map/adapt/adopt/reject disposition. Compare with existing observability/data-handling practices and record the decision and any requested changes. Follow the owner's repository instructions and obtain message authorization before contacting another agent if none is already given.

Done when the owner's disposition is linked here with its rationale and the candidate reflects any agreed changes. An unreviewed candidate alone is not canonical acceptance.

2026-09-22: operator authorized contacting the owner. Assimilation request sent to info-tech-canon as State Hub message 3f8f46c0-5fbb-4995-838f-c8820af174f1, asking for an explicit observe/map/adapt/adopt/reject disposition on practice-pattern/orwell-logging-diagnostics. The request treats the candidate as incoming/ material under the owner's intake-and-assimilation practice, does not write into their repo, and offers to send the file content on request. 2026-09-24: disposition received and verified — adapt, decided 2026-09-22 under INFO-DEC-2026-003 by the canon owner. Reply message fff06b47-040b-4a97-8849-aeecbdbfed05; record at info-tech-canon infospace/assimilation/orwell-logging-diagnostics/ASSIMILATION.md (commit 5a1ea90), with our candidate frozen under source/ at 628f984.

Rationale, as recorded by the owner: no existing canon artifact separates verbosity from disclosure, and neither the Data nor the Security model describes a controlled, temporary exception to omission, so the candidate is not a duplicate. It is pattern-shaped and fits PracticePatternScheme. It is adapted rather than adopted because the name and the --orwell flag are consumer-specific; the canon form takes a neutral name, the scheme's layout and imported concepts, while the six practice points carry over unchanged. tmux-amq 04de219 is an implemented and tested known use, so the pattern enters at candidate lifecycle status. No changes to our candidate were requested.

The disposition does not authorize unsafe logging in any runtime, and this repo introduces none. T01 is closed: the owner's disposition is linked here with its rationale and the candidate needs no agreed changes.

Record registration or final disposition

id: COORDINATION-WP-0004-T02
status: wait
priority: medium
state_hub_task_id: "0260b21a-2786-5548-976b-c71f788f3d23"

Depends on T01. For adopt/adapt, record the owner-registered artifact ID, canonical path, version/index entry and validation evidence, then update the candidate and relevant consumer references. Canonical changes belong to info-tech-canon and follow its owner-gated assimilation process.

For observe/map/reject, record the final owner disposition and its implications instead of inventing a canonical registration. Close this follow-up when the owner's chosen outcome is documented and the consumer references are accurate.

2026-09-24: still waiting, now on a known artifact rather than an unknown disposition. Canon placement is info-tech-canon INFO-WP-0030 (workplans/INFO-WP-0030-explicit-unsafe-diagnostics-pattern.md), status proposed as of this check, so no registered artifact exists yet — canon.yaml and infospace/artifacts/index.yaml currently list only the assimilation record, not a practice pattern. The owner will send the registered artifact ID, canonical path and canon version when INFO-WP-0030 finishes. Record them here with validation evidence, refresh the consumer references, then close. Do not anticipate the canonical name or path before registration.

2026-09-27 loose-end review: T02 remains blocked on the canonical owner. State Hub record 75e5efe7-03b0-5492-8244-42851709423d still reports INFO-WP-0030 as proposed; the owner's local workplan agrees. The owner's canon.yaml (version 0.12.0) and infospace/artifacts/index.yaml still register only assimilation/orwell-logging-diagnostics, not the adapted practice pattern. The candidate and consumer references already describe registration as pending, so no local implementation can satisfy T02 yet. The workplan is now blocked rather than active.

Cross-owner observation (derived case; no new workplan):

case_id: COORDINATION-WP-0004-T02-canon-registration
scenario_type: cross_owner_wait
state: waiting
beneficiary_workplan_id: COORDINATION-WP-0004
obligor_workplan_id: INFO-WP-0030
reason: Canonical owner registration and validation evidence are pending.

No matching prj- driver was found in the State Hub workplan scan. Resume when the owner supplies the registered artifact ID, canonical path, version, index entry and validation evidence; then update local references and close T02. This review observed the foreign records without changing them or starting worker injection. All four archived workplans have only completed tasks; no other unfinished local tasks were found.