Close loose ends: G3 evidence pack, G4 load design, mark blocked workplans

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
This commit is contained in:
tegwick 2026-09-28 23:11:36 +02:00
parent 20e8191f3b
commit b586296998
6 changed files with 117 additions and 10 deletions

View file

@ -0,0 +1,46 @@
---
id: UPC-EVID-G3-0001
type: evidence
repo: prj-unattended-progress-company
parent_workplan: UPC-WP-0003
created: "2026-09-28"
as_of: "2026-09-28"
---
# G3 dogfood-loop acceptance pack
Links only; authoritative records live in `binky-control` and `railiance`.
No secrets or raw data here.
## Claim
At least one end-to-end internal loop runs unattended under Green/Blue policy
and leaves an audit trail without founder mid-flight steering.
## Evidence
| Item | Record | Status | What it shows |
| --- | --- | --- | --- |
| Workstation-independent executor | BINKY-WP-0004 | finished | Loop no longer needs the laptop or a host coding agent |
| Railiance rhythm via llm-connect | BINKY-WP-0006 | finished | Mail scan + triage and daily brief run on railiance01 |
| Mail loop, 3 clean cycles | BINKY-WP-0006 (2026-07-22) | done | Hub events `binky_mail_intake` + `binky_mail_triage`, each `ok` |
| Weekly review, production proof | AWQ-011 → REIN-A-0003, ops_run `ad0b05c4-8ad8-40c7-9985-75481728ae30` | closed / promoted | Unattended `binky_weekly_review` run on 2026-08-08 |
| Briefs as cadence trail | `binky-control/briefs/` | daily 2026-08-04…07, weekly 2026-08-08 | Committed, dated outputs |
| Dogfood audit | `binky-control/audits/OK-Audit-v0-binky.md` | v0, 2026-07-16 | First flagship-offer run on the company itself |
## Residuals preventing the founder S3 mark
1. **Briefs stop at 2026-08-08.** `binky-control/briefs/` has nothing after the
weekly review, and binky-control has had no rhythm-generated commits since
the 2026-08-16 work. Either the rhythm is not running or its output is not
committed; unattended-ness after 2026-08-08 is unproven. Needs a check on
railiance01 (owner: binky-control / REIN-A-0003). This is the main
blocker to a clean S3 request.
2. **S3 is still ⬜** in `binky-control/SuccessMilestones.md`. Only the
founder marks it (Yellow).
3. AWQ-012 (open-weights retarget) is optional and does not block S3.
## Verdict
G3 evidence: **strong for 2026-07-22…08-08, gap since**. Not yet ready to
request the S3 mark; do so once residual 1 is explained or fixed.