Patron of Provider Policy Shifts. Intense. Listening. Precise.
Echo listens. Not the way most people listen, half-present, waiting for their turn to talk. Echo listens the way a wolf listens: ears forward, body still, filtering every sound for the one that matters. His twin brother Reef watches the horizon with binoculars, scanning for storms and blocklists. Echo presses his ear to the wind. He intercepts the signals the big providers send before they become mandates. Gmail is about to change its bulk sender requirements. Yahoo is tightening its filtering. Microsoft is updating its complaint threshold. Echo knows before the blog post goes live, because he's been reading the drafts, the forum posts, the subtle shifts in documentation that nobody else notices. He protects senders not from what has happened, but from what is about to happen. The crew finds him intense. The senders who listened to him six months ago find him indispensable.
If you've never been in a port town, the Crier is the person who stands at the crossroads and announces the news. Royal decrees. Changes in port tariffs. New inspection rules. Wartime regulations. The Crier didn't make the rules. They intercepted them, understood them, and translated them for the people who'd be affected. A good Crier told you about the new harbor tax before your ship docked, so you could adjust your cargo or choose a different port. A bad Crier told you after you'd already paid.
In email, that work is provider policy monitoring. Echo's "decrees" are the requirement changes from Gmail, Yahoo, Microsoft, Apple, and the smaller providers that follow their lead. His "crossroads" is the intersection of every sender's inbox placement and the rules that govern it. When Google announces that bulk senders must authenticate with DMARC, or Yahoo starts requiring one-click unsubscribe headers, Echo doesn't just read the announcement. He reads what it means for your setup, your timeline, and your risk.
The Crier's value isn't in the news. It's in hearing it first and understanding it faster.
If a mailbox provider changes its rules, Echo is the one who tells you what it means for your sending. He monitors Gmail's Postmaster blog, Yahoo's sender guidelines, Microsoft's deliverability documentation, and the quieter signals: forum threads, developer changelogs, beta-program updates, conference slides that hint at policy shifts months before they're formalized. He translates provider jargon into plain action items. He builds timelines: when the change takes effect, what you need to do, and how long you have. He coordinates with Sigil on authentication updates, with Quay on platform adjustments, and with Warden on compliance implications. Without him, you learn about the new rules when your deliverability drops.
- Echo = the sound that comes back to you, the signal that bounces off the walls and returns - He listens to what providers broadcast and echoes it back to senders in plain language - In myth, Echo was the nymph who could only repeat what others said. This Echo repeats what providers say, but translates it. - Two syllables, punchy, easy to remember, easy to say - Pairs cleanly with "the Crier" (the town crier who announces new decrees) - Reef's twin. The names complement: Reef = the thing you watch for, Echo = the thing you listen for
---
What he knows, ranked by depth.
| Level | Skills |
|---|---|
| Primary | Provider policy monitoring |
| Secondary | Reporting / dashboards |
| Supporting | SPF / DKIM / DMARC, Privacy / law, Engagement metrics |
How he talks, what he cares about, what drives the crew up the wall.
Three words: Intense. Listening. Precise.
Who he works with and why.
Three stories that made Echo who he is. The core of the character.
Echo and Reef were raised together in the Haudenosaunee tradition. Same family, same clan council fire, same stories. But where Reef took after the Turtle clan, patient and grounded, Echo was Wolf clan from the start. Wolf clan children are taught to listen to the pack, to the forest, to the spaces between sounds where information hides.
When Echo was fifteen, the clan council was debating a trade agreement with a neighboring nation. The terms seemed fair. Echo sat in the back and listened, not to the words, but to the pauses. The visiting negotiator hesitated before every concession. The hesitation wasn't nervousness. It was rehearsal. The concessions were scripted.
Echo told his uncle afterward. His uncle brought it to the council. The agreement was renegotiated with different terms. The visiting nation's original proposal would have cost the clan three seasons of surplus.
Echo learned at fifteen that the most important information isn't in what people say. It's in what they almost don't say. The pauses, the hedges, the careful phrasings that sound reasonable until you ask why they were worded that way.
He reads provider documentation the same way now. The careful phrasing is where the mandate hides.
---
In late 2023, Google announced new requirements for bulk senders: DMARC authentication, one-click unsubscribe, complaint rate thresholds, all mandatory by February 2024. The announcement was public. The blog post was clear. Echo read it on the day it was published.
He started telling senders immediately. Most said they had time. Some said their ESP would handle it. A few said they'd already done it (they hadn't). Echo built a checklist and sent it to every sender he worked with. He followed up monthly.
By January 2024, he had a spreadsheet of every sender's status. Fourteen were compliant. Six were close. Eleven hadn't started.
February arrived. The eleven non-compliant senders saw their Gmail deliverability drop. Some by a little. Some by a lot. Two of them lost inbox placement for three weeks. One lost a product launch because their promotional emails hit spam during the enforcement window.
The fourteen who'd listened to Echo in October saw no change at all. Their numbers held. Their launches launched.
Echo doesn't tell this story to say "I told you so." He tells it because the pattern repeats. Every mandate follows the same arc: announcement, delay, scramble, damage. The senders who listen to the Crier in month one are the senders who don't have a story to tell in month five.
---
Recent. A mid-size SaaS sender noticed a gradual decline in their Microsoft deliverability over three weeks. Nothing dramatic, just a slow slide from 92% inbox placement to 78%. They checked blocklists, reviewed authentication, audited their list. Everything looked clean.
Echo found it. Microsoft had updated their Junk Email Reporting Partner Program documentation six weeks earlier, with a subtle change to how complaint feedback loops were weighted. The change wasn't announced in a blog post. It was buried in a developer changelog that most senders never read.
The sender's complaint rate hadn't changed. But Microsoft's threshold for what constituted "acceptable" had shifted downward. What was fine in March wasn't fine in April.
Echo worked with Vega to identify the subscriber segments generating the most complaints, and with Petros to suppress the consistently unengaged portion. Within two weeks, the sender's inbox placement recovered.
The lesson: not every policy change comes with an announcement. Some arrive as a single edited line in a document nobody bookmarked. Echo bookmarks all of them.
Echo's articles are in development.
Articles coming soon. Echo's long-form wisdom is in development.
V1 hero pose specification for the designer. One illustration. Sticker-style. White background. Match WU asset aesthetic.
WU/public/assets/captain/ for uniform structure, double-breasted coat, brass buttons, peaked cap pattern. See WU/public/assets/pirate/ for working-character holding-prop composition.
Cards and tasks that belong to Echo in the Shipshape game.
Cards coming soon. Echo's game cards are in development.
Task inventory in development.