activity-core/activity-definitions/binky-weekly-mail-intake.md
tegwick 73cc785426
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s
Build and Publish Container Image / build-and-push (push) Successful in 9s
feat(definitions): enable Binky operating-rhythm definitions (DEC-2026-003 cutover)
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>
2026-07-18 14:33:21 +02:00

44 lines
1.4 KiB
Markdown

---
id: binky-weekly-mail-intake
name: Binky Weekly Paper-Mail Intake Check
enabled: true
owner: custodian-agent
governance: custodian
status: active
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
# Resolver implemented (BINKY-WP-0004-T02); for kind=mail_intake, due is
# true when no binky_mail_intake progress event was recorded in the last
# 7 days. (Unprocessed-drop detection stays with the executing session —
# the AWQ-008 drop dir is outside hub visibility.)
---
# 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"]
```