activity-core/activity-definitions/binky-daily-rhythm.md
tegwick b2fa9642b6 feat(definitions): propose Binky operating-rhythm definitions (disabled)
Three proposed, disabled definitions for the binky-control rhythm
(BINKY-WP-0003-T05): daily rhythm, weekly paper-mail intake, weekly
founder-review prep. All parse via definition_parser. Enabling requires
the proposed binky_rhythm_status state-hub resolver and an executor
(llm-connect assessment, BINKY-WP-0003-T06).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 11:02:29 +02:00

49 lines
1.7 KiB
Markdown

---
id: binky-daily-rhythm
name: Binky Daily Operating Rhythm
enabled: false
owner: custodian-agent
governance: custodian
status: proposed
trigger:
type: cron
cron_expression: "23 8 * * 1-5" # weekdays 08:23
timezone: Europe/Berlin
misfire_policy: skip
context_sources:
- type: state-hub
query: binky_rhythm_status
params:
repo: binky-control
bind_to: context.rhythm
# Proposed resolver (not yet implemented): returns
# {items: [{kind: "daily_brief", due: bool, date: "YYYY-MM-DD"}]} — due is
# true when no brief exists for today in binky-control/briefs/. Implementing
# it is part of the BINKY-WP-0003-T06 follow-up workplan proposal.
---
# 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.
```rule
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.