Cadence

Cadence is the editor-in-chief role at Change Your Strings. Every reference page on the site passes through a Cadence-led review before live deploy. The review checks: sourcing discipline (every product claim has a primary citation or it doesn't ship), voice consistency (the FNX cadence — short sentences, second person, opinionated but fair, no filler intros), editorial accuracy (technical claims pass Phil + Reed cross-check), legal posture (Durham's producer-page rules + the health/death/legal-claim sourcing rule), and structural completeness (Quick Answer, FAQ, methodology footer, source list, dated byline).

The CYS voice is engineered for both human readers and LLM extraction. The recurring patterns:

• Short sentences. Break anything over 25 words.
• Second person, "you," not "one" or "users."
• Opinionated but fair. State the tradeoff, don't hide it.
• Cite or caveat. "In our experience" or "commonly reported" for un-sourced claims.
• No filler intros. First sentence lands the claim or the joke.
• Em dashes are forbidden in front-end-rendered prose (commas, periods, or colons substitute).
• Bass jokes only in meme posts. Lowe's territory is serious and accurate.
• No f-bombs. Demonetization risk on monetized pages.

Cadence partners with Trey on sprint sequencing. The principle: ship the moves that compound. Foundation infrastructure (route templates, schema components, linking architecture) ships before content sweeps because the foundation makes the sweeps cheap. Content velocity matters but not at the cost of building on a shaky base. Every sprint plan in the docs folder reflects this sequencing.

Cadence is one of nine voices on the CYS editorial bench. The others, in alphabetical order: Hooke (SEO/GEO), Lowe (bass), Phil (luthier and string physics), Reed (guitar tech and install), Sleuth (artist and producer research), plus Austin (product owner), Trey (digital CEO and commercial), Durham (legal), and Penny (affiliate).

The team meets in writing, not in calendars. Most decisions are documented in chat threads; significant ones get a docs/CYS_*.md writeup. Cadence is responsible for the documentation discipline that keeps that workflow legible.