activity-core/activity-definitions/binky-weekly-mail-intake.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

44 lines
1.4 KiB
Markdown

---
id: binky-weekly-mail-intake
name: Binky Weekly Paper-Mail Intake Check
enabled: false
owner: custodian-agent
governance: custodian
status: proposed
trigger:
type: cron
cron_expression: "37 9 * * 1" # Monday 09:37
timezone: Europe/Berlin
misfire_policy: skip
context_sources:
- type: state-hub
query: binky_rhythm_status
params:
repo: binky-control
kind: mail_intake
bind_to: context.rhythm
# Same proposed binky_rhythm_status resolver as binky-daily-rhythm; for
# kind=mail_intake, due is true when the founder's weekly scan drop
# (AWQ-008 pipeline, binky-control) has unprocessed items or no intake
# ran in the last 7 days.
---
# Binky Weekly Paper-Mail Intake Check
Runs Mondays at 09:37 Berlin time. Checks whether newly scanned paper mail
for Binky Hedgehog GmbH awaits triage (AWQ-008: drop location → naming →
obligation/deadline/receipt triage → DUO Belegablage routing) and emits one
intake task when due.
```rule
id: emit-mail-intake-task
for_each: context.rhythm.items
bind_as: item
condition: 'context.item.due'
action:
task_template: Triage Binky paper-mail scans (week of {context.item.date})
description: Run the AWQ-008 intake pipeline in binky-control; route obligations to queues, receipts toward DUO Belegablage.
target_repo: binky-control
priority: medium
labels: ["binky", "mail-intake", "automated"]
```