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

Record info-tech-canon's adapt disposition; close WP-0004-T01.
Some checks are pending
check / test (push) Waiting to run
Details
CI Smoke / host-smoke (push) Waiting to run
Details
CI Smoke / container-smoke (push) Waiting to run
Details

Browse source 
Owner disposition INFO-DEC-2026-003 (2026-09-22) is adapt, verified against
info-tech-canon commit 5a1ea90. No changes to the candidate were requested,
so T01 is done. T02 still waits: canon placement is INFO-WP-0030, still
proposed, so no registered artifact exists yet.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 61492@bnt-lap001
Assistant-Session: 8e8b440c-c018-4275-aadc-b5b721c5b979
This commit is contained in:
tegwick 2026-09-24 02:22:06 +02:00
parent 00490da2a1
commit 289607e288
2 changed files with 43 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

13
docs/orwell-logging-diagnostics-candidate.md
View file

@ -5,7 +5,8 @@ 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: candidate prepared; owner review and registration outstanding
Status: owner disposition `adapt` recorded 2026-09-22 (INFO-DEC-2026-003);
canon registration pending under info-tech-canon INFO-WP-0030
## Problem
@ -50,3 +51,13 @@ owner disposition before a canon change; a candidate is not registration.
WP-0003-T04 to `workplans/COORDINATION-WP-0004-orwell-canon-review.md`. The
follow-up requires explicit owner disposition and, if accepted, a canonical
artifact/version/index entry. WP-0003 closure does not imply canonical acceptance.
2026-09-24: info-tech-canon disposed this candidate as **adapt** under
`INFO-DEC-2026-003`; its assimilation record is
`infospace/assimilation/orwell-logging-diagnostics/ASSIMILATION.md` (commit
`5a1ea90`), which freezes this file at `628f984` under `source/`. No changes to
this candidate were requested. The canon form will take a neutral name and the
`PracticePatternScheme` layout; the six practice points carry over unchanged.
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.

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

@ -9,7 +9,7 @@ flavor: planning
owner: codex
topic_slug: communication
created: "2026-09-07"
updated: "2026-09-22"
updated: "2026-09-24"
state_hub_workstream_id: "bf08c283-0f43-5a8d-9e63-17c4b96ded11"
---
@ -29,7 +29,7 @@ without claiming canonical acceptance or authorizing unsafe runtime logging.
```task
id: COORDINATION-WP-0004-T01
status: progress
status: done
priority: medium
state_hub_task_id: "c1342268-6e04-5892-a0c9-4dfc3527d466"
```
@ -50,7 +50,25 @@ 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.
Awaiting the owner's reply; the disposition remains theirs to make.
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
@ -69,3 +87,13 @@ 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.