binky-control/workplans
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
..
BINKY-WP-0001-statehub-bootstrap.md Conform workplan to canonical BINKY-WP prefix (BNKY-WP-0001 -> BINKY-WP-0002) 2026-07-16 02:51:35 +02:00
BINKY-WP-0002-operating-kernel-bootstrap.md Prepare first Office-Hour Command Day runbook; close BINKY-WP-0002 2026-07-16 09:16:43 +02:00
BINKY-WP-0003-autopilot-and-rhythm.md rhythm bridge 2026-07-16: queue hygiene clean; AWQ-005 website draft; include AWQ-008 paper-mail intake artifacts + hub id sync 2026-07-16 15:02:48 +02:00
BINKY-WP-0004-workstation-independent-executor.md DEC-2026-002 resolved: agent-harness (single shared runtime) 2026-07-17 23:37:16 +02:00