92 lines
3 KiB
Markdown
92 lines
3 KiB
Markdown
---
|
|
id: REIN-A-0003
|
|
type: workplan
|
|
title: "Binky weekly founder-review ops-run approach"
|
|
domain: agents
|
|
repo: rein-aharness
|
|
status: active
|
|
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: "4a7ab4e1-5b34-461b-8532-38dd95b3b941"
|
|
---
|
|
|
|
# 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
|
|
|
|
```task
|
|
id: REIN-A-0003-T01
|
|
status: done
|
|
priority: high
|
|
state_hub_task_id: "fec71480-b8c1-48f7-ab4a-8e3ac918cf7e"
|
|
```
|
|
|
|
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: REIN-A-0003-T02
|
|
status: done
|
|
priority: high
|
|
state_hub_task_id: "f23de6a4-3bda-4927-b758-8acfd2c1d035"
|
|
```
|
|
|
|
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
|
|
|
|
```task
|
|
id: REIN-A-0003-T03
|
|
status: wait
|
|
priority: medium
|
|
state_hub_task_id: "cd6b0f33-73ca-49b1-81fe-f15ee321dafb"
|
|
```
|
|
|
|
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.
|