coulomb/binky-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: agent-harness tenant #1 instance manifest (HARNESS-WP-0001-T07)

Browse source 
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.
This commit is contained in:
tegwick 2026-07-18 11:07:12 +02:00
parent 04410c6269
commit efe4e55e6a
13 changed files with 186 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

10
workplans/BINKY-WP-0004-workstation-independent-executor.md
View file

@ -107,8 +107,14 @@ re-add the cron line. Blue lane with founder notification at cutover.
```task
id: BINKY-WP-0004-T06
status: blocked
blocking_reason: "Gates: Red-lane Lane 2/3 provisioning + agent-harness Railiance deployment (HARNESS-WP-0001-T06/T07) + 3 business days of verified runs. DEC-2026-002 resolved 2026-07-17 (agent-harness). Runbook: integrations/executor-cutover-runbook.md"
status: todo
priority: medium
state_hub_task_id: "eb8c9860-49b4-4d9e-b242-fff48b2ef603"
```
**Unblocked 2026-07-18** for operator execution: Red-lane Lanes 2–3,
HARNESS-WP-0001-T06 (Railiance deploy), and T07 (binky instance manifest +
three definition proof runs) are done. Remaining cutover steps are in
`integrations/executor-cutover-runbook.md` and
`integrations/harness-tenant-onboarding.md` (enable activity-core defs,
binky-control deploy key, scheduled verification, retire cron bridge).