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).
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.
Convention change, not new code: closing an item now means setting its
terminal status (status: closed/resolved/done + outcome where
applicable) directly on the item's own yaml block in place, instead of
deleting it and hand-writing a bullet in a separate "Completed"/
"Resolved decisions" log. WORK-RECORDS.md (CUST-WP-0061-T04, generated
by fix-consistency's C-33) already lists every closed/resolved/done
record with status/lane/source -- that supersedes the hand-maintained
logs as the going-forward view.
- AutopilotWorkQueue.md: closing note added; "## Completed" relabeled
"(historical -- pre-canon, 2026-07-21)", frozen as-is, nothing
migrated or deleted
- DecisionQueue.md: closing note added -- its "## Resolved decisions"
entries were already structured as in-place yaml blocks with
status: resolved (ahead of AWQ's convention already), so this only
clarifies the log is superseded going forward, no structural change
- OfficeHourQueue.md: closing note added -- items already live under
"## Queued items" with status: queued|prepared|done in place, no
separate log ever existed here
- OperatingRhythm.md: queue-hygiene checklist updated to describe
in-place status transitions instead of "moved to the log"; added
item 5 noting WORK-RECORDS.md needs no hand-maintenance
Re-ran fix-consistency: WORK-RECORDS.md content unchanged (correctly
idempotent -- these were prose-only edits, no yaml block content
changed).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Crontab line active (weekdays 08:23). chmod +x had been lost when the
original install command was denied — without it every cron run would
have failed silently.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Headless lane-restricted rhythm session script and enable/disable docs in
OperatingRhythm.md. Crontab installation itself is a one-line founder
action — the permission layer refuses agent-installed persistence, which
is the correct boundary.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
OperatingRhythm.md (daily brief format, queue hygiene, weekly review),
AutopilotWorkQueue.md seeded with 6 evergreen items, first daily brief
written for 2026-07-16.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
