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

29 lines
751 B
Markdown
Raw Normal View History

Refresh scope document to match implemented core
2026-07-03 01:50:14 +02:00
---
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
id: ADAPTIVE-WP-ADHOC-2026-07-03
Refresh scope document to match implemented core
2026-07-03 01:50:14 +02:00
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"
Review remaining ceiling work and record contract blockers Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e76a-f84c-7fb2-8309-fdbddf620a43
2026-09-28 11:51:44 +02:00
state_hub_workstream_id: "be24f99d-2047-5256-a7f8-1c4868094e45"
Refresh scope document to match implemented core
2026-07-03 01:50:14 +02:00
---
# Ad hoc repo maintenance - 2026-07-03
## Refresh Scope Document To Match Implemented Capabilities
```task
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
id: ADAPTIVE-WP-ADHOC-2026-07-03-T01
Refresh scope document to match implemented core
2026-07-03 01:50:14 +02:00
status: done
priority: medium
repo.work.assign_missing_identifiers source: repo-manager reason: deterministic projection registration Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e76a-f84c-7fb2-8309-fdbddf620a43
2026-09-28 11:54:07 +02:00
state_hub_task_id: "c0292285-09c0-5d29-9dcf-c99d0e583690"
Refresh scope document to match implemented core
2026-07-03 01:50:14 +02:00
```
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.
Reference in a new issue Copy permalink