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

BINKY-WP-0006: retarget Railiance rhythm to llm-connect/OpenRouter
Some checks failed
Work Records / validate (push) Has been cancelled
Details

Browse source 
Reject Claude Code (or any coding agent) on railiance01. Mail-scan stays
deterministic; triage/briefs use llm-connect HTTP → structured JSON →
deterministic apply. Document in integrations/railiance-llm-rhythm.md and
rewrite WP-0006 tasks accordingly; timers no longer require_claude.
This commit is contained in:
tegwick 2026-07-22 00:00:04 +02:00
parent 5011e53090
commit 88a4886ea7
9 changed files with 252 additions and 63 deletions
Download patch file Download diff file Expand all files Collapse all files

7
integrations/executor-cutover-runbook.md
View file

@ -42,9 +42,10 @@ cd ~/binky-control && git pull
| Gap | Follow-up |
| --- | --- |
| No continuous harness consumer of state-hub sink emissions | BINKY-WP-0006 / harness intake |
| No `claude` CLI on railiance01 (agentic daily/review fail-closed until installed) | BINKY-WP-0006 |
| Host timers are interim dual of activity-core cron (not pure sink-driven) | retire timers when poller live |
| Post-scan **triage** still assumes coding-agent session (Claude) | BINKY-WP-0006: **llm-connect → OpenRouter** + JSON apply (see `railiance-llm-rhythm.md`) |
| Daily/review unattended without host coding agent | Same pattern via llm-connect |
| Host timers dual activity-core schedules | Simplify once llm path is the only executor |
| **Out of scope / rejected:** install Claude Code on railiance01 | — |
## Rollback