prj-unattended-progress-com.../workplans/UPC-WP-0003-unattended-and-load.md
tegwick 96196912fc Follow up: G4 log owner AWQ-014, G5 package DEC-2026-006, rhythm restored
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 293620@bnt-lap001
Assistant-Session: 50ae9ffb-1cc3-48ec-8cfe-1941bcf2f2fb
2026-09-28 23:18:32 +02:00

88 lines
3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
id: UPC-WP-0003
type: workplan
title: "Unattended dogfood acceptance and founder-load envelope (G3–G4)"
domain: infotech
repo: prj-unattended-progress-company
status: blocked
flavor: planning
owner: bernd
topic_slug: infotech
repo_goal_id: "79a2b057-b765-47ad-b5d9-c1bbc49eba43"
created: "2026-08-11"
updated: "2026-09-28"
state_hub_workstream_id: "81b17b8a-4b22-5510-8830-a8d19aed821e"
---
# Unattended dogfood acceptance and founder-load envelope (G3–G4)
## Goal
1. **G3:** Package acceptance evidence that at least one end-to-end Green/Blue
loop runs unattended with audit trail (already largely built in BINKY-WP-0004/0006).
2. **G4:** Define and start a ≥30-day founder-load measurement against the
1–3 h/day + ~2 OH days/month envelope.
Parent goal: `79a2b057-…`. Depends on foundation maps; can run in parallel
with UPC-WP-0002 after T01 evidence folder exists.
## Linked children
| ID / artefact | Role |
| --- | --- |
| BINKY-WP-0004, 0006 | Executor + llm-connect rhythm (finished) |
| AWQ-011 / REIN-A-0003 / ops_run `ad0b05c4-…` | Weekly review production proof |
| `audits/OK-Audit-v0-binky.md` | Dogfood audit |
| `OperatingRhythm.md`, `briefs/` | Cadence evidence |
| *missing* load metric | G4 design needed in binky-control |
## Tasks (proposed — activate when UPC-WP-0002 is underway or G1 not blocking)
```task
id: UPC-WP-0003-T01
status: done
priority: high
state_hub_task_id: "57636795-371d-56ac-b4f4-cfcf2968e133"
```
Write `evidence/g3-dogfood-acceptance.md` linking finished child WPs, audit,
and at least one production ops_run; list any residual that prevents founder
S3 mark.
**Done (2026-09-28):** `evidence/g3-dogfood-acceptance.md`. Names one real
residual: rhythm output stranded unpushed on railiance01 and timers disabled since 2026-09-11.
```task
id: UPC-WP-0003-T02
status: done
priority: high
state_hub_task_id: "b38eebc3-51a7-54e4-a4d3-8f8edfc16aac"
```
Specify founder-load measurement (what counts, log location, Red exceptions)
in a short design note under `architecture/` and ensure a live residual or
child intake in `binky-control` owns ongoing logging.
**Progress (2026-09-28):** design note at
`architecture/founder-load-measurement.md`. **Done (2026-09-28):** residual
`binky-control` **AWQ-014** owns the log; `briefs/load-log.csv` created there.
```task
id: UPC-WP-0003-T03
status: todo
priority: medium
state_hub_task_id: "d79967eb-a270-53aa-a501-0a4f38d8c1cc"
```
After ≥30 days of measurement (or first checkpoint), update gate-map G3/G4
and prepare founder decision packages for S3 / load-budget claims.
**Blocked (2026-09-28):** T03 needs ≥30 days of logged measurement; the
window starts at the first logged day in `binky-control/briefs/load-log.csv`
(founder enters minutes). Also: G3 rhythm was restored 2026-09-28 (see
`evidence/g3-dogfood-acceptance.md`); S3 request follows a few clean days.
## Acceptance
- G3 evidence pack complete; S3 mark requested or residual explicit
- G4 measurement live as a work record outside this file’s prose