Skip to content

2026-05-28 — Morning brief (Sam stack) killed

Decision

Tear down the morning-brief / Sam / daily-life-reply stack across all surfaces. No revival planned.

Trigger

AWS bill PDF surfaced in audit (May MTD = $434.37): $362.72 was a one-off Claude Code experiment Devin already deleted, but the underlying morning-brief stack (24/7 EC2 + EIP + Bedrock-routed LLM calls + CF Worker reply queue) was the host for that experiment and the long-running cost driver.

What was killed

Cloudflare (account aea242a268ed4cbc039211786a57cc00, via wrangler): - Worker daily-life-reply — DELETED 2026-05-28 - KV namespace daily-life-replies (id abd55acb1ed34d35a1269ffb1e04e8c0) — DELETED 2026-05-28

~/.claude/.env block removed: - NTFY_TOPIC, NTFY_SERVER - GCAL_PRIMARY, GCAL_FAMILY - MORNING_BRIEF_TIME, EVENING_WRAP_TIME - REPLY_TOKEN, REPLY_URL - GMAIL_APP_PASSWORD, GMAIL_FROM, GMAIL_TO - (CLAUDE_BIN kept — used by other tooling)

AWS teardown — COMPLETE 2026-05-29 (Devin via Console): - ✅ EC2 t4g.small terminated - ✅ Elastic IP released (was already gone when checked — auto-released on termination) - ✅ EBS gp3 volume vol-0037ad9e8475c171b deleted - ✅ Bonus: IAM user renamed nanny-pics-rekog → kindredpics-rekog via CloudShell aws iam update-user - Expected June bill drop: ~\(400/mo recurring recovered (\)362.72 Bedrock + $37.68 Rekog + $7.92 EC2/EBS/EIP all eliminated)

Canonical patches

  • active/stampready.md line 26 — morning brief struck from build order with kill date
  • active/stampready.md line 87 — "morning-brief" removed from paywall policy list
  • ~/.claude/.env — block deleted

Memory implications

  • reference_global_env_location.md — still valid (cross-venture creds at ~/.claude/.env)
  • No new memory entry needed; this decision file is the durable record.

Reversal

Restoring the morning brief would require: re-create CF Worker + KV + script logic from vault history (Claude Transfer Files/Claude Memory/project_daily_life_system.md), re-add env vars, re-provision EC2 in us-west-2 or migrate to a Cloudflare Cron Worker instead.

Per Devin: no revival planned.