coulomb/coordination-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore(consistency): renormalize lifecycle state [auto]
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Updated by fix-consistency on 2026-09-07:
  - workplan status: ready → active

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07b5b-ea58-7ad2-bdbb-0b1c995cfc35
This commit is contained in:
custodian-sync 2026-09-07 16:42:39 +02:00
parent f7aafd50e5
commit 214964ccb8
1 changed files with 62 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

62
workplans/COORDINATION-WP-0004-orwell-canon-review.md Normal file
View file

@ -0,0 +1,62 @@
---
id: COORDINATION-WP-0004
type: workplan
title: "OrwellLoggingDiagnostics canon review"
domain: communication
repo: coordination-engine
status: active
owner: codex
topic_slug: communication
created: "2026-09-07"
updated: "2026-09-07"
state_hub_workstream_id: "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
```task
id: COORDINATION-WP-0004-T01
status: todo
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.
## Record registration or final disposition
```task
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.