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
codex fab1cb19a1
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
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

459 B
Raw Blame History

id type title domain repo status owner created updated
CUST-WP-ADHOC-2026-08-25 workplan Ad hoc tasks 2026-08-25 infotech the-custodian active codex 2026-08-25 2026-08-25

Ad hoc tasks 2026-08-25

Verify one-pass workplan binding

id: CUST-WP-ADHOC-2026-08-25-T01
status: done
priority: low

Confirm that a newly registered workplan records its backing file without a second fix-consistency run (CUST-WP-0068-T07).