coulomb/kaizen-agentic
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kaizen-agentic/workplans/ADHOC-2026-08-21.md
tegwick f6e2d40a75
All checks were successful
ci / test (push) Successful in 2m42s
Details
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 0s
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:23 +02:00

755 B
Raw Blame History

id type title domain repo status owner topic_slug created updated
KAIZEN-WP-ADHOC-2026-08-21 workplan Ad hoc Glas execution-boundary alignment agents kaizen-agentic finished codex glas-execution-boundary-alignment 2026-08-21 2026-08-21

Ad hoc Glas execution-boundary alignment

Align the documented execution handoff with Glas contract 1.0

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.