fix(workplans): move work-record identifiers onto the repository prefix
Identifiers predating the PREFIX-WP-NNNN convention were rejected by the canon registry, so none of this repository's work records could be registered. One prefix per repository (ADR-007). Existing conforming identifiers keep their numbers where possible; the pre-convention records take the next free numbers rather than renumbering work that was already correct. Projection UUIDs are re-derived from the new canonical ids (ADR-007 decision 2). Nothing was registered on central under the old identifiers, so no hub record is orphaned by this. Refs CUST-WP-0068-T03 Assistant: claude-code Assistant-Model: opus Assistant-Process: 2583210@bnt-lap001 Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
This commit is contained in:
parent
678ed0bb56
commit
7c8f7e6a9e
7 changed files with 87 additions and 87 deletions
102
workplans/REINAH-WP-0006-binky-weekly-review-approach.md
Normal file
102
workplans/REINAH-WP-0006-binky-weekly-review-approach.md
Normal file
|
|
@ -0,0 +1,102 @@
|
|||
---
|
||||
id: REINAH-WP-0006
|
||||
type: workplan
|
||||
title: "Binky weekly founder-review ops-run approach"
|
||||
domain: agents
|
||||
repo: rein-aharness
|
||||
status: finished
|
||||
owner: codex
|
||||
topic_slug: rein-aharness
|
||||
priority: medium
|
||||
created: "2026-08-08"
|
||||
updated: "2026-08-08"
|
||||
origin: residual
|
||||
origin_ref: REIN-A-0002
|
||||
related:
|
||||
- REIN-A-0002
|
||||
- AWQ-011
|
||||
state_hub_workstream_id: "84f3f979-8788-5b25-a269-d855282af4c6"
|
||||
---
|
||||
|
||||
# REINAH-WP-0006 — Binky weekly founder-review ops-run approach
|
||||
|
||||
## Origin
|
||||
|
||||
Production evidence gathered while closing REIN-A-0002 showed ops run
|
||||
`76b03314-99a4-42e4-aff5-3aa0be43787c` fail safely on 2026-08-07 because the
|
||||
static approach registry has no match for labels `binky`, `weekly-review`, and
|
||||
`automated` (definition `42cb3992-1a31-50d8-94bd-2c430acd89b5`).
|
||||
|
||||
This is outside REIN-A-0002's FI/Binky daily timer cutover and is handed off as
|
||||
a live residual rather than extending that finished scope.
|
||||
|
||||
## Goal
|
||||
|
||||
Define, implement, test, and deploy the cheapest correct approach for Binky's
|
||||
weekly founder-review ops run, including its domain completion event.
|
||||
|
||||
## Determine the weekly-review contract and approach
|
||||
|
||||
```task
|
||||
id: REINAH-WP-0006-T01
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "73557788-4967-51b3-a0fb-7fd0e6b731f6"
|
||||
```
|
||||
|
||||
Inspect the activity-core definition and Binky weekly-review contract. Decide
|
||||
whether an existing deterministic command can satisfy it or a new structured
|
||||
executor is required. Record required inputs, output, and completion event.
|
||||
|
||||
**Decision (2026-08-08):** implement `brief-weekly` as structured llm-connect
|
||||
generation plus a deterministic markdown applier; never use a host coding-agent
|
||||
session. Inputs are the review week's daily briefs, `SuccessMilestones.md`,
|
||||
`DecisionQueue.md`, `RiskRegister.md`, `WORK-RECORDS.md`, the previous weekly
|
||||
review, and recent git history. Output is
|
||||
`briefs/YYYY-MM-DD-weekly-founder-review.md`, committed idempotently, followed
|
||||
by a `binky_weekly_review` progress event. Code derives milestone movement and
|
||||
the RISK-005 `clear|watch|escalate|quiet` state; model output cannot override
|
||||
those facts. Binky residual intake `AWQ-011` is the upstream work record.
|
||||
|
||||
## Implement and test the registry entry
|
||||
|
||||
```task
|
||||
id: REINAH-WP-0006-T02
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "23975c42-0dcb-58fc-85e4-5837d846e1d2"
|
||||
```
|
||||
|
||||
Add the selected approach and pure registry mapping for `weekly-review` plus
|
||||
Binky. Cover execution success, domain completion, and explicit failure.
|
||||
|
||||
**Depends on:** REINAH-WP-0006-T01.
|
||||
|
||||
**Implemented 2026-08-08:** `brief_weekly` structured generation,
|
||||
deterministic milestone/RISK-005 signals, idempotent markdown apply + commit,
|
||||
CLI `brief-weekly`, approach registry dispatch, completion event, and tests.
|
||||
Full suite: 87 passed.
|
||||
|
||||
## Deploy and prove one production cycle
|
||||
|
||||
```task
|
||||
id: REINAH-WP-0006-T03
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "b6f0ae25-6df5-5f2e-a9b4-b9deb2e59489"
|
||||
```
|
||||
|
||||
Deploy the approach to the production claim loop, trigger or observe one run,
|
||||
and record an `open` → `claimed` → `succeeded` proof with its domain event.
|
||||
|
||||
**Depends on:** REINAH-WP-0006-T02.
|
||||
|
||||
**Production proof 2026-08-08:** deployed rein-aharness `8e98ead` to
|
||||
railiance01 and manually triggered activity definition
|
||||
`42cb3992-1a31-50d8-94bd-2c430acd89b5`. Ops run
|
||||
`ad0b05c4-8ad8-40c7-9985-75481728ae30` was claimed as `brief-weekly`, called
|
||||
llm-connect successfully, posted `binky_weekly_review` (HTTP 201), committed
|
||||
`briefs/2026-08-08-weekly-founder-review.md` as Binky commit `27156d6`, and
|
||||
completed `succeeded`. The deterministic result escalated RISK-005 after two
|
||||
active milestone-free review cycles. Upstream intake `AWQ-011` was closed with
|
||||
outcome `promoted` to this workplan.
|
||||
Loading…
Add table
Add a link
Reference in a new issue