Complete T06 cutover: remove binky rhythm bridge crontab, install scripts/railiance-rhythm systemd user timers on railiance01 (Europe/Berlin), document residual continuous-intake gaps as BINKY-WP-0006. Three completion event types verified (daily_brief, mail_intake on Railiance, weekly_review). DEC-2026-003 marked resolved/executed.
2.3 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated |
|---|---|---|---|---|---|---|---|---|---|
| BINKY-WP-0006 | workplan | Railiance rhythm: continuous intake + agentic runtime on host | infotech | binky-control | ready | codex | the-custodian | 2026-07-21 | 2026-07-21 |
Close the residual gaps after BINKY-WP-0004 cutover so rhythm is fully unattended on Railiance without host-timer dual scheduling.
Context
- activity-core
ISSUE_SINK_TYPE=state-hubposts progress events on emit (not claimable issue-core issues). agent-harness intake still polls issue-core. - agent-harness k8s deploy is
sleep infinity(placeholder). - railiance01 host timers call task files directly (interim).
- Agentic daily/review need
claudeCLI on railiance01 (absent as of 2026-07-21); mail-scan works via AppRole without Claude.
Task: Choose emission → execution contract
id: BINKY-WP-0006-T01
status: todo
priority: high
Decide with activity-core / harness owners:
A) Restore opt-in ISSUE_SINK_TYPE=rest for Binky labels only, or
B) Teach agent-harness to claim work from a state-hub work-record / task queue, or
C) Keep host timers as the durable executor and demote activity-core schedules
to observability-only for Binky.
Record decision (DEC if founder-relevant) and update
integrations/executor-cutover-runbook.md.
Task: Continuous consumer on Railiance
id: BINKY-WP-0006-T02
status: todo
priority: high
Implement the chosen path: systemd/k8s poller loop, not sleep infinity.
Health metrics + logs under ~/.cache/binky-control/rhythm/.
Task: Agentic runtime on railiance01
id: BINKY-WP-0006-T03
status: todo
priority: high
Install and auth Claude Code (or approved hosted agentic adapter) on
railiance01 so run-daily.sh / run-review.sh exit 0 unattended. Document
in integrations/executor-worker-secrets.md if new secret lanes appear.
Task: Retire dual scheduling
id: BINKY-WP-0006-T04
status: todo
priority: medium
Once T01–T03 proven for three business days: remove host timers or disable redundant activity-core schedules so only one cadence owner remains. Update OperatingRhythm.md.
Task: Closure
id: BINKY-WP-0006-T05
status: todo
priority: low
Mark finished; log milestone; statehub fix-consistency.