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

3 commits

Author SHA1 Message Date
tegwick
11bba92b84 docs: mark agent-harness Red-lane secrets Lanes 2–3 provisioned 
Forgejo sandbox deploy key and mail AppRole delivered to railiance01;
checkboxes closed with host path and catalog ids (no secret values).
 2026-07-17 23:57:56 +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
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