fab1cb19a1
`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>
31 lines
831 B
Markdown
31 lines
831 B
Markdown
---
|
|
id: CUST-WP-ADHOC-2026-07-02
|
|
type: workplan
|
|
title: "Ad Hoc Tasks — 2026-07-02"
|
|
domain: infotech
|
|
repo: the-custodian
|
|
status: finished
|
|
owner: codex
|
|
topic_slug: custodian
|
|
created: "2026-07-02"
|
|
updated: "2026-07-02"
|
|
---
|
|
|
|
# CUST-WP-ADHOC-2026-07-02 — Ad Hoc Tasks
|
|
|
|
Small same-day improvements that are useful to track, but do not justify a
|
|
dedicated requirement/workplan cycle.
|
|
|
|
## Extend Canonical Capability Tags
|
|
|
|
```task
|
|
id: CUST-WP-ADHOC-2026-07-02-T01
|
|
status: done
|
|
priority: medium
|
|
```
|
|
|
|
Extend the repo-classification canon so `monetization`, `lifecycle`,
|
|
`decision-support`, and `product-development` are recognized as recommended
|
|
canonical capability tags. Update both the machine-readable allowed-values file
|
|
and the human-readable standard example/family lists so State Hub validation and
|
|
documentation remain aligned.
|