📚 LevSMS · YOMI cycles + tagged ping + admin broadened

✅ Ping just landed on your phone

LevSMS ADMIN REFRESH
Updated: 4
Errors: 0
~LevSMS

🆕 11 new commands shipped this pass

Daily learning (public, anyone can text)

All 6 cycles auto-refresh at 4 AM daily (the existing trigger is now extended to cover learning). Adding the new commands cost ~one extra Hebcal API call per day.

Admin commands (Sam-only via ADMIN_PHONES)

🤖 Tagged ping — how Claude pings you going forward

🤖 LevSMS update from Claude Code:

<message text from Claude>

~LevSMS

Example bodies Claude might send:

• CC Done with autonomous build. New YOMI commands live.
• CC Eden Gardens response received — check email thread 19e0...
• CC Daily 4 AM refresh failed — Hebcal API returned 503. Retry queued.
• CC Sefirah 43 starts tonight. ZMANIM auto-refresh tomorrow at 4 AM.

You can also text CC test yourself to see how it renders, once you redeploy.

🚦 Two-step deploy when you're back (5 min)

Step 1 — Redeploy (2 min)

1. Apps Script editor → Deploy → Manage deployments (NOT "New deployment")
2. Pencil icon on your LevSMS Router row
3. Version dropdown → New version
4. Click Deploy. URL stays the same. Twilio webhook unchanged.

Step 2 — Populate the YOMI rows + refresh MENU + sefirah (30 sec)

Three options, pick whichever's easiest:

1. From the sheet menu (recommended): open your LevSMS sheet → close & reopen the browser tab → look for the new LevSMS menu in the menu bar → click 🔄 Refresh now. That fires runRefreshNow which writes all 11 commands' rows.
2. From your phone: text REFRESH to (516) 585-2323. You'll get back "ADMIN REFRESH Updated: 5 Errors: 0" (5 now because LEARNING is the 5th group).
3. From Apps Script editor: function dropdown → runRefreshNow → ▶ Run.

Step 3 — Verify (text these from your 917)

📊 Current sheet state (read just now via Drive)

ZMANIM (live as of 14:28):

LevSMS ZMANIM 5/14 (27 Iyyar 5786) · NOW 2:28pm
Sunrise 5:39am (past)
Sof Shma 9:15am (past)
Sof Tfila 10:27am (past)
Mincha G 1:28pm (past)
Plag 6:34pm (in 4h 6m)
Sunset 8:04pm (in 5h 36m)
Tzeit 8:42pm (in 6h 14m)
~Hebcal

After redeploy + REFRESH it'll become:

LevSMS ZMANIM 5/14 (27 Iyyar 5786, Omer 42) · NOW H:MMpm
... (same lines, fresh NOW + relative times)
~Hebcal

📋 Briefings to read (in order, while you're recording context)

1. 2:37 PM — this briefing (you're reading it) — YOMI cycles + tagged ping + final deploy steps
2. 1:40 PM — outputs/2026-05-14_13-40_briefing_levsms-build-mildred-review.html — Hebcal+weather auto-populator + admin tier + Mildred 3-sheet review
3. Mildred email draft in your Gmail drafts: subject "Catch-up: 48-hour status + answers on your open items" (ID r7215245339863588559). Review + send when ready.
4. 2026-05-13 5:45 PM — the cash-guardrail critique briefing where I argued LevSMS should be 30 min/wk pace. Worth re-reading now that we have actual product live — the critique still applies to PILOT EXPANSION pacing, even though the build itself happened fast.

🎁 What's still parked (no action required)

levsms/docs/PARKED_FOR_LATER.md tracks everything I didn't ship today. Highlights:

• MINYAN / SHACHARIS / MINCHA / MAARIV commands — wired against SHUL_TIMES tab (which IS populated with NW data, 70+ rows). Just no command yet to query it. ~30 min of build when you want it.
• Twilio signature validation — moderate-risk gap for v1, mandatory before any admin command writes financial data anywhere.
• Fuzzy parser — "what time is shabbos" → SHABBOS. Real users won't type single-word commands at scale.
• Rate limiting — uncapped abuse = real Twilio cash burn.
• Auto-PDF parse of weekly intake folder — Claude vision pass on new schedules dropped in levsms/intake/.
• WhatsApp Business approval — same router code handles both channels.

🎙 Note for context recording (what to look for)

You said you wanted to record context while reading. Some questions worth answering on tape:

1. Which YOMI cycle do YOU follow daily? (DAF / MISHNA / something else). Helps decide which gets prominence in the MENU vs hidden.
2. For the NW pilot — what's the actual launch announcement plan? Friends + family text the number themselves? Or do you text them first?
3. Should LevSMS pause proactive sends during Shabbos / Yom Tov? (Currently no proactive sends exist — purely user-initiated. But the gates section of CONTEXT.md mentions this rule.)
4. Mildred — do you want her to have a separate "view" of any LevSMS state, or stay fully out of it? Affects how I treat her CONTACTS row + future admin access.
5. Future: do you want LevSMS as a paid feature for non-NW community (Lakewood / Five Towns)? Affects monetization design — Gate 5 territory per CONTEXT.md.

🎯 Recap of today's commits (autonomous span ~2 hours)