2fbbf9fc76
BINKY-WP-0006: close with three clean railiance mail cycles
...
Work Records / validate (push) Has been cancelled
Host LLM_CONNECT_URL discovery uses ClusterIP when DNS is unreachable;
mail path fails hard if triage fails. Mark T06 done and workplan finished;
update residual docs (OperatingRhythm, cutover runbook, llm-rhythm).
2026-07-22 10:28:11 +02:00
88a4886ea7
BINKY-WP-0006: retarget Railiance rhythm to llm-connect/OpenRouter
...
Work Records / validate (push) Has been cancelled
Reject Claude Code (or any coding agent) on railiance01. Mail-scan stays
deterministic; triage/briefs use llm-connect HTTP → structured JSON →
deterministic apply. Document in integrations/railiance-llm-rhythm.md and
rewrite WP-0006 tasks accordingly; timers no longer require_claude.
2026-07-22 00:00:04 +02:00
c3ea150971
BINKY-WP-0004 finished: retire workstation cron, Railiance rhythm timers
...
Work Records / validate (push) Has been cancelled
Complete T06 cutover: remove binky rhythm bridge crontab, install
scripts/railiance-rhythm systemd user timers on railiance01 (Europe/Berlin),
document residual continuous-intake gaps as BINKY-WP-0006. Three completion
event types verified (daily_brief, mail_intake on Railiance, weekly_review).
DEC-2026-003 marked resolved/executed.
2026-07-21 23:51:43 +02:00
80923a519b
cutover executed: definitions live, deploy key attached, bridge paused
...
DEC-2026-003 deployment 2026-07-18: image with resolver + enabled
definitions imported to railiance01 k3s, sync 20/20 upserted, Temporal
schedules reconciled (3 Binky schedules live), cron bridge paused for
the Mon-Wed verification window.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-18 15:51:36 +02:00
b6c583f411
cutover runbook: deploy-key attach via warden lane, not founder UI clicks
...
Per ops-warden INTENT §7 / WARDEN-WP-0029 (founder directive 2026-07-18).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-18 14:27:23 +02:00
efe4e55e6a
feat: agent-harness tenant #1 instance manifest (HARNESS-WP-0001-T07)
...
Extend .kaizen/schedule.yml with harness fields for daily rhythm, weekly
mail intake, and weekly review-prep; add task files, onboarding handoff
doc, and cutover gate updates for BINKY-WP-0004-T06.
2026-07-18 11:07:12 +02:00
7c5e644d6f
DEC-2026-002 resolved: agent-harness (single shared runtime)
...
- DecisionQueue: moved to resolved log with rescoped outcome (three-layer
model; binky-control = tenant #1 ); hub decision resolved
- Secret lanes doc: identifiers renamed executor-worker → agent-harness
before any provisioning happens
- Cutover runbook + WP-0004-T06: gate 1 done; deployment gate now points
at HARNESS-WP-0001-T06/T07 in the agent-harness repo
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 23:37:16 +02:00
02a8d293ab
BINKY-WP-0004 T04/T05 done, T06 blocked with cutover runbook
...
- T04: executor-worker MVP (new repo ~/executor-worker) ran one task
end-to-end: kaizen schedule-prepare persona, agentic llm-connect
session, sandbox commit e043f21, hub progress event
- T05: recurring mailbox scan fully wired (two-phase: deterministic
credentialed scan + LLM triage session with suspicious-mail log-only
rule); email checklist item 9 now gated only on Lane 3 AppRole
- T06: blocked — gates are DEC-2026-002, Red-lane Lanes 2/3, Railiance
deploy, 3 verified runs; runbook at
integrations/executor-cutover-runbook.md
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 17:17:15 +02:00
