tegwick
13001a1452
`ADHOC-YYYY-MM-DD` is unique per date but not per repository, so any two repos
opening an ad-hoc on the same day collide. The 2026-08-26 fleet projection
reset refused 9 records for exactly this reason.
Canon (work-record-types_v0.1, CUST-WP-0066) settled the form as
`{PREFIX}-WP-ADHOC-YYYY-MM-DD`, filename unchanged, and grandfathered existing
ids on the condition they are never *silently* re-derived. This is the explicit
migration that clause allows for.
The hub id is derived from the record id, so a changed id is a different
record: stale state_hub_*_id fields are dropped and fix-consistency re-derives.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
31 lines
921 B
Markdown
31 lines
921 B
Markdown
---
|
|
id: NK-WP-ADHOC-2026-08-23
|
|
type: workplan
|
|
title: "Ad Hoc Tasks — 2026-08-23"
|
|
domain: infotech
|
|
repo: net-kingdom
|
|
status: finished
|
|
owner: codex
|
|
topic_slug: netkingdom
|
|
created: "2026-08-23"
|
|
updated: "2026-08-23"
|
|
---
|
|
|
|
# Ad Hoc Tasks — 2026-08-23
|
|
|
|
## Advance the canonical audit-core E level after adversarial evidence
|
|
|
|
```task
|
|
id: NK-WP-ADHOC-2026-08-23-T01
|
|
status: done
|
|
priority: high
|
|
```
|
|
|
|
Updated the Tenancy Posture §5 worked example from `E1` to `E2` after
|
|
audit-core published bounded adversarial evidence for both tenant-filtered
|
|
paths. The canon text names run `WH-ENG-20260822-AUDIT-E2-03`, preserves the
|
|
claim's limited meaning, and records the facility freshness review deadline of
|
|
`2026-08-23T22:10:25Z` rather than presenting the result as timeless proof.
|
|
|
|
Verification validates audit-core's declaration against the canonical schema,
|
|
runs the tenancy-posture unit suite, and checks the repository diff.
|