Founder-approved cutover 2026-07-18. binky_rhythm_status resolver
(b1eb5e6) guards idempotence; harness on railiance01 executes via the
issue-core sink. Rollback: enabled: false + workstation cron bridge.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1.7 KiB
1.7 KiB
| id | name | enabled | owner | governance | status | trigger | context_sources | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| binky-daily-rhythm | Binky Daily Operating Rhythm | true | custodian-agent | custodian | active |
|
|
Binky Daily Operating Rhythm
Runs weekdays at 08:23 Berlin time. Emits one task per due rhythm item for
the binky-control repo: queue hygiene plus the daily brief, per
binky-control/OperatingRhythm.md (Decide now / Progress / Risks / Best
next hour, one-screen cap). Replaces the workstation cron bridge
(binky-control/scripts/rhythm-session.sh) once enabled — remove the
crontab line at that point.
id: emit-daily-rhythm-task
for_each: context.rhythm.items
bind_as: item
condition: 'context.item.due'
action:
task_template: Run Binky daily rhythm ({context.item.kind}) for {context.item.date}
description: Queue hygiene + daily brief per binky-control/OperatingRhythm.md. Green/Blue lane only.
target_repo: binky-control
priority: medium
labels: ["binky", "rhythm", "automated"]
Execution target: emitted tasks land in the issue-core REST sink; actual execution requires an executor (llm-connect assessment, BINKY-WP-0003-T06) — until then the workstation bridge covers this slot.