tegwick
9f56c88c96
`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
1.4 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated |
|---|---|---|---|---|---|---|---|---|---|
| SECRETS-WP-ADHOC-2026-08-23 | workplan | Implemented scope and intent-gap reconciliation | infotech | secrets-engine | finished | codex | custodian | 2026-08-23 | 2026-08-23 |
SECRETS-WP-ADHOC-2026-08-23 - Implemented scope and intent-gap reconciliation
Reconcile implemented capability scope
id: SECRETS-WP-ADHOC-2026-08-23-T01
status: done
priority: medium
Checked the repository workplans and coordination inbox. The only active work,
SECRETS-WP-0006-T05/T06, remains waiting on external production approval and
authority; the current ops-warden message requested no credential action.
Rewrote SCOPE.md as an implemented capability boundary rather than an
aspirational/current-work ledger, and recorded a dated assessment against
INTENT.md in
history/2026-08-23-scope-intent-capability-gap-assessment.md. The assessment
documents the achieved CLI MVP and the concrete approval, provisioning,
revocation, verification, auth, evidence, lifecycle, tenancy, and service-mode
gaps without exposing secret material.
statehub fix-consistency was attempted twice and interrupted after repeated
60-second stalls in State Hub HTTP calls (GET /topics/<id> and
PATCH /repos/secrets-engine). The progress event was recorded successfully,
but registrar/index consistency remains pending on State Hub availability.