coulomb/binky-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
33 commits 1 branch 0 tags 678 KiB
Commit graph

3 commits

Author SHA1 Message Date
tegwick
ce14c254db BINKY-WP-0004-T03: executor worker secret lanes prepared 
- Lane 1 (LLM provider): reuse verified — warden catalog
  openrouter-llm-connect, policy workload-kv-read-llm-connect-provider-secrets
- Lane 2 (forgejo deploy key): new, per-repo write deploy key design,
  founder Red lane
- Lane 3 (mail-scan AppRole): executor-worker-binky-mail bound to the
  existing IMAP read policy — closes email checklist item 9's auth
  blocker on paper; provisioning founder Red lane
- No secret values anywhere; T04 can proceed on Lane 1 alone

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-07-17 17:08:33 +02:00
tegwick
0f91a98d08 BINKY-WP-0004-T01: kaizen schedule opt-in + executor ownership decision 
- .kaizen/schedule.yml scaffolded via schedule init, validates clean
  (coach + optimization weekly, tdd-workflow disabled)
- DEC-2026-002 prepared: executor worker in a new small repo, per
  ADR-005 boundaries; fallback allows sandbox prototype, no cutover
  before resolution
- Decision rationale recorded in the executor assessment

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-07-17 17:01:19 +02:00
tegwick
bcabe2d17b BINKY-WP-0004 draft: workstation-independent executor 
Six tasks from the llm-connect executor assessment: kaizen WP-0006
alignment + schedule opt-in, binky_rhythm_status resolver, OpenBao lanes
(incl. non-interactive AppRole for recurring mail scans), executor worker
MVP on Railiance, recurring mailbox scan, cutover retiring the cron
bridge.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-07-17 12:20:11 +02:00