coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions
the-custodian/workplans/ADHOC-2026-07-02.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

831 B
Raw Blame History

id type title domain repo status owner topic_slug created updated
CUST-WP-ADHOC-2026-07-02 workplan Ad Hoc Tasks — 2026-07-02 infotech the-custodian finished codex custodian 2026-07-02 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

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.