5ff416f6a8
`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
26 lines
629 B
Markdown
26 lines
629 B
Markdown
---
|
|
id: ADAPTIVE-WP-ADHOC-2026-07-03
|
|
type: workplan
|
|
title: "Ad hoc repo maintenance - 2026-07-03"
|
|
domain: financials
|
|
repo: adaptive-pricing
|
|
status: finished
|
|
owner: codex
|
|
topic_slug: helix-forge
|
|
created: "2026-07-03"
|
|
updated: "2026-07-03"
|
|
---
|
|
|
|
# Ad hoc repo maintenance - 2026-07-03
|
|
|
|
## Refresh Scope Document To Match Implemented Capabilities
|
|
|
|
```task
|
|
id: ADAPTIVE-WP-ADHOC-2026-07-03-T01
|
|
status: done
|
|
priority: medium
|
|
```
|
|
|
|
Update `SCOPE.md` so the repo boundary, current state, and execution limits
|
|
match the implemented generic pricing core, Coulomb proving ground, and current
|
|
Stripe shadow-publication / governance surfaces.
|