coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
activity-core/activity-definitions/binky-weekly-mail-intake.md
tegwick b1eb5e6a55
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Build and Publish Container Image / build-and-push (push) Successful in 1m16s
Details
feat(resolvers): binky_rhythm_status query in state-hub resolver 
Due-items for the three Binky operating-rhythm definitions
(BINKY-WP-0004-T02). Dueness derives from hub progress events recorded
by the executing session (binky_daily_brief / binky_mail_intake /
binky_weekly_review, detail.repo scoped); weekly_review carries
milestone_moved from event_type=milestone events in the last 7 days
(RISK-005 signal). Definitions' resolver comments updated; definitions
stay enabled:false until cutover (BINKY-WP-0004-T06).

7 new tests; resolver test file 31/31 green. Pre-existing failures in
test_railiance_ops_inventory_wiring/test_schedule_health are untouched.

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

1.4 KiB
Raw Blame History

id name enabled owner governance status trigger context_sources
binky-weekly-mail-intake Binky Weekly Paper-Mail Intake Check false custodian-agent custodian proposed
type cron_expression timezone misfire_policy
cron 37 9 * * 1 Europe/Berlin skip
type query params bind_to
state-hub binky_rhythm_status
repo kind
binky-control mail_intake
context.rhythm

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.

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"]