coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions
the-custodian/workplans/ADHOC-2026-08-25.md

26 lines
525 B
Markdown
Raw Normal View History

chore(adhoc): verify one-pass workplan binding Refs CUST-WP-0068-T07 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-25 15:35:12 +02:00
---
fix(workplans): qualify ad-hoc identifiers with the repository prefix `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>
2026-08-28 00:28:24 +02:00
id: CUST-WP-ADHOC-2026-08-25
chore(adhoc): verify one-pass workplan binding Refs CUST-WP-0068-T07 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-25 15:35:12 +02:00
type: workplan
title: "Ad hoc tasks 2026-08-25"
domain: infotech
repo: the-custodian
finish three custodian workplans from live hub evidence Close CUST-WP-0064 after the 2026-08-24 unassisted fire ingested clay-borg, close CUST-WP-0065 now that all 120 active repos project a classification, and close ADHOC-2026-08-25. Mark CUST-WP-0067 T02/T10 done (reverse relays already gone; work-record recovery lives on 0068). Park the later no-checkout SBOM regression as CUST-IN-0015. Teach the classification gate to use this host's checkout path.
2026-08-28 20:27:05 +02:00
status: finished
chore(adhoc): verify one-pass workplan binding Refs CUST-WP-0068-T07 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-25 15:35:12 +02:00
owner: codex
created: "2026-08-25"
finish three custodian workplans from live hub evidence Close CUST-WP-0064 after the 2026-08-24 unassisted fire ingested clay-borg, close CUST-WP-0065 now that all 120 active repos project a classification, and close ADHOC-2026-08-25. Mark CUST-WP-0067 T02/T10 done (reverse relays already gone; work-record recovery lives on 0068). Park the later no-checkout SBOM regression as CUST-IN-0015. Teach the classification gate to use this host's checkout path.
2026-08-28 20:27:05 +02:00
updated: "2026-08-28"
chore(consistency): write back registrar identifiers Keep the UUIDs the registrar minted for CUST-IN-0015, CUST-WP-0068-T09, and the ad-hoc workplans after the run failed on an unrelated historic task create.
2026-08-28 20:33:31 +02:00
state_hub_workstream_id: "b82be75e-29c3-58a0-a39e-cc4d6ac96790"
chore(adhoc): verify one-pass workplan binding Refs CUST-WP-0068-T07 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-25 15:35:12 +02:00
---
# Ad hoc tasks 2026-08-25
## Verify one-pass workplan binding
```task
fix(workplans): qualify ad-hoc identifiers with the repository prefix `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>
2026-08-28 00:28:24 +02:00
id: CUST-WP-ADHOC-2026-08-25-T01
chore(adhoc): verify one-pass workplan binding Refs CUST-WP-0068-T07 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-25 15:35:12 +02:00
status: done
priority: low
```
Confirm that a newly registered workplan records its backing file without a
second `fix-consistency` run (`CUST-WP-0068-T07`).
Reference in a new issue Copy permalink