coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(resolvers): binky_rhythm_status query in state-hub resolver
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

Browse source 
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>
This commit is contained in:
tegwick 2026-07-17 17:07:00 +02:00
parent a2c53508ad
commit b1eb5e6a55
5 changed files with 282 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

8
activity-definitions/binky-weekly-mail-intake.md
View file

@ -17,10 +17,10 @@ context_sources:
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.
# 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