eea17a7abc
BINKY-WP-0003-T06: llm-connect executor assessment; workplan done
...
llm-connect = engine (adapter library), kaizen-agentic WP-0006/ADR-005 =
persona + schedule-prepare convention, activity-core = scheduler with a
stub TaskExecutorWorkflow. Missing piece: one thin executor worker on
Railiance. Follow-up workplan proposal (BINKY-WP-0004 candidate) included.
All six WP-0003 tasks done.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 14:04:59 +02:00
89754611f0
BINKY-WP-0003-T05: activity-core wiring — 3 proposed definitions landed
...
Deployment verified: production-backed on Railiance, issue-core REST sink,
TaskExecutorWorkflow still a stub (llm-connect's slot). Definitions landed
disabled in activity-core commit b2fa964; enablement needs the
binky_rhythm_status resolver + an executor.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 14:04:37 +02:00
bc49a24c4c
BINKY-WP-0003-T01: company email → OpenBao integration plan (AWQ-007 prep)
...
Vault path prod/binky/company-email/imap, secrets-engine catalog draft,
email-connect read-only IMAP wiring. Credential handover stays a single
Red-lane founder step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 10:50:29 +02:00
