binky-control/integrations
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
..
activity-core-wiring.md BINKY-WP-0003-T05: activity-core wiring — 3 proposed definitions landed 2026-07-16 14:04:37 +02:00
company-email-openbao.md BINKY-WP-0004 T04/T05 done, T06 blocked with cutover runbook 2026-07-17 17:17:15 +02:00
executor-cutover-runbook.md DEC-2026-002 resolved: agent-harness (single shared runtime) 2026-07-17 23:37:16 +02:00
executor-worker-secrets.md DEC-2026-002 resolved: agent-harness (single shared runtime) 2026-07-17 23:37:16 +02:00
llm-connect-executor-assessment.md BINKY-WP-0004-T01: kaizen schedule opt-in + executor ownership decision 2026-07-17 17:01:19 +02:00
mailbox-binky-company.yml Record IONOS IMAP host facts for company mailbox 2026-07-17 00:15:25 +02:00
paper-mail-intake.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