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

10
OperatingRhythm.md
View file

@ -58,11 +58,11 @@ all `enabled: true`). Execution on Railiance:
`23 8 * * 1-5 /home/worsch/binky-control/scripts/rhythm-session.sh # binky rhythm bridge`
and pause railiance timers. Script kept for one month as break-glass.
**Known residual (BINKY-WP-0006):** activity-core `ISSUE_SINK_TYPE=state-hub`
emits progress events, not claimable issue-core tasks; agentic daily/review
on Railiance need `claude` CLI on that host (mail-scan is deterministic and
already runs there). Until Claude is installed on railiance01, agentic slots
may still be run from a laptop harness session with the same task files.
**Known residual (BINKY-WP-0006):** finish **llm-connect / OpenRouter** path
for mail triage + briefs on Railiance (structured LLM output + deterministic
apply). **Do not** install Claude Code or another coding agent on railiance01.
Mail-scan is already deterministic and proven there; see
`integrations/railiance-llm-rhythm.md`.
## Weekly review (founder, ~15 min)