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

7 commits

Author SHA1 Message Date
tegwick
6ab1391b18 BINKY-WP-0004-T06 in progress: DEC-2026-003 approved, definitions enabled 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-07-18 14:38:40 +02:00
tegwick
efe4e55e6a feat: agent-harness tenant #1 instance manifest (HARNESS-WP-0001-T07) 
Extend .kaizen/schedule.yml with harness fields for daily rhythm, weekly
mail intake, and weekly review-prep; add task files, onboarding handoff
doc, and cutover gate updates for BINKY-WP-0004-T06.
 2026-07-18 11:07:12 +02:00
tegwick
7c5e644d6f DEC-2026-002 resolved: agent-harness (single shared runtime) 
- DecisionQueue: moved to resolved log with rescoped outcome (three-layer
  model; binky-control = tenant #1); hub decision resolved
- Secret lanes doc: identifiers renamed executor-worker → agent-harness
  before any provisioning happens
- Cutover runbook + WP-0004-T06: gate 1 done; deployment gate now points
  at HARNESS-WP-0001-T06/T07 in the agent-harness repo

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-07-17 23:37:16 +02:00
tegwick
02a8d293ab BINKY-WP-0004 T04/T05 done, T06 blocked with cutover runbook 
- T04: executor-worker MVP (new repo ~/executor-worker) ran one task
  end-to-end: kaizen schedule-prepare persona, agentic llm-connect
  session, sandbox commit e043f21, hub progress event
- T05: recurring mailbox scan fully wired (two-phase: deterministic
  credentialed scan + LLM triage session with suspicious-mail log-only
  rule); email checklist item 9 now gated only on Lane 3 AppRole
- T06: blocked — gates are DEC-2026-002, Red-lane Lanes 2/3, Railiance
  deploy, 3 verified runs; runbook at
  integrations/executor-cutover-runbook.md

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-07-17 17:17:15 +02:00
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