prj-unattended-progress-com.../evidence/g3-dogfood-acceptance.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

2.5 KiB

id type repo parent_workplan created as_of
UPC-EVID-G3-0001 evidence prj-unattended-progress-company UPC-WP-0003 2026-09-28 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. Rhythm output is stranded and the timers are off (checked 2026-09-28). The workstation copy of binky-control/briefs/ stops at 2026-08-08, but railiance01's checkout holds 13 unpushed rhythm commits: daily briefs 2026-08-10…14 and 2026-09-07…11, weekly reviews 2026-08-14 and 2026-09-11. So the loop did run unattended, but (a) it has not pushed, so the audit trail is not on the remote, and (b) the three binky-rhythm-* user timers are disabled/inactive, so nothing has run since 2026-09-11 (and nothing between 2026-08-15 and 2026-09-06). Owner: binky-control / REIN-A-0003. Fixed 2026-09-28: the 13 commits were rebased and pushed, and the three timers re-enabled on railiance01 (daily timer fired on install).
  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…09-11 (once pushed), stopped since. Not yet ready to request the S3 mark; do so once residual 1 is fixed (push + re-enable timers).