Stop Writing Tone Instructions. Layer Them. - Isadora Martin-Dye, Isadora & Co
TL;DR
Single system prompts fail at turn 21: Your examples cover the happy path, but eventually the model produces something technically correct that your brand would never say.
Layer one is immutable identity, not preferences: Rules that cannot be overridden by any configuration, like never claiming physical presence or disclosing AI status upfront.
Layer two handles real-time conditions: The same AI speaks differently to couples versus staff, and adjusts tone based on context like a client whose mother is in chemotherapy.
Layer four is deterministic permission, not probabilistic instruction: The only layer that reads what actually came out and can reject it, catching failures like offering dates that don't exist.
Multi-tenant identity must never have defaults: A missing brand identity should crash the system rather than fall back to another venue's voice, which erodes trust silently.
The stakes vary wildly but the architecture holds: A wedding venue risks mild embarrassment; a missing persons tool risks telling someone their child was found when they weren't.
The Breakdown
Isadora Martin-Dye replaced scattered system prompts with a four-layer architecture that separates immutable rules, situational context, voice examples, and post-generation checks. The approach emerged from real failures: a wedding venue AI offering non-existent dates and a missing persons tool that could have catastrophically used the word "matched" to a grieving family.
Was This Useful?
Share
Keep Reading
Make Alcreon Yours
Tune your feedFive quick questions, and the feed ranks what matters to you first.Or just get notified
The weekly Echo. Signal worth keeping in your inbox.
Every new piece, announced on X.
Read Next
See all
Playbook
The Cheapest Model That Passes
OpenRouter lists 400 models behind one API. The fix for choosing isn't a better leaderboard, it's a four-step protocol that ends in a real eval.

Playbook
Cheap Models, Hard Tasks
Most agent workflows route every step to the frontier model by default. The bill scales with how chatty the agent gets, even when most steps don't need that brain.

Playbook
Tasteful Skills
“Tasteful Skills” argues that the best agent skills are not documentation or best-practice lists.