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>

.kaizen/schedule.yml

@@ -0,0 +1,17 @@
+# Kaizen scheduled agent execution manifest (ADR-005)
+# Declares which agents run on what cadence in this repo.
+# Validate with: kaizen-agentic schedule validate
+version: '1'
+timezone: Europe/Berlin
+agents:
+  coach:
+    cadence: weekly
+    cron: 0 9 * * 1
+    enabled: true
+  optimization:
+    cadence: weekly
+    cron: 0 10 * * 1
+    enabled: true
+  tdd-workflow:
+    cadence: monthly
+    enabled: false

DecisionQueue.md

@@ -22,7 +22,31 @@ fallback_if_no_response: ""
 
 ## Open decisions
 
-*(none)*
+### DEC-2026-002 — Executor worker lives in a new small repo
+
+```yaml
+id: DEC-2026-002
+title: "Executor worker ownership: new thin repo (proposed name: executor-worker) vs. inside activity-core"
+lane: yellow
+status: prepared
+created_at: "2026-07-17"
+needed_by: "before BINKY-WP-0004-T04 deployment (soft)"
+attention_cost: "~2 min read"
+agent_recommendation: "Create a new small repo. ADR-005 (kaizen-agentic) explicitly
+  excludes LLM invocation from both kaizen-agentic ('no LLM invocation; prepare
+  produces a runner-agnostic bundle') and activity-core (owns cron→task only);
+  headless-runner integration is marked 'future; prepare output is runner-agnostic'.
+  activity-core's TaskExecutorWorkflow is a stub by design. A thin repo consuming
+  emitted tasks + `schedule prepare` bundles + llm-connect adapters keeps all three
+  existing boundaries intact and matches the executor assessment
+  (integrations/llm-connect-executor-assessment.md)."
+evidence:
+  - ~/kaizen-agentic/docs/adr/ADR-005-scheduled-agent-execution.md (Boundaries)
+  - integrations/llm-connect-executor-assessment.md
+options: [approve, reject, revise, defer]
+fallback_if_no_response: "Proceed with new-repo prototype for T04 in a sandbox;
+  no cutover (T06) before this decision is resolved."
+```
 
 ## Resolved decisions
 

integrations/llm-connect-executor-assessment.md

@@ -97,6 +97,16 @@ Ownership note: items 1–5 span activity-core / kaizen-agentic / secrets-
 engine domains; the follow-up workplan in binky-control should track them
 as dependencies, with the implementation workplans living in those repos.
 
+## Ownership decision (2026-07-17, BINKY-WP-0004-T01)
+
+Recommendation recorded as **DEC-2026-002**: the executor worker lives in a
+**new small repo**, not inside activity-core or kaizen-agentic. ADR-005's
+boundaries exclude LLM invocation from both existing repos and explicitly
+defer "headless Claude Code / cloud agent runner integration" as a future,
+runner-agnostic concern — that future runner is exactly this worker.
+binky-control opted into kaizen scheduling on the same date
+(`.kaizen/schedule.yml`, coach + optimization weekly, tdd-workflow off).
+
 ## Verdict
 
 Feasible and well-aligned: every layer already exists or is an active

workplans/BINKY-WP-0004-workstation-independent-executor.md

@@ -2,6 +2,7 @@
 id: BINKY-WP-0004
 title: "Workstation-Independent Executor"
 status: active
+state_hub_workstream_id: "b800f91d-a377-45ec-8ff3-6e763c524dff"
 ---
 
 Remove the workstation from the autopilot loop. Successor to BINKY-WP-0003,
@@ -25,8 +26,9 @@ schedule file committed. Green/Blue lane.
 
 ```task
 id: BINKY-WP-0004-T01
-status: todo
+status: done
 priority: high
+state_hub_task_id: "5741487d-2022-4ed6-b4ad-8db745cb90f4"
 ```
 
 ## Task: binky_rhythm_status resolver in activity-core
@@ -42,6 +44,7 @@ or direct PR in that repo per its governance. Green lane (code + tests).
 id: BINKY-WP-0004-T02
 status: todo
 priority: high
+state_hub_task_id: "b44af058-22e4-4d63-a28c-8f6c69d65ea1"
 ```
 
 ## Task: OpenBao lanes for the executor worker
@@ -59,6 +62,7 @@ Catalog metadata only; any new secret provisioning is founder Red lane.
 id: BINKY-WP-0004-T03
 status: todo
 priority: medium
+state_hub_task_id: "e4740aa0-94f7-4ebe-9217-aaca3ef902cc"
 ```
 
 ## Task: Executor worker MVP — one task end-to-end on Railiance
@@ -75,6 +79,7 @@ Blue lane; deployment location Railiance.
 id: BINKY-WP-0004-T04
 status: todo
 priority: high
+state_hub_task_id: "3cb36d02-9934-4c80-81dd-589e7725e407"
 ```
 
 ## Task: Recurring mailbox scan through the executor
@@ -89,6 +94,7 @@ log). Blue lane.
 id: BINKY-WP-0004-T05
 status: todo
 priority: medium
+state_hub_task_id: "2fd2f523-5bd6-400f-abc1-45d3b0a8fcec"
 ```
 
 ## Task: Cut over — enable Binky definitions, retire the cron bridge
@@ -103,4 +109,5 @@ re-add the cron line. Blue lane with founder notification at cutover.
 id: BINKY-WP-0004-T06
 status: todo
 priority: medium
+state_hub_task_id: "eb8c9860-49b4-4d9e-b242-fff48b2ef603"
 ```