COORDINATION-WP-0004-T02 done: record registered canon artifact; CUST-WP-0075
Some checks failed
CI Smoke / host-smoke (push) Waiting to run
CI Smoke / container-smoke (push) Waiting to run
check / test (push) Has been cancelled

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 3775@bnt-lap001
Assistant-Session: cfacb6a5-ad5b-4f79-ac67-053e3b0d34a3
This commit is contained in:
tegwick 2026-10-03 03:25:51 +02:00
parent ac16a472db
commit 0b7eeb1483
4 changed files with 33 additions and 10 deletions

View file

@ -8,6 +8,6 @@
| Kind | ID | Status | Lane | Source |
| --- | --- | --- | --- | --- |
| workplan | COORDINATION-WP-0004 | blocked | — | workplans/COORDINATION-WP-0004-orwell-canon-review.md |
| workplan | COORDINATION-WP-0004 | active | — | workplans/COORDINATION-WP-0004-orwell-canon-review.md |
| task | COORDINATION-WP-0004-T01 | done | — | workplans/COORDINATION-WP-0004-orwell-canon-review.md |
| task | COORDINATION-WP-0004-T02 | wait | — | workplans/COORDINATION-WP-0004-orwell-canon-review.md |
| task | COORDINATION-WP-0004-T02 | todo | — | workplans/COORDINATION-WP-0004-orwell-canon-review.md |

View file

@ -5,8 +5,10 @@ Canonical owner: info-tech-canon
Requested by: coordination-engine / COORDINATION-WP-0003-T04
Follow-up: COORDINATION-WP-0004
Known use: tmux-amq's local diagnostic mode
Status: owner disposition `adapt` recorded 2026-09-22 (INFO-DEC-2026-003);
canon registration pending under info-tech-canon INFO-WP-0030
Status: superseded by canon. Registered by info-tech-canon as
`practice-pattern/explicit-unsafe-diagnostic-mode`
(`infospace/patterns/ExplicitUnsafeDiagnosticMode.md`, pattern status
`candidate`, version 0.1) at canon version 0.13.0 under INFO-WP-0030
## Problem
@ -61,3 +63,14 @@ this candidate were requested. The canon form will take a neutral name and the
Canon placement is pending under `INFO-WP-0030`, so there is still no
registered canonical artifact and this file remains a candidate, not canon.
The disposition does not authorize unsafe logging in any runtime.
2026-10-03: registration complete. info-tech-canon finished `INFO-WP-0030` on
2026-09-27 and returned the registration in State Hub message `37bf8ae5`:
artifact `practice-pattern/explicit-unsafe-diagnostic-mode`, path
`infospace/patterns/ExplicitUnsafeDiagnosticMode.md`, pattern status
`candidate`, version 0.1, canon version 0.13.0. Verified in the owner checkout:
the pattern file exists with that id and version, and
`infospace/artifacts/index.yaml` lists it. The owner reports `make check`
passing (60 tests, 0 validation errors or warnings). The canonical name is
neutral; `OrwellLoggingDiagnostics` is kept as an alias. This file is now a
historical candidate. Cite the canonical artifact, not this file.

View file

@ -148,9 +148,10 @@ versions. No source bodies, checkpoint text, credentials or terminal output are
projected. Local status/history may expose checkpoints to the approved user.
TAMQ owns unsafe `--orwell` diagnostics. Coordination-engine has no unsafe sink.
`docs/orwell-logging-diagnostics-candidate.md` records the candidate practice;
canonical review/registration remains with info-tech-canon, tracked separately
in COORDINATION-WP-0004 with operator approval.
The practice is canon: info-tech-canon
`practice-pattern/explicit-unsafe-diagnostic-mode` (canon 0.13.0, alias
`OrwellLoggingDiagnostics`). `docs/orwell-logging-diagnostics-candidate.md`
keeps the original candidate for provenance.
Default checks: `uv run pytest`, `git diff --check`, compileall, CLI help/version.
Tests exercise SQLite durability and locking, fake State Hub and gita, actual

View file

@ -4,7 +4,7 @@ type: workplan
title: "OrwellLoggingDiagnostics canon review"
domain: communication
repo: coordination-engine
status: active
status: finished
flavor: planning
owner: codex
topic_slug: communication
@ -74,7 +74,7 @@ rationale and the candidate needs no agreed changes.
```task
id: COORDINATION-WP-0004-T02
status: todo
status: done
depends_on: [COORDINATION-WP-0004-T01]
priority: medium
state_hub_task_id: "0260b21a-2786-5548-976b-c71f788f3d23"
@ -113,7 +113,7 @@ Cross-owner observation (derived case; no new workplan):
```yaml
case_id: COORDINATION-WP-0004-T02-canon-registration
scenario_type: cross_owner_wait
state: waiting
state: satisfied
beneficiary_workplan_id: COORDINATION-WP-0004
obligor_workplan_id: INFO-WP-0030
reason: Canonical owner registration and validation evidence are pending.
@ -127,3 +127,12 @@ starting worker injection. All four archived workplans have only completed
tasks; no other unfinished local tasks were found.
2026-10-03: every depends_on target is terminal (C-40); cleared to todo by CUST-WP-0075.
2026-10-03 closure (CUST-WP-0075): the owner's return arrived 2026-09-27 as
State Hub message `37bf8ae5` and sat unread. Registered artifact
`practice-pattern/explicit-unsafe-diagnostic-mode`, path
`infospace/patterns/ExplicitUnsafeDiagnosticMode.md`, version 0.1, canon
0.13.0; index entry present in `infospace/artifacts/index.yaml`; owner reports
`make check` green. Updated `docs/orwell-logging-diagnostics-candidate.md` and
the spec reference to cite the canonical artifact. ADR-002 is left as a dated
decision record. T02 done; workplan finished.