coulomb/adaptive-pricing
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
adaptive-pricing/workplans/ADHOC-2026-07-03.md
codex 5ff416f6a8
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>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-28 00:28:19 +02:00

629 B
Raw Blame History

id type title domain repo status owner topic_slug created updated
ADAPTIVE-WP-ADHOC-2026-07-03 workplan Ad hoc repo maintenance - 2026-07-03 financials adaptive-pricing finished codex helix-forge 2026-07-03 2026-07-03

Ad hoc repo maintenance - 2026-07-03

Refresh Scope Document To Match Implemented Capabilities

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.