scope: client-account - Rye Valley delivery decision about how we write Longevity Code newsletters.
- Date: 2026-10-08
- Decider(s): Michael Houck (confirmed), Blake Stewart (recommended)
- Status: decided
Decision
Megaphone Studio should draft Longevity Code newsletters to match the format Warren’s live (published) issues use, not the voice bible. The two conflict; live issues win.
Context
Hermes posted a ruling request to Megaphone because the voice bible and Warren’s actual published issues diverged enough to create ambiguity about which to follow. Blake Stewart recommended live issues: Warren references past posts in recent emails, suggesting he expects stylistic continuity. Blake also noted the account was passed along with minimal context, Warren has not reviewed any drafts sent in the past month, and he’s an exacting client (per prior inbox note).
Michael confirmed Blake’s recommendation with a one-word “I agree.”
Consequences
- Studio defaults to live-issue format for all future Longevity Code drafts
- Voice bible is secondary reference only (use for gaps where live issues give no signal)
- No human review in 30 days is a watch flag - Blake owns the client relationship and should monitor for engagement or churn signals