3 commits

Author	SHA1	Message	Date
tegwick	73cc785426	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
tegwick	b1eb5e6a55	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
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