info-tech-canon/workplans/INFO-WP-0030-explicit-unsafe-diagnostics-pattern.md
tegwick e0ca7de63b
Some checks are pending
CI Smoke / host-smoke (push) Waiting to run
CI Smoke / container-smoke (push) Waiting to run
Close out INFO-WP-0030; record second Emission Cadence declaration
INFO-WP-0030: register practice-pattern/explicit-unsafe-diagnostic-mode
(adapted from coordination-engine's OrwellLoggingDiagnostics candidate,
INFO-DEC-2026-003) at canon 0.13.0, close the assimilation, and notify
coordination-engine for COORDINATION-WP-0004-T02. Workplan finished.

INFO-WP-0029: record activity-core's source-owned declaration (T03/T04
done) with its expected-rate/calendar-schedule incompatibility as
demand/EmissionExpectedRateCalendar.md, and record audit-core's
structural-only observer evaluation of net-kingdom's declaration as a
steward note. No party has yet produced a real observer result against
traffic, so T05 and the workplan stay blocked on external action.

Updated artifact-count and practice-pattern-count assertions in
tests/test_cli.py and tests/test_service.py for the new artifact.

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

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 317218@bnt-lap001
Assistant-Session: a8d6c0ab-c70f-4610-a288-576f44d747d4
2026-09-28 00:06:16 +02:00

60 lines
2.3 KiB
Markdown

---
id: INFO-WP-0030
type: workplan
title: "Place the adapted OrwellLoggingDiagnostics practice pattern"
domain: infotech
repo: info-tech-canon
status: finished
owner: claude
topic_slug: canon-optimization
created: "2026-09-22"
updated: "2026-09-27"
flavor: planning
state_hub_workstream_id: "75e5efe7-03b0-5492-8244-42851709423d"
---
# Place the adapted OrwellLoggingDiagnostics practice pattern
The canon owner disposed the coordination-engine candidate as **adapt**
(`INFO-DEC-2026-003`, recorded in
`infospace/assimilation/orwell-logging-diagnostics/ASSIMILATION.md`). This
workplan carries stages 4 and 5 of the intake practice. When it finishes, it
supplies coordination-engine's COORDINATION-WP-0004-T02 with the registered
artifact ID, path, and version.
## Write the pattern in canon shape
```task
id: INFO-WP-0030-T01
status: done
priority: medium
state_hub_task_id: "13d9ccbe-8136-5fc9-b8ae-4307b4eec773"
```
Written as `practice-pattern/explicit-unsafe-diagnostic-mode`
(`infospace/patterns/ExplicitUnsafeDiagnosticMode.md`), `status: candidate`,
`version: "0.1"`. Imports `Log`/`LogRecord` from `model/observability`,
`DataClassification`/`Sensitivity` from `model/data`, and
`EnvironmentPromotion` from `model/devsecops`. Alias `OrwellLoggingDiagnostics`
is kept. Known Uses cites tmux-amq `04de219` and names the one observed test
(`tests/test_diagnostics.py::test_orwell_log_is_private`), stating plainly
that it does not demonstrate the production-refusal invariant — tmux-amq has
no production/non-production distinction to check against.
## Register, version, and close the assimilation
```task
id: INFO-WP-0030-T02
status: done
priority: medium
state_hub_task_id: "4c9a3fa1-e870-53e0-a43f-4831b7d7529c"
```
Registered in `canon.yaml` (assimilation record + `version: 0.13.0`) and
`infospace/artifacts/index.yaml`. `infospace/infospace.yaml` needed no change:
it does not carry a separate pattern catalog. Indexes and briefs regenerated;
`make check` passes (60 tests; 0 validation errors/warnings; count-based
tests updated for the new artifact). `CHANGELOG.md` records canon 0.13.0.
`infospace/assimilation/orwell-logging-diagnostics/ASSIMILATION.md` is set to
`closed`. Sent coordination-engine the artifact ID, path, and version for
COORDINATION-WP-0004-T02 (State Hub message `37bf8ae5-5fdd-44d9-b58c-296f9973c2cf`).