binky-control/workplans/BINKY-WP-0006-railiance-rhythm-continuous-intake.md
tegwick c3ea150971
Some checks failed
Work Records / validate (push) Has been cancelled
BINKY-WP-0004 finished: retire workstation cron, Railiance rhythm timers
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.
2026-07-21 23:51:43 +02:00

87 lines
2.3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
id: BINKY-WP-0006
type: workplan
title: "Railiance rhythm: continuous intake + agentic runtime on host"
domain: infotech
repo: binky-control
status: ready
owner: codex
topic_slug: the-custodian
created: "2026-07-21"
updated: "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-hub` posts **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 `claude` CLI on railiance01 (absent as of 2026-07-21);
mail-scan works via AppRole without Claude.
## Task: Choose emission → execution contract
```task
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
```task
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
```task
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
```task
id: BINKY-WP-0006-T04
status: todo
priority: medium
```
Once T01T03 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
```task
id: BINKY-WP-0006-T05
status: todo
priority: low
```
Mark finished; log milestone; `statehub fix-consistency`.