tegwick
f6e2d40a75
`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
28 lines
755 B
Markdown
28 lines
755 B
Markdown
---
|
|
id: KAIZEN-WP-ADHOC-2026-08-21
|
|
type: workplan
|
|
title: "Ad hoc Glas execution-boundary alignment"
|
|
domain: agents
|
|
repo: kaizen-agentic
|
|
status: finished
|
|
owner: codex
|
|
topic_slug: glas-execution-boundary-alignment
|
|
created: "2026-08-21"
|
|
updated: "2026-08-21"
|
|
---
|
|
|
|
# Ad hoc Glas execution-boundary alignment
|
|
|
|
## Align the documented execution handoff with Glas contract 1.0
|
|
|
|
```task
|
|
id: KAIZEN-WP-ADHOC-2026-08-21-T01
|
|
status: done
|
|
priority: high
|
|
```
|
|
|
|
|
|
Apply the completed GLAS-WP-0004 handoff: Kaizen blueprints and agent instances
|
|
name a versioned `harness_profile_ref`; Glas resolves the concrete rein, model,
|
|
sandbox, tool policy, and limits. Preserve activity-core scheduling and durable
|
|
work ownership and rein-local task intake where it already exists.
|