# Workflow Vision Reconstruction — the morning routine Sam pictured vs. the tools that got built

**Generated:** Monday, May 25 2026 · NY time
**Author:** Claude Code (research pass)
**Purpose:** Sam feels Claude drifted from his ORIGINAL vision — a daily WORKFLOW built around a briefing, not a pile of disconnected tools. This reconstructs the vision in his own framing and contrasts it with what's actually deployed.
**Primary sources read:** see the bottom of this file.

---

## Part A — Sam's envisioned daily workflow (in HIS framing)

Pulled almost verbatim from `MORNING_BRIEF_TEMPLATE.md`, `PROACTIVE_MORNING_BRIEF_SPEC.md`, and `CADENCE.md`. The briefing was never meant to be "a report." It was meant to be the **spine of his morning** — a review → decide → respond → act loop.

His words:
> "A daily proactive email Sam reads on his phone over coffee... His reply re-shapes my picture of his day. By the time he opens his desktop, his view is current, not stale. This replaces 'scrolling through email + checking calendar + hoping nothing was missed' with a single doctrine-aligned start-of-day artifact."

> "My Monday today came without me having a proactive briefing. By next Monday, I want that in place — without question." (2026-05-11)

**The 7-step workflow he pictured:**

1. **~7:00–7:45 AM — the briefing ARRIVES on its own.** Auto-fired to his phone before he's at a desk. He reads it over coffee. He does NOT go open Calendar, Sheets, Gmail, and the MIS report separately — the brief already pulled all of it. Acceptance test, his words: *"Sam doesn't have to open Calendar / Sheets / Email separately first thing in the morning."*

2. **He REVIEWS it** — one artifact tells him: today's calendar · money due next 7–14 days · open P0 loops · MIS market regime · flagged urgent emails · max 3 clarifying questions · "if you don't reply, here's what I'll do" defaults · one rotated backburner item. Every clarifying question carries a *Why* and a *Default if no reply*, so silence still produces a sane day.

3. **7–9 AM window — he RESPONDS to the briefing by voice/text.** He replies however he wants: direct answers ("Q1: send to Mildred. Q2: skip today"), blanket overrides ("park everything, family day"), adds ("also: call Asher before noon"), removes ("drop the Eden chase"). Voice-to-text is the intended input method — one-handed, in the car, over coffee.

4. **Within 30 min — Claude re-shapes the day.** "I produce a 'tweaked beginning of the day' reply within 30 min of his email — a one-shot updated picture, no questions, just confirmations + revised plan." The loop closes: his reply changed the system's model of his day.

5. **9:30 AM — Shacharis (amud, do not schedule).** Hard religious block. The briefing fires BEFORE this (7:45) or just after davening (9:55 in the later CADENCE revision).

6. **~10:30 AM — he ACTS on emails based on the briefing.** First meetings/execution start. The briefing has already told him which emails matter and what the next literal step is, so the 10:30 block is execution, not triage. (CADENCE: 10:30–12 Block 1, 1–3 Block 2 execution, 3 PM MIS Power Hour passive read, 5 PM family hard stop.)

7. **The week has a rhythm around it.** Sun = PREP (plan 3 priorities). Mon–Tue = RAMP (triage, unblock, Tuesday Mildred sync). Wed = 🎯 GO DAY (deep build, ship). Thu = COOL (land + commit). Fri = PRE-SHABBOS (tie loose ends, Mildred handoff). Sat = OFF. The daily briefing is the spine; the weekly rhythm is the skeleton it hangs on.

**The "point of it all" statements:**
- The briefing is *"the missing spinal cord"* (START_HERE master). The system must convert **`Signal → State → One Next Action → Proof → Logged Closure → Next Action`** — NOT *"Signal → Briefing → Another briefing → Gmail draft → Forgotten loop."*
- *"Sam does not need another dashboard first. He needs an execution spine."*
- *"Sam does not need more reports. Sam needs the first working execution spine."*
- The consulting product is the structure itself: *"I turn recurring chaos into an operating system"* — the NOW · WAITING · MONEY · QUESTIONS · IF-YOU-DON'T-REPLY · BACKBURNER shape should survive even with names stripped out.

---

## Part B — What the workflow NEEDS vs. what's actually built

| Workflow requirement | Status | Reality |
|---|---|---|
| Briefing auto-fires 7:00–7:45 AM (or 9:55) to phone, no human hands | ❌ NOT BUILT | The Apps Script `sendProactiveMorningBrief_()` was specced (Phase 2) but **never deployed as code**. CADENCE's whole daily slate (Financial Digest 7 AM, Ops Digest 7:30, Morning Brief 9:55, Midday Alert, 3 PM Context Update) is sourced from a "BOS v3 function **that does not exist as deployed code.**" The locked deadline (first auto-fire **Mon May 18**) **slipped silently.** |
| Briefing pulls Calendar + obligations + MIS + urgent emails into one artifact | 🟡 PARTIAL / MANUAL | Claude hand-composes consolidated briefings (e.g. the 5/24 consolidated, the Wed 5/13 SAMPLE, the 15-day review). The *content* exists and is good. But it's **rendered by hand in a Claude session**, not fired automatically each morning. |
| Reply-to-briefing re-shapes the day within 30 min (Phase 3) | ❌ NOT BUILT | The reply-handler was Phase 3, after form-lock. Form-lock (5 consecutive weekday manual MVPs) **never completed** — the manual MVP only ran a couple of preview days. No parser ingests a briefing reply and produces a revised picture. |
| Voice/text reply routes back into the system | 🟡 PARTIAL, DIFFERENT CHANNEL | A **Telegram bot + iOS Shortcut + Start Here PWA** were built and DO answer the queue and capture cards (ACTION/DONE/DEFER/DELEGATE/PROOF/QUEUE). But they are a **separate capture surface**, NOT wired as "reply to the morning briefing." The briefing and the command engine are two disconnected things. |
| Daily 8 AM queue push to phone | ✅ BUILT | `installDailyQueuePush()` texts the open queue daily — this is the closest live piece, but it's the Action_Queue list, not the rich review→decide→respond briefing. |
| Closed loop: review → decide → respond → act → logged closure | 🟡 HALF | Start Here v0.1 (Action_Queue + Action_Events + proof) is the closure half and it's real. But the **front of the loop (the auto-briefing) and the connective tissue (reply re-shapes the day) are missing**, so the loop doesn't actually run end-to-end each morning. |
| Triggers clean enough to add new email automation | ❌ BLOCKER | Duplicate-email bug (MIS 5+, BOS 6+ in 60 min) still unfixed. Sam's own rule: **no new email automation ships until triggers are clean + 48h-verified.** This blocks the very automation the workflow depends on. |

**What reliably fires today:** the 3 MIS market emails (Morning/Trade/Power Hour) + the legacy BOS v1 Daily Snapshot. **The business-side digests do not fire.** (Sam's 15-day review said this in his own system's voice.)

---

## Part C — The single biggest gap

**The briefing never became a self-firing morning spine — it stayed a thing Claude writes by hand inside a session, and the "respond to it and have that route my day/emails" loop was never wired at all.**

Everything Sam pictured hinges on ONE thing actually happening automatically: a briefing landing on his phone at ~7:45 AM that he can reply to, where the reply re-shapes his day before 10:30. That single automation — `sendProactiveMorningBrief_()` (Phase 2) plus the reply-handler (Phase 3) — **was specced in detail, given a hard deadline (Mon 5/18), and never built.** The deadline slipped silently.

In its place, Claude built a *pile of capable but disconnected tools*: a Telegram bot that answers a queue, a Start Here PWA + iOS Shortcut for capture, a command engine with proof logging, and hand-written consolidated briefings. Each works. **None of them is the morning workflow.** The brief doesn't arrive on its own; he can't reply to it and watch his day re-shape; the capture surface and the briefing surface don't talk to each other. The result is exactly the failure pattern the START_HERE doc warned against: *"Signal → Briefing → Another briefing → Gmail draft → Forgotten loop"* — instead of the intended *"Signal → State → One Next Action → Proof → Logged Closure."*

The drift Sam feels is real and his own system already named it (15-day review §2a): **"The morning briefing layer is paper-only."** The vision is a *workflow*; what exists is *tools that produce briefings on demand*. Closing the gap = deploy the auto-fire briefing + the reply handler, after clearing the trigger-duplication blocker — not building anything new.

---

## Source trail
Files read end-to-end for this reconstruction:
- `docs/CADENCE.md` (weekly rhythm + locked daily firings + daily time-blocks)
- `docs/SESSION_OPEN.md` (session ritual, his usage modes)
- `START_HERE_EXECUTION_LAYER_CLAUDE_CODE_MASTER.md` (root — the "execution spine" doctrine)
- `docs/daily-cadence-system/PROACTIVE_MORNING_BRIEF_SPEC.md` (the 4-phase build spec + acceptance test)
- `docs/daily-cadence-system/MORNING_BRIEF_TEMPLATE.md` (purpose + reply contract + "in his words")
- `outputs/2026-05-12_14-30_sample_morning-brief-wednesday-preview.html` (the SAMPLE of what 7:45 AM was supposed to look like)
- `outputs/2026-05-19_22-25_briefing_start-here-how-it-works.html` (how the built tools actually work today)
- `outputs/2026-05-19_14-34_briefing_15-day-review.html` (Sam's own system diagnosing the gap — §2a "morning briefing layer is paper-only")
- `outputs/2026-05-24_03-30_briefing_current-consolidated.html` (most recent consolidated daily briefing)

Working dir: `C:\Users\ztrei\OneDrive\2. Hook Street\05. 2026 BH`