Records absent from central carried random pre-ADR-007 identifiers minted by the retired local hub, which C-06 refused as stale references. Deriving from the canonical record id takes no identity from anything. Refs CUST-WP-0068-T06 Assistant: claude-code Assistant-Model: opus Assistant-Process: 2583210@bnt-lap001 Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
3.6 KiB
| id | type | title | domain | repo | status | owner | topic_slug | priority | created | updated | origin | origin_ref | related | state_hub_workstream_id | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| REIN-A-0003 | workplan | Binky weekly founder-review ops-run approach | agents | rein-aharness | finished | codex | rein-aharness | medium | 2026-08-08 | 2026-08-08 | residual | REIN-A-0002 |
|
119fca2b-0966-51b4-9758-12c8d49adfc5 |
REIN-A-0003 — 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
id: REIN-A-0003-T01
status: done
priority: high
state_hub_task_id: "d79cc49a-fb1b-540e-9c8a-c6feae751da5"
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
id: REIN-A-0003-T02
status: done
priority: high
state_hub_task_id: "63601140-e2b3-5156-a503-cd6bd79ad8b5"
Add the selected approach and pure registry mapping for weekly-review plus
Binky. Cover execution success, domain completion, and explicit failure.
Depends on: REIN-A-0003-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
id: REIN-A-0003-T03
status: done
priority: medium
state_hub_task_id: "b4fa6608-26a2-55f7-a0ea-3b042197b15f"
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: REIN-A-0003-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.