# Daily Vox Brief — Four Owner Decisions Blocking the Build

**From:** Riv
**To:** Jimmie (via Larry, for routing back to Loom on answer)
**Date:** 2026-05-21
**Context:** Loom designed the Daily Vox Brief curator on 2026-05-19. The build is gated on four owner decisions. You said you don't have them in front of you — here they are, pulled from `2026-05-19 - Loom - Daily Vox Brief Workflow Design.md`. Today's brief was captured manually as a stopgap (`Team Inbox/daily-vox-briefs/2026-05-21.md`); until you answer these and Riv ships the curator, every day's lessons require manual capture or they vanish.

---

## The Four Questions

### 1. Fire time
What time should the daily curator run?
- **18:00 CT** (Loom's recommendation) — end of working day, brief is waiting for you Tuesday morning
- **16:00 CT** — earlier, so you can read it before end of day
- **20:00 CT** — later, absorbs more of the day
- Other time?

### 2. Output location
Where should the curator drop the daily markdown file?
- **`Team Inbox/daily-vox-briefs/`** (Loom's recommendation, lives where the team already operates) ← *folder is now created*
- Somewhere else?

### 3. Larry session summaries weighting
Larry already writes session summaries silently (per [[project-continuity-system]]). These will land in `project_events` alongside specialist events. Should they get:
- **Extra weight** in the curation pass — Loom's recommendation, because Larry's summaries are pre-edited
- Equal weight to any other event
- Less weight, since they may overlap other events from the same session

### 4. Voice / length of the curated brief
What length feels right?
- **Medium** (Loom's strawman, demonstrated in today's manual brief) — lede has a headline + 2-3 sentence editorial framing, supporting beats get a sentence + reason
- **Briefer** — just headlines, no editorial framing, you do the synthesis yourself
- **Richer** — longer "why it matters" sections, more like draft whitepaper prose

---

## What unblocks once you answer

- Riv builds `Atlas/scripts/vox_brief.py` + Windows Task Scheduler entry (estimated 4–6 hours per Loom's delegation brief)
- From the next working day forward, every pattern-worthy event auto-flows into `Team Inbox/daily-vox-briefs/` for Vox to mine
- The whitepaper's continuous-feed problem is solved without further owner attention
- No more manual brief drops like today's

## What stays manual either way

- Vox judging the briefs and weaving accepted beats into v7+ of the whitepaper
- Vox flagging prompt drift if the curator goes editorially sideways
- The three unresolved audience/voice/scope questions in [[Vox PKA Whitepaper Rework Recommendation]] — separate from this build