status: pass 4 COMPLETE — all sections (§0-§11) closed for pass 4 — §3 venue gaps closed (HK Yardbird/Pak Loh/Lung King Heen + Tokyo Sazenka + Narisawa-expanded + LatAm Quintonil/Don Julio + Amsterdam Choux/DS/Flore + new RAI-adjacent peer Showw); §3.3 patterns 5→9 (Sazenka wakon-kansai + four-kanji menu + Yardbird single-illustrator + Don Julio Art-of-Hospitality); §3.4 patterns 3→4 (Lung King Heen 2023 demotion → hotel-anchored single-narrator-dependency anti-pattern); §4 Q1 2026 GEO baseline measured = 0.00/9-query-sample (Michiu invisible across all discovery-intent queries) — §4.1.1 new + §4.2 audit-checklist verified-where-possible + §4.4 Tier-4 awards-pipeline added + §4.5 baseline replaces TBD + new §4.6 Q1 P0 priorities; Sazenka philosophy-name gates the §4.3 Sep-2026 position essay AND the title-tag rewrite; only desk-research-impossible Yama remains open in §3; §11.1 hypotheses remain external (owner/eng-bound) prompt_version: v4 primary_market: Netherlands (Amsterdam + Randstad). International / RAI-event tourist segment is secondary. audience_tiers:

• Status Builders (25-40, IG-native, Amsterdam locals, save-and-share)
• Classic Connoisseurs (45-65, taste-led, returning, press-and-search readers)
• Corporate Bookers (30-55, decide where the group eats, LinkedIn-primary, RAI-adjacent) sources_global:
• Brandwatch — Digital Marketing Trends 2026 (1,000+ marketers surveyed, 18M+ conversations analyzed, Jan–Oct 2025)
• HubSpot — State of Marketing 2026 (1,500+ global marketers)
• Sprout Social — 2026 Social Media Trends + Social Intelligence Report
• Kantar — Media Reactions 2025 + Marketing Trends 2026
• National Restaurant Association — 2026 State of the Industry (US benchmark only)
• Restaurant Dive — 2026 outlook coverage (US benchmark only)
• McKinsey — What US Consumers Want from Restaurants in 2026 (US benchmark only) sources_netherlands:
• DDMA — Barometer 2025 / Marketing Focus 2026 (Dutch digital media reduction trend)
• KHN (Koninklijke Horeca Nederland) — Stand van de Horeca 2026 (sector volume vs. value)
• FSIN (Foodservice Instituut Nederland) — Foodservice Monitor 2026 outlook
• DataReportal — Digital 2025 Netherlands (social media penetration + channel mix)
• PostSimple — Social Media Usage in the Netherlands 2026 (NL platform-specific breakdown)
• Deloitte NL — Dutch Digital Consumer Trends
• Lightspeed / Eijsink / Chefs Culinar / Vangeloven — NL horeca trends 2026 (operator-side compendium)
• MarketingTribune — Horecava 2026 awards + trends coverage authoring:
• Drafted by Claude (Opus 4.7) against Michiu-2026-Marketing-Strategy-Prompt-v4.md
• Voice grounded against src/brand/review-prompt.ts v2.0, src/brand/dm-prompt.ts v1.0
• Repo state at draft: HEAD = 84e88a1 (2026-05-11)
• NL-market layer + 3-tier audience map added in pass 1 patch after user feedback (2026-05-11)

Michiu 2026 Marketing Strategy — Baseline

[!note] Document status Pass 4 COMPLETE — all 12 sections (§0-§11) closed as of 2026-05-11. All sections (§0–§11) drafted; pass-4 closed every remaining §3 benchmark gap that was closable via desk research AND closed §4 (GEO action plan) — measured Q1 2026 baseline at 0.00 mentions across a 9-query sample (Michiu invisible to LLM discovery-intent queries; brand-name search works), audited the michiu.nl surface from external signals (site 503-blocking direct WebFetch, suspected Cloudflare bot-challenge), and surfaced 7 immediate Q1 P0 fixes in §4.6 (title-tag, IG bio, Yelp category, GBP category, crawler reachability, LinkedIn company-page creation, about-us body rewrite — last two added by §5 work). §5 added cross-channel deployment rules (§5.0.1 — Sazenka philosophy-name everywhere; Yardbird single-illustrator visual identity; Quintonil dual-brand; Lung King Heen distribution-failure as cadence governor), a current-state audit (§5.0.2 — including the critical finding that no Michiu LinkedIn company page exists and TikTok content currently violates §1.1), and rebuilt §5.5 as LinkedIn + Press (Penn-owned) with explicit LinkedIn pillars and cadence. Two pass-4 findings flagged for owner: (a) verified 2012 founding date / 14-year operating runway extends the heritage card; (b) €25/p packages on businessrestaurants.nl directory may undercut the §0 shift #2 premium positioning. §6 synced to shipped reality (new §6.0 implementation-state inventory: 10/10 helpers live, 13 migrations applied 0030–0052 + 0053 Campaigns in-code-pre-apply; Sun's cultural_moment_t_minus_6_weeks is the first live draft-emitting loop end-to-end). Pass-2's proposed migration numbers (0030-0035) corrected to actual (0038-0044). New §6.8 spec'd three pass-4-derived schema additions at migration-paste level: brand_audiences.philosophy_name column (0054), brand_visual_identity table (0055), awards_pipeline table (0056). Closed in pass-4: HK cluster (Yardbird ✓ / Pak Loh ✓ / Lung King Heen ✓ — including the 2023 3→2 star demotion, now §3.4 pattern 4), Tokyo (Sazenka ✓ — surfaces §3.3 patterns 6 + 7 as Michiu's nearest 3-star structural twin; Narisawa expanded ✓), LatAm (Quintonil ✓ / Don Julio ✓ — surfaces §3.3 pattern 9), Amsterdam premium peers (Choux ✓ / Restaurant DS ✓ / Flore — the venue formerly known as Bord'Eau, rebranded under Bas van Kranen April 2025 ✓), plus Restaurant Showw newly identified as the proximal RAI-adjacent Michelin peer (Gelrestraat 28, missed in passes 1–3). §3.3 ADOPT 5→9; §3.4 AVOID 3→4. Single highest-leverage pass-4 finding: Sazenka's "wakon-kansai" named-philosophy framing (§3.3 pattern 6) → Michelle's position-essay (§4.3 Sep 2026) should land a Michiu-coined philosophy-name before Penn pitches Tier-1 press. Remaining open: Yama (desk-research-impossible — owner/Chef-Chau input required) and §11.1 Q1 hypotheses (external, owner/eng-bound). Earlier passes: pass-3 (Den/Ikoyi/Humble Chicken/Endo; §4.4 NL press critic verification — Broekaert/Grimm/Versprille).

[!warning] Primary market Most Michiu clients are Dutch (Amsterdam + Randstad). International / RAI tourist guests are a real but secondary segment. When global trend reports (Brandwatch, HubSpot, NRA, McKinsey US) and NL-specific data diverge, the NL data wins for tactic prioritization. The 2026 NL signals are sharper than the global averages — see §1.8 and the per-trend NL sub-bullets.

0. Executive summary

The 2026 strategic shifts (6)

1. Stop describing what we are. Name what we cook. Across every source — Brandwatch (AI slop mentions +200% in 2025, 82% negative)¹, HubSpot (audiences reward "authentic, helpful, human")², Sprout (52% of social users concerned about undisclosed AI content)³, Kantar (60%+ worry generative AI enables misleading ads)⁴ — the same wall is going up: generic, polished, adjective-heavy restaurant content reads as machine-generated in 2026. The defense is visible craft and named specifics. Hokkaido uni, not "premium uni." 45-day dry-aged Wagyu, not "carefully aged beef." Cantonese aged soy from our supplier in Hong Kong, not "our special sauce." This is already encoded in our review-reply prompt⁵ — extend it across every outbound surface.

2. Own the corporate-dining lane near the RAI. Three Asian-cuisine restaurants on Scheldestraat are within 400–600m of us; none have an active B2B strategy or LinkedIn presence⁶. 60% of US restaurant operators reported traffic declines in 2025⁷ and McKinsey records higher-income consumers driving disproportionate growth while lower-income retreat⁸ — the strategic answer is to go up-segment, not down. Build the Penn-led editorial + LinkedIn outreach motion to event planners and EAs running the Money20/20, IBC, KubeCon, GreenTech and PLMA dinners. The local competition has 1,700 IG followers and cancels reservations⁶. This is uncontested.

3. Make the cast the brand. Brandwatch⁹ and Kantar¹⁰ both report employee-led content outperforming brand-channel content (employee shares = 30% engagement lift, 2× CTR; 61% of marketers planning to increase creator-content investment in 2026). Our cast is pre-built: owner-chef Michelle, the sous team, the sommelier, the pastry lead, FOH. Zuck assists; the cast contributes. Not influencers — us.

4. Activate the gamification pillar inside the lunch daypart — through gesture, not framing. Variable-reward mechanics (Brandwatch's "little treat" trend hit 40k+ monthly mentions¹¹; restaurant nostalgia + comfort tops the NRA 2026 culinary list¹²) work only if they read as hospitality, not as a loyalty program. The Circle-dice in lunch lands as a gesture a guest tells a friend about; the moment we name the system, we collapse into the same category as every points-and-perks scheme. See §1 principle 3 and the banned-phrase list¹³.

5. Build the GEO citation moat before the LLMs lock in their top-three. 67% of marketers say search behavior is shifting toward AI/social discovery¹⁴; 41% of Gen Z search social first¹⁵; Reddit and LinkedIn are now in the top-5 LLM-cited domains¹⁴. For Michiu specifically: the queries that matter ("best omakase in Amsterdam under €150", "restaurant near RAI Amsterdam business dinner", "Cantonese-Japanese Netherlands") have no established LLM answer set yet. Six months of long-form chef + dish + sourcing content on michiu.nl, Reddit-cultivated mentions, and targeted Dutch-press citations (Het Parool, NRC, Misset Horeca) put us in the answer set before competitors notice the lane exists. Highest-leverage tactic in this document.

6. Design for the Dutch "less but more meaningful" 2026 mood. The NL signal is stark and consistent across DDMA¹⁶ and FSIN/KHN¹⁷: 35% of Dutch (47% Gen Z+Millennial) want to reduce digital use, 67% expect that reduction to be permanent; hospitality volume +1% with turnover +3.8% — guests visit less often but spend more per visit and expect each visit to be memorable. This is the headline NL mood of 2026. It maps directly to Michiu's structural position (we are not the everyday spot; we are the deliberate decision) and it raises the bar on every gesture-per-visit (§1.8). Tactics that demand high attention from guests (phone-free supper club, chef's-note menu, the dice) are weather-aligned with the Dutch mood; tactics that demand frequent low-engagement touches (daily IG posts, generic promo emails) are weather-against. Reorder the operating cadence accordingly.

The single highest-leverage move: the GEO moat (shift #5). Every other tactic in this strategy needs Michiu to already be in the LLM's answer set when a Status Builder or Corporate Booker asks the question. If Pillar 3 work doesn't land, none of the other shifts compensate.

The single biggest risk: the team treats the Marketing OS as production-ready when it isn't. The 10 helpers can draft — they cannot post. Per hard rule #6 in CLAUDE.md and decision D16 (graduated autonomy rejected, 2026-05-10), every output flows through the Universal Approval Queue forever. If anyone proposes a "set-and-forget" tactic, that tactic dies at the queue. Brand safety > efficiency.

The single capability the OS doesn't yet have that this strategy requires: the public.click_tracking table is specced in docs/marketing-attribution-strategy.md but not migrated. Until the migration ships AND the Zenchef booking widget's metadata pass-through question is resolved (marketing-attribution-strategy.md:42)¹⁸, the entire "tactic X drove €Y in revenue" measurement loop in §6 and §10 is hypothetical. Engineering pre-req before campaign-level attribution claims are defensible.

1. Strategic principles

Seven principles, ordered from most-load-bearing to most-tactical. Each is pressure-tested against the question: would a generic Amsterdam restaurant write the exact same thing? If yes, it was cut.

1.1 Specificity is the moat

In an environment where 200%+ growth in AI-slop mentions¹ and 52% of social users worry about undisclosed AI content³ are simultaneously true, the only durable differentiator is the named, the dated, the sourced. Not "premium sake" — Tokubetsu Junmai from Kameizumi, decanted at the table. Not "fresh fish" — the line-caught hamachi we got Tuesday. Not "chef's special" — Michelle's pork-belly-and-Hokkaido-scallop dumpling that's been on the menu since opening. This rule already governs our review-reply prompt⁵; every helper, every channel, every caption must extend it. Adjectives are the enemy. Nouns and dates are the moat.

1.2 Three "felt, never told" rules are one principle at three layers

The Circle, the positioning, and the gamification mechanic share a single underlying rule: the guest experiences the thing without being told the thing exists. A guest at Adept tier doesn't read "you are at Adept tier" — they notice their table is the one by the window again. A guest does not read "Amsterdam's new home for success" — they notice they're sitting next to a managing partner closing a deal. A guest who rolls the lunch dice doesn't read about a "rewards program" — they read about the dice. The umbrella, the framing, the program-name are all banned outbound (brand_banned_phrases v2026.1 — see §6 Pillar 4)¹³. The artifact, the gesture, the moment are encouraged. This is hospitality. The alternative is marketing.

1.3 The gesture, not the system

Specific to gamification — but worth its own principle because gamification is the new pillar and the failure mode is named. The dice is a noun. The roll is a verb. The sake wheel is a noun. The surprise pour is a moment. Gamification, loyalty rewards, earn points, level up, unlock perks, spin to win, play our game are system-language that names what's happening, and naming it collapses it into discounting-by-another-name (which the owner has explicitly distinguished it from). The mechanic works to the exact extent that it doesn't announce itself. First production instance: Circle-dice in the lunch daypart — see §2 trend 4 and §5 channel playbook (in pass 2).

1.4 The cast is the brand

Brandwatch reports 30% engagement lift and 2× CTR for employee-shared content vs. company-channel content⁹; Kantar records a net 61% of marketers planning to increase creator spend in 2026¹⁰; HubSpot finds 22% of marketers cite expanding from text into visual/audio formats as the most effective 2025 diversification¹⁹. Michiu has the cast already: owner-chef Michelle, the sous team, the sommelier, the pastry lead, the FOH team. The 2026 work is not finding influencers — it is making the cast camera-ready. Zuck assists with framing and scheduling; the content originates from the people who do the work. This is a structural advantage over restaurants whose chefs do not want to be visible.

1.5 Human-in-the-loop is permanent

Brand safety > efficiency. Trust scores exist (§6, Insight helper) as an audit metric — they are never an autopost unlock. Decision D16 (2026-05-10) explicitly rejected graduated autonomy²⁰. Every output from every helper — including Siren's 47-th-consecutive-unedited-approval reply — flows through the Universal Approval Queue. The math is asymmetric: a single off-brand autopost during an allergen incident, PR crisis, or tone drift costs more than the cumulative time saved by all prior automated approvals combined. This is not a constraint we are working around. This is the moat.

1.6 Attribution closes or the tactic is brand-only — honestly labeled

Per the privacy-first attribution architecture¹⁸: every paid or organic tactic that touches the website routes through m_campaign (organic) or gclid (Google Ads) → public.click_tracking row → matched to the Zenchef reservation.created event by booking-flow click-id pass-through (primary, pending Zenchef widget answer) or hashed_email/hashed_phone SHA-256 fallback → POS revenue. We measure exact € ROI per post and per ad. Tactics that genuinely cannot be attributed — in-restaurant moments, Circle gestures, brand-level press — get labeled "brand-only" honestly and paired with a leading indicator that is measurable (GBP photo views, Reddit thread surface count, EGC volume). 33% of marketers cite ROI measurement as their #1 challenge²¹; we have built around that, and we should not hide the parts where we still can't measure.

1.7 Cantonese-Japanese is a position, not a hyphen

The cuisine order matters because the brand answer to "why these two cuisines together" is the brand. Cantonese first because it is the chef's lineage; Japanese second because it is the technique grammar applied. Every outbound surface needs to be able to answer the question without resorting to the word fusion (which is banned and which signals the AI-slop genre)¹³. The 2026 work in §4 (GEO content roadmap) and §5 (channel playbook) is to publish the answer to that question in 4–6 long-form pieces on michiu.nl — sourcing essays, dish-origin essays, the chef's lineage essay — that show up in LLM grounding when the question is asked.

1.8 Less, with more weight (the Dutch 2026 mood)

In the Netherlands specifically, 2026 is the year of fewer-but-meaningful — across digital media, restaurant visits, and ad attention. DDMA's Barometer finds 35% of Dutch (47% Gen Z+Millennial) are actively reducing digital media use, with 67% expecting that reduction to be permanent¹⁶. FSIN and KHN report NL hospitality turnover +3.8% but volume only +1% — "guests visit less often but expect each visit to be meaningful, thoughtful and memorable"¹⁷. The average Dutch person uses 2.0 social platforms daily, down from 2.4²². The same consumer who wants more peace and more offline time is also the one who, when they do book a restaurant, is choosing the place that earns the night. This is structurally Michiu's lane. The operating implication: reduce posting frequency to favor depth. A weekly piece of substance beats four daily filler posts in 2026 NL. Cadence is a brand decision, not a default. Zuck's content calendar in §5 (pass 2) will be rebuilt around this.

1.9 Audience tier × 2026 trend resonance map

The 2026 strategy addresses three audience tiers, each with distinct channels, decision rhythms, voice anchors, and trend resonances. Every tactic in §2–§11 should name which tier(s) it primarily addresses (pass-2 work). The grid below summarizes the per-tier trend-fit so that pass-2 tactic tagging is mechanical.

How to read the map: when a tactic in §2 is drafted (or re-tagged in pass 2), it must name which tier(s) it serves. A tactic that hits Status Builders only is fine; one that tries to hit all three usually hits none well. Trends with weak fit for a tier are not "skip the trend for that tier" — they're "skip the trend as the primary lens for that tier and use it secondarily."

Per-tier 2026 reordering of strategic shifts:

• For Status Builders: shifts #1 (specificity), #3 (cast is the brand), #4 (gamification gesture) are highest-leverage. The Dutch 2026 mood (#6 shift, "less with more weight") amplifies all three.
• For Classic Connoisseurs: shifts #1 (specificity), #5 (GEO moat — they Google), #6 (Dutch less-but-meaningful) are highest-leverage. The cast (#3) shows up via press cites, not IG.
• For Corporate Bookers: shifts #2 (RAI corporate lane), #5 (GEO — they Google for "near RAI"), #6 (Dutch hospitality value-over-volume implies they pay properly) are highest-leverage. The cast (#3) shows up via Michelle's LinkedIn voice.

1.9.1 Dietary dimension — Status Builders specifically (owner-confirmed 2026-05-11)

A meaningful subset of the Status Builders tier is Muslim; a small sub-subset additionally prefers halal meat. The owner-confirmed operating posture is parallel non-pork visibility everywhere — not "no pork" and not "afterthought non-pork option," but EVERY SB-targeted surface has a non-pork hero at equal visual hierarchy to any pork-led content.

Concretely:

• IG / TikTok craft clips (Tactic 1.1) — if a pork dumpling clip runs in a week, a non-pork dumpling clip (chicken-shiitake, prawn-chive, lamb-cumin) runs the same week at equivalent production quality. Not "occasional alternative." Equal cadence.
• Menus (Tactic 5.1) — non-pork hero dishes sit in the main flow, NOT under a "vegetarian / dietary" header that re-marginalizes them. Same visual hierarchy.
• Cultural-moment pop-ups (Tactic 2.1) — pork-led classics stay (the baked pork-chop rice is part of the cha-chaan-teng vocabulary), but a non-pork hero (soy-cured chicken rice; salt-baked seabass rice) is equally prominent; the press pitch leads with both.
• Day-in-the-kitchen content (Tactic 3.1) — rotation includes pork-breaking AND non-pork-led equivalents (wagyu primal, whole-fish breakdown, dumpling-folding); pork-only sequences do not run as standalone SB-targeted assets.
• Halal-meat sub-subset — surfaced via Zenchef dietary fields + Schema.org suitableForDiet annotations on michiu.nl; NOT separately targeted in content (substance rule — we don't claim halal sourcing in outbound content unless we have actual halal-meat sourcing to back it up).

Why this posture: the "ignore + let pork lead" path silently excludes a meaningful slice of the tier we work hardest to serve. The "remove pork from SB content entirely" path loses the non-Muslim majority of SB + collapses important Cantonese-Japanese craft surface. Parallel-visibility serves both, doesn't apologize, and turns a structural fact into a quiet brand signal — the menu LITERALLY has more heroes — that reads as generosity, not accommodation. Aligns with §1.8 substance-over-claim.

Enforcement: the §6.7 ingestion map adds a dietary_considerations column to brand_audiences (migration 0045); helpers drafting SB-primary content read this field and Julius flags single-hero-only briefs. Other tiers carry their own dietary patterns in the same column (CC older-cohort gluten/heat/allergen; CB international group-spread reliability defaults — see migration 0045 seed text).

What this is NOT: a "halal menu" or "Muslim menu" — there is one Michiu menu; the non-pork heroes are first-class dishes, not a parallel sub-menu. The accommodation is never the headline of any moment; it is structural, not promotional.

2. The 11 trends, mapped to Michiu and the OS

[!tip] NL data interpolation Each trend below carries a brief NL-specific bullet inside "Why it matters for Michiu" where Dutch-market data (DDMA, FSIN, KHN, DataReportal) materially shifts the global Brandwatch framing. The NL bullet is what to act on when the two sources diverge.

Audience tier tagging — §2 tactics

Tier tags below apply to all tactics in §2. "Primary" = the tier the tactic is built for and the one that converts; "Secondary" = the tier the tactic also touches but isn't the design center. Where a tactic genuinely serves all three at once, it is labeled All three — but those are rare and most are properly single-tier. Tier abbreviations: SB = Status Builders, CC = Classic Connoisseurs, CB = Corporate Bookers.

Pattern observations from the tagging:

• CB tactics are the most concentrated by helper — all three CB-primary tactics (8.1, 8.2, 8.3) route to Penn-led LinkedIn + outreach surface. This makes the CB lane structurally efficient: one helper owns it.
• SB tactics distribute across more channels (IG, TikTok, in-restaurant moments, takeaway) — Zuck has the heaviest workload for SB.
• CC tactics lean on dinner-service moments + press + Siren — they don't show up much on IG. The cadence-per-tier rebuild in §5 (pass 2 still) needs to acknowledge: CC almost never sees an IG post; design the surfaces they DO see (menu, reply, GBP, press) with extra care.
• No CB-primary tactic appears in trends 1, 2, 4, 5 — the CB tier is concentrated in trend 8 (offline), trend 6 (employees-as-brand via Michelle/sommelier LinkedIn voice), trend 7 (no-list essay, reply-meta-post — published-principles read as competence to CB), and trend 10 (GEO — they Google). If we want more CB volume, build more trend-6/7/8/10 tactics, not more trend-2 cultural moments.
• Trend 6 + trend 7 are the trends with the highest CB lift relative to global Brandwatch framing — both because of NL's world-leading LinkedIn penetration (31%²²) and because the CB tier values stated principles + visible competence above almost any other variable.
• "All three" tactics (1.3 and 5.1) are both brand-policy-level — a website footer, a menu redesign. The pattern: things that touch every guest because they ARE the brand surface, not because they're optimized for everyone. Trend-7 no-list + trend-9 transparency footnote share this property.
• CC dominates trend 3 (trying is cool) — every drafted trend-3 tactic is CC-primary. The Classic Connoisseurs tier rewards visible craft + stated principles + named-person profiles most strongly. Trend-3 work IS the CC-tier work.

Each entry uses identical sub-headings (parseable for brand_sops ingestion). Tactics tag: Action / Channel / Voice anchor / OS owner / Trigger / Attribution hook.

Trend 1 — Only brands with soul will thrive in the AI slop era

What it means. Mentions of "AI slop" grew 200%+ in 2025 with 82% negative sentiment¹; consumers are actively rewarding human-made content with sustained attention. The premium-tier restaurant category is one of the most exposed because adjective-heavy food writing reads as exactly the kind of content an LLM produces by default.

Why it matters for Michiu. Two pressures compound: (a) Cantonese-Japanese restaurants are the genre most likely to generate look-alike AI content because "fusion food" carries a familiar visual grammar (Asian-inspired plating + warm wood interior + chopsticks + neon) that any image model will reproduce; (b) the words our category reaches for — premium, refined, elevated, curated, distinctive — are exactly the words on our banned list¹³ precisely because they are the AI-slop tell. The defense is the same defense as the moat: visible craft, named specifics, the chef's hand on the camera.

NL-specific: Dutch consumers respond to AI uncertainty with sharper trust-loss than the global average. Deloitte NL's Dutch Digital Consumer work finds Dutch users among Europe's most concerned about AI-generated commercial content²³; Kantar's NL trust data shows Dutch consumers reward brands that name their human authorship more than the global average⁴. Tactic 1.3 (the "No AI here" policy footnote on michiu.nl) is therefore not a defensive disclaimer — for the Dutch market it is a status signal. Lean into it.

Risk if ignored. Our feed becomes indistinguishable from the dozen other Cantonese-Japanese venues that opened in European cities in 2024–2026. We lose to a competitor whose only differentiator is that their chef shows up in the frame.

Tactics

• Tactic 1.1 — Hand-folded dumpling close-up series

  • Action: Weekly 8–12 second silent vertical clip of Michelle (or sous chef) hand-folding a dumpling. No music, no captions, no text overlay. Just the hands and the dough. Posted natively on IG Reels + TikTok.
  • Channel: IG Reels + TikTok
  • Voice anchor: Guidara (warmth via competence) + Sutherland (the discipline reads as oblique status signal)
  • OS owner: Zuck (extends existing caption-prompt v2 + scheduler); new Power-Up: craft-clip-weekly
  • Trigger: Manual — owner-requested weekly during a 20-min lunch-prep shoot
  • Attribution hook: m_campaign=craft_dumpling_<YYYY-MM-DD> on the link in bio for the week the clip runs; leading indicator: save:view ratio (anti-vanity, see §10 in pass 2)
  • Dietary rule (§1.9.1, SB-primary): any week that features a pork dumpling clip MUST also feature a non-pork dumpling clip (chicken-shiitake, prawn-chive, lamb-cumin) at equivalent production quality. Equal cadence, not "alternative." Zuck's craft-clip schedule enforces; Julius flags if the cadence drifts to pork-only over a 2-week rolling window.

• Tactic 1.2 — "What you didn't see" supplier-credit story arc

  • Action: Once per menu rotation, a 4-frame IG carousel showing (1) the supplier's farm/boat/distillery (2) the box arriving at our back door (3) Michelle inspecting (4) the dish on a plate. Name the supplier. Name the variety. Name the price-per-kilo if appropriate.
  • Channel: IG carousel + LinkedIn (B2B framing for Corporate Booker persona)
  • Voice anchor: Godin (story-shaping — the four frames are the story)
  • OS owner: Zuck drafts; Penn co-owns for LinkedIn version
  • Trigger: Inngest event menu.rotation.confirmed (does not yet exist — propose addition in §6 pass 2)
  • Attribution hook: m_campaign=supplier_<supplier-slug> UTM on bio link; brand-only leading indicator: supplier outreach inbound (whether other restaurants try to source from the same supplier — flattery proxy)

• Tactic 1.3 — "No AI here" policy footnote on michiu.nl

  • Action: Quiet one-line footer on our website: "All photography by [name]. All copy by Michelle Zhang and our team. No AI image generation, no AI-rewritten descriptions." Then live up to it: every photo on the site captures a real plate from a real service. (50% of marketers predict authentic/unpolished content will be a major 2026 trend²⁴ — being the first in the Amsterdam category to put this in writing is a status signal.)
  • Channel: website (michiu.nl footer + an /about/our-content page that explains the policy in 200 words)
  • Voice anchor: Kahneman (loss-aversion — names what we don't do)
  • OS owner: Julius (the policy IS the brand-guardian rule made public); Carlos owns the page on GBP description sync
  • Trigger: Manual — one-time launch, then quarterly review by Julius drift monitor
  • Attribution hook: GEO-relevant — feeds the memory_documents chunk-set for the chef story / sourcing pieces; brand-only otherwise

• Tactic 1.4 — Michelle's voice in every published long-form piece

  • Action: Six long-form essays on michiu.nl over 2026 (Pillar 3 content roadmap, see §4 pass 2) — every one of them must contain at least one quoted-out paragraph in Michelle's voice. Not Zuck's draft of Michelle's voice. Michelle's actual answer to a Penn-conducted 15-minute interview, transcribed and lightly edited.
  • Channel: website long-form + LinkedIn excerpt
  • Voice anchor: Guidara (warmth — only the chef has it) + Godin (the voice is the story)
  • OS owner: Penn drafts the interview; Julius enforces the quoted-paragraph rule
  • Trigger: Manual — quarterly cadence
  • Attribution hook: GEO — feeds memory_documents; LinkedIn excerpt gets m_campaign=longform_<piece-slug>

Trend 2 — Trendjacking is out. Genuine participation is in.

What it means. Brands that participate in cultural moments because they actually have a perspective on them earn audience reward (Brandwatch cites Tommy Hilfiger's "airball" TikTok at 2M+ likes as the canonical 2025 example²⁴); brands that staple their product onto unrelated cultural moments get punished (Brandwatch cites E.L.F. Cosmetics' backlash after a controversial comedian hire). 50% of marketers predict authentic/unpolished content as a major 2026 trend²⁴; Marcus Collins's framing: "You either drive the culture car, ride shotgun, or suck tailpipe when your brand doesn't add a point of view outside products."²⁴

Why it matters for Michiu. Cantonese-Japanese is sitting on a cultural calendar most Amsterdam venues don't engage with at all: Lunar New Year, Mid-Autumn Festival, Dragon Boat Festival, oseibo, hanami / sakura, momiji, oseichi-ryōri, the Cantonese yum-cha tradition itself. Add the Amsterdam-Chinatown / Zeedijk diaspora layer (which is part of the city's cultural fabric but rarely the subject of premium-tier restaurant content) and we have a six-to-eight-moment-per-year participation calendar that is genuinely ours and that almost no competitor is set up to honor. Trendjacking risk for us is zero in this lane because the calendar is the inheritance. The opposite trendjacking risk — chasing King's Day or Pride or Sinterklaas with a forced food angle — is the real failure mode to avoid.

NL-specific: Dutch press (Het Parool food section, NRC Achterpagina, Volkskrant Lekker) reliably covers cultural-calendar dining moments — Mid-Autumn and Lunar New Year especially have an editorial slot most years. The pitch window is 4–6 weeks ahead. NL hospitality 2026 framing¹⁷ specifically names the consumer desire for "comfort in familiar dishes while wanting to be surprised by worldly influences" — our cultural-calendar moments are the canonical version of that pairing in the NL market. Add to Penn's editorial calendar: pre-event NL-language pitches to Het Parool + Foodie Amsterdam for each major moment.

Risk if ignored. We default to the same calendar every Amsterdam restaurant runs (Valentine's, Mother's Day, Restaurant Week, Christmas) and our cultural specificity erodes. Status Builders looking for "the place that gets it" find another venue.

Tactics

• Tactic 2.1 — Mid-Autumn cha-chaan-teng pop-up (one weeknight, late September)

  • Action: One Wednesday in late September, transform lunch service into a cha-chaan-teng — milk tea, pineapple buns, baked pork-chop rice, the whole vocabulary of Hong Kong diner culture rendered through our kitchen's technique. A non-pork hero (soy-cured chicken rice / salt-baked seabass rice) sits on the menu at equal visual hierarchy to the baked pork-chop rice — see §1.9.1. Limited cover count (40 seats). Tickets via Zenchef. Mooncakes on every plate, supplied by [confirmed mooncake supplier — verify with Michelle, pass 2 task].
  • Channel: in-restaurant; promoted on IG carousel + LinkedIn (RAI lunch-time corporate audience)
  • Voice anchor: Godin (the story — what cha-chaan-teng is and why we honor it) + Guidara (warmth in the format)
  • OS owner: Sun proposes the Campaign archetype; Zuck builds the content; Penn pitches Het Parool food section the day after
  • Trigger: Sun creates the Campaign manually in late August; Inngest event campaign.created routes the rest
  • Attribution hook: m_campaign=midautumn_chachaanteng_2026 on Zenchef booking link; direct revenue + new-customer count from reservation.created event matched on m_campaign cookie
  • Dietary rule (§1.9.1, SB+CC joint): the Penn press pitch leads with BOTH the pork-chop rice AND the non-pork hero in the lede, not pork-led-with-non-pork-mentioned. Same visual treatment in the IG carousel. The accommodation is never the headline (it's structural, not promotional) but the visibility is parallel.

• Tactic 2.2 — Lunar New Year long table (one Sunday, 50–60 covers, family-style)

  • Action: Annual Lunar New Year long table — 50–60 seats, one long communal setting, ten-course family-style menu. Tickets release 6 weeks ahead. Circle members get 72-hour priority (felt, not announced — the priority simply exists in the booking link sent via Clara's lifecycle flow).
  • Channel: in-restaurant; IG + LinkedIn promotion; Clara's email/WhatsApp for Circle priority
  • Voice anchor: Guidara (warmth at scale) + Sutherland (the 72-hour priority is an oblique status moment)
  • OS owner: Clara owns the Circle priority send; Zuck owns public promotion; Penn owns press
  • Trigger: Manual Campaign creation; Inngest campaign.created + clara.lifecycle.priority_send
  • Attribution hook: m_campaign=lny_longtable_2026 + Circle priority send adds circle_priority_send_id to the lifecycle_outreach_log (see Clara helper spec, marketing-os-build-plan.md §2)

• Tactic 2.3 — Sakura week dessert collaboration with the patisserie program

  • Action: Two-week window in late March / early April: a single sakura-leaf-cured namelaka by our pastry lead, available as both a dine-in course and a small box-of-four for takeaway. The leaf is genuinely sourced (verify with patisserie supplier). The story is the curing process.
  • Channel: in-restaurant + IG (the curing process clip is the asset)
  • Voice anchor: Sutherland (the cured-leaf detail is oblique — most guests will not know that sakura leaves are eaten, that's the moment) + GaryVee (kinetic clip energy)
  • OS owner: Zuck owns content; pastry-lead drives the source material
  • Trigger: Inngest event seasonal.sakura.window (does not yet exist — propose in §6 pass 2; cron-based, fires on Mar 20 each year)
  • Attribution hook: m_campaign=sakura_namelaka_2026 on the takeaway-box order link; in-restaurant dessert demand is brand-only

• Tactic 2.4 — What we will NOT do

  • Action: Explicit no-list, encoded as a Sun strategic principle and a Julius rule: no Valentine's "couples menu" with hearts on the plate, no St. Patrick's Day green-themed cocktail, no King's Day orange-themed dessert, no forced-tie-in to whatever non-food cultural moment is dominating that week's news cycle. Decline tactically.
  • Channel: internal policy — appears as a Julius rule (severity: 'warn') and as a Sun briefing-template guardrail
  • Voice anchor: N/A — it's a guardrail, not an output
  • OS owner: Julius + Sun
  • Trigger: evaluated at Campaign-brief time
  • Attribution hook: N/A — guardrail

Trend 4 — Little treat culture is having a big impact

What it means. "Little treat" mentions hit 40k+ per month throughout 2025; 23% of marketers see feel-good purchases as a 2026 growth trend¹¹. Brandwatch cites Waitrose's "Little Treats" loyalty program (UK 2025) and the Labubu collectibles surge as the canonical examples. The pattern: cost-of-living pressure + dopamine-economy mechanics = consumers seeking small, deliberate, share-worthy indulgences rather than large purchases.

Why it matters for Michiu. This is the trend most directly aligned with the gamification pillar (§1.3) and with the Circle architecture²⁵. Sutherland's "irrational value" mechanics — surprise tastings, a small handwritten haiku with the dessert, the sake flight that was "selected for you tonight" — are exactly the surface this trend rewards. The lunch daypart is the lowest-cost test environment because: (a) lunch covers are easier to fill incrementally (b) the gesture-level cost is lowest (c) the share-mechanic operates fastest at lunch because that's when guests post in real time. Also relevant: 40% of US consumers are cutting restaurant frequency⁷ AND wellness + affordability are jointly top-of-mind²⁶ — a small, gestural, low-frequency indulgence reads as "yes" to both at once.

NL-specific: The NL hospitality 2026 trend ("less often, more meaningful per visit"¹⁷) and the rising no-show problem¹⁷ interlock here. Dutch guests are increasingly making same-day or day-of decisions about whether to dine out — Sun's micro-opportunity Power-Up (Tactic 4.4, rainy-Tuesday + open tables) catches exactly this behavior with a no-discount, gesture-led message. It is more strategically important in NL than the global "little treat" framing suggests because it converts spontaneity into structured demand. Promote Tactic 4.4 from "propose" to a P0 Sun Power-Up build in §6 pass 2.

Risk if ignored. Lunch remains the weakest daypart. Circle perks remain abstract benefits guests don't notice. We compete on price (a battle we cannot win against the casual end of the Scheldestraat corridor) instead of competing on gesture (a battle no Asian restaurant in Amsterdam-Zuid is even fighting).

Tactics

• Tactic 4.1 — The lunch dice (gamification pillar, first production instance)

  • Action: A wooden 6-sided die on every lunch table Tuesday-Friday. Roll once. The result is a small kitchen gesture: an extra dumpling, a thumb-sized scoop of pickled daikon, a sip of sake the sommelier picked, a chef's-pick teaspoon of the pastry of the day, a small bao on the house, a "skip the wait next time" courtesy card. Six results, all gestures, none of them framed as "rewards." A guest who asks "what is this?" is told "It's the dice. Roll it." Nothing further. The mechanic is felt, not told.
  • Channel: in-restaurant — the entire artifact is the channel
  • Voice anchor: Sutherland (the obliqueness IS the mechanic) + Guidara (warmth in the gesture)
  • OS owner: Sun proposes the Campaign archetype lunch-dice-2026; Zuck builds the silent FOH-shot launch clip; Carlos updates the lunch GBP description to reference "the dice on the table" without naming a program
  • Trigger: Campaign-brief manual launch; weekly Insight digest captures dice_roll_outcome distribution from POS
  • Attribution hook: Brand-only at the gesture level. Leading indicator: lunch covers Tue–Fri (4-week trailing average), and organic IG mentions of the dice (Insight listening Power-Up). Lagging indicator: lunch-daypart revenue Tue–Fri vs. baseline. NEVER use the word "gamification" or "rewards" in any caption, GBP post, or reply about the dice.

• Tactic 4.2 — The "selected for you tonight" sake pour (dinner)

  • Action: Sommelier-chosen 30ml pour brought to each table during the second course of any tasting menu. No upsell — it's already in the menu price. The pour comes with two sentences from the sommelier: which sake, why this one tonight, what to taste for. Same script structure every table; the bottle changes.
  • Channel: in-restaurant
  • Voice anchor: Guidara (warmth via expertise)
  • OS owner: Sun proposes the Campaign archetype; the sommelier owns the script (worked-example library — feeds memory_documents for the sake-program chunk-set)
  • Trigger: Manual operational pattern; tracked nightly in POS as a line-item
  • Attribution hook: Brand-only. Leading indicator: tasting-menu repeat-visit rate within 90 days (Insight Power-Up — cohort analysis on the reservations table)

• Tactic 4.3 — Circle birthday gesture, never a "birthday email"

  • Action: Two weeks before a Circle member's birthday, Clara surfaces them in the universal approval queue. A human (Michelle or FOH lead) handwrites one line on a card. The card is mailed to their address (we have it from Zenchef). The card invites them in for a small thing — no menu, no offer, no points. When they arrive, the kitchen sends out a single hand-shaped chocolate or a small bowl of their last-ordered dessert. The Adept/Master tier is felt in the which dessert — we know what they liked last time.
  • Channel: Direct mail → in-restaurant
  • Voice anchor: Guidara (the form factor is the point)
  • OS owner: Clara drafts the card line + identifies the last-ordered dessert from reservation.completed event history; approval queue surfaces to Michelle
  • Trigger: Inngest clara.birthday.window_open (14 days out) — does not yet exist; propose in §6 pass 2
  • Attribution hook: Brand-only at the gesture level. Leading indicator: 90-day return rate post-birthday-gesture (Insight cohort Power-Up)

• Tactic 4.4 — Rainy-Tuesday Sun-triggered "if you're nearby" push

  • Action: When the Sun helper detects ≥6 open lunch tables AND the local Amsterdam-Zuid weather forecast shows ≥4mm rain between 11:00–14:00 local, draft a short same-day push to Clara's lifecycle list of "guests who have been in the last 90 days and live within 3km" (geofence on stored billing-address). The message offers no discount — it offers warmth: "Soup of the day is salt-baked chicken broth with goji and ginger. Table by the window is open if you want to escape the rain."
  • Channel: WhatsApp Business (primary) → email (secondary, for guests without WhatsApp opt-in)
  • Voice anchor: Guidara (warmth) + GaryVee (kinetic — present tense, specific)
  • OS owner: Sun detects + drafts; Clara owns the send list and channel; approval queue routes to Michelle or FOH lead
  • Trigger: Inngest sun.micro_opportunity.weather_occupancy (composite event — see §6 pass 2 Power-Up spec)
  • Attribution hook: m_campaign=rainytuesday_<YYYY-MM-DD> on the booking link in the WhatsApp message; same-day reservation conversion measured from the click_tracking match

• Tactic 4.5 — Pastry program small-box-of-four (boxed takeaway)

  • Action: A small four-piece namelaka box, takeaway only, available Thursday–Sunday during the patisserie program's most photographed flavor windows (yuzu-matcha is the launch flavor). Priced for the "little treat" affordability frame; sized for IG. Pickup window: 16:00–18:00 so it's a deliberate detour, not an add-on to dinner.
  • Channel: website ordering page + in-store walk-in
  • Voice anchor: Sutherland (the takeaway-as-treat reframing) + Godin (the box is the story)
  • OS owner: Zuck content; pastry lead owns the supply; Carlos updates GBP "products" attribute
  • Trigger: Manual launch; weekly content cadence
  • Attribution hook: m_campaign=namelaka_box_<flavor> UTM on the order page; direct revenue measurable (the order is on michiu.nl, not Zenchef)

Trend 5 — Nostalgia marketing is here to stay

What it means. Nostalgia conversations reached 43M mentions in 2025, +18% YoY²⁷; NRA's 2026 culinary forecast names nostalgia, comfort, and "flavor escapism" as the dominant consumer desire¹²; McKinsey's 2026 restaurant consumer work confirms higher-income consumers driving growth specifically into comfort and known-quantity dining⁸. Brandwatch's note is sharp: effective nostalgia marketing taps genuine emotional touchpoints — not retro filters.

Why it matters for Michiu. This is the trend most directly aligned with the cuisine itself, and the one our category has the most natural authority to tell. Cha-chaan-teng childhood memory (the Hong Kong working-class diner — milk tea, pineapple bun, instant noodles in soup, the smell of evaporated milk in coffee) and Japanese home-cooking nostalgia (the rice-and-pickle plate a grandmother made, the karaage at the corner izakaya) are both genuinely-felt food memories that millions of diaspora and Asia-curious Amsterdam diners carry. We can render them at a higher technique tier than the memory itself, which is the move — not "we make pineapple buns" but "we make the pineapple bun your grandmother bought you at Café de Coral, finished in our oven with butter from the same Dutch farm we get our pastry butter from."

NL-specific: The NL hospitality 2026 forecast explicitly names "comfort in familiar dishes while surprised by worldly influences and creative twists"¹⁷ AND the parallel rise of "compact, thoughtfully constructed menus"¹⁷ as the dominant operator trend. Tactic 5.1 (chef's-note menu redesign — one italic memory line per dish, compact menu) is therefore precisely on-trend for the NL operator-side and consumer-side simultaneously. This is the rare tactic where the NL data is stronger evidence than the global Brandwatch nostalgia framing.

Risk if ignored. Nostalgia gets ceded to the casual end of the Cantonese restaurant scene (the Zeedijk Cantonese venues that have always been here, doing it well, but without our technique grounding). Our category-defining "why these two cuisines together" answer is left half-told.

Tactics

• Tactic 5.1 — Chef's note: one paragraph per dish on the dinner menu that names the memory it came from

  • Action: Redesign the dinner menu. Each dish gets a single italic line beneath the dish name: "The pineapple bun Michelle remembers from Sunday mornings at Café Lan Fong Yuen, Hong Kong, 1996" or "The katsu Michelle's father made when she was twelve, with the cabbage cut at the angle he insisted on." No flowery prose. One sentence. Anchored in a real person, a real place, a real year.
  • Channel: in-restaurant (the menu) + michiu.nl (the menu page)
  • Voice anchor: Godin (every sentence is a story) + Guidara (specific warmth)
  • OS owner: Penn ghost-writes from a Michelle interview; Julius enforces specificity (every memory must name a year, a place, or a person — abstract memories blocked)
  • Trigger: Manual — menu redesign launch
  • Attribution hook: Brand-only. Leading indicator: avg time-on-menu-page on michiu.nl (Insight); lagging: tasting-menu attach rate (POS)
  • Dietary rule (§1.9.1, all-three tiers): the menu must have non-pork hero dishes findable at first scan AND placed in the main menu flow — NOT siloed under a "vegetarian / dietary" header (siloing re-marginalizes; main-flow placement is the structural signal). The chef's-note treatment applies equally to pork and non-pork dishes — no asymmetric warmth. Julius gates: a menu draft that places non-pork heroes only in a separate section is blocked at review.

• Tactic 5.2 — "What grandmother made" Sunday-lunch quarterly series

  • Action: Four Sundays per year, lunch service becomes a single-family-recipe homage. Michelle's grandmother's recipe, the sous chef's grandmother's recipe, the sommelier's grandmother's recipe (sake-from-the-grandparents'-prefecture pairing), the pastry lead's grandmother's recipe. Each Sunday is one cast member. The press angle writes itself.
  • Channel: in-restaurant; IG + LinkedIn content; Penn-pitched press
  • Voice anchor: Guidara (warmth) + Godin (each Sunday is a story arc)
  • OS owner: Sun proposes the Campaign archetype grandmother-sunday-quarterly; Penn pitches Het Parool, NRC, possibly Volkskrant
  • Trigger: Sun creates 4 Campaigns at start of year
  • Attribution hook: m_campaign=grandmother_<staff-firstname>_<season> on Zenchef booking link; press cites attributed via Penn's outreach log

• Tactic 5.3 — Re-issue of a "first-month" dish from Michiu's earliest menu, once per quarter, only for that quarter

  • Action: Reach into the restaurant's own short history. Each quarter, one dish that was on the menu when Michiu opened (or in its first year) returns to the dinner menu for that quarter only. The chef's note names the original date range. Returning guests notice; new guests are told via a single sentence on the menu.
  • Channel: in-restaurant + IG (the return-of-the-dish post)
  • Voice anchor: Sutherland (the scarcity is the mechanic) + Kahneman (FOMO works because the disappearance is real)
  • OS owner: Zuck content; Sun owns the rotation calendar
  • Trigger: Quarterly menu rotation
  • Attribution hook: m_campaign=heritage_dish_<dish-slug>_<quarter> UTM on bio link the week of launch

Trend 8 — Digital fatigue is driving brands to meet consumers offline

What it means. 57% of event organizers reported increased in-person attendance in 2025; 75% of attendees say immersive experiences help them disconnect and engage meaningfully²⁸. Brandwatch cites Peloton's NYC Marathon cheering booth, Offline Club / Othership / Sofar Sounds (phone-free gatherings), and Katherine Wroblewski's framing: "Consumers crave human trust in AI-driven world. Retreat to trusted micro-communities and hunger for real-world experiences."²⁸

Why it matters for Michiu. Offline is already our terrain. The risk is not absence — it is under-amplification. We run tastings, chef's table, sake events, supplier dinners, omakase, and we tell the world about almost none of these in the moment they happen. The 2026 work is making the offline programming visible as content without making the content the point. This is also the lane where the Corporate Booker persona⁶ converts hardest — event planners who experience Michiu once become repeat bookers for every RAI event they manage.

NL-specific (this trend is materially stronger in NL than global): DDMA's 2025 Barometer is the sharpest single data point in this entire strategy: 35% of Dutch (47% Gen Z+Millennial) are actively reducing digital media use, and 67% expect that reduction to be permanent¹⁶. The Dutch consumer is not just "open to" offline — they are walking toward offline. For Status Builders specifically, the phone-free supper club (Tactic 8.4) shifts from a quirky one-off to a structural alignment with their stated behavior. For Corporate Bookers, NL has one of the world's highest LinkedIn penetration rates²² AND a value-over-volume hospitality consumption pattern¹⁷ — the RAI event-week LinkedIn play (Tactic 8.3) compounds two NL advantages no global benchmark restaurant can match.

Risk if ignored. The offline programming becomes invisible to the discovery loop. A Status Builder who would have come for the chef's table doesn't know it exists. A Corporate Booker considering Michiu for a Money20/20 dinner can't find evidence we handle groups.

Tactics

• Tactic 8.1 — The chef's table, properly documented

  • Action: Every chef's table booking becomes a single 6-frame carousel asset (with guest permission, in their own context — never naming them publicly). The carousel: (1) the empty table set (2) the first course landing (3) Michelle plating in the open kitchen (4) a hand-pour of sake (5) a dessert moment (6) the bill folded with a handwritten thank-you. Posted within 48 hours of the dinner — the asset is the social proof.
  • Channel: IG + LinkedIn
  • Voice anchor: Guidara (the warmth is the offering)
  • OS owner: Zuck owns capture protocol + scheduler; Sun proposes the asset Power-Up chefs-table-capture-protocol
  • Trigger: Inngest reservation.completed with tag=chefs_table (event topic confirmed real, see src/marketing-os/orchestration/topics.ts:81)
  • Attribution hook: m_campaign=chefs_table_carousel on bio link the week it posts; LinkedIn version → Corporate Booker pipeline; direct chef's-table bookings tracked from m_campaign cookie

• Tactic 8.2 — Quarterly event-agent tasting evening (the highest-leverage B2B move in this document)

  • Action: Once a quarter, host 6–8 Amsterdam event-planning agents for a 90-minute complimentary tasting. Pre-arranged 5-course menu, 75 minutes table time, structured intro from Michelle, no sales pitch, a leave-behind one-pager with group-dining contact and pricing. The cost (€150–200 per event) is dwarfed by a single repeat-booking event agent (per docs/rai-scheldestraat-strategy.md: €3,000–€15,000/year in group revenue per active relationship⁶).
  • Channel: in-restaurant; LinkedIn pre-event invitations; Penn-owned outreach
  • Voice anchor: Kahneman (the no-pitch is the trust signal) + Guidara (the warmth is the demonstration)
  • OS owner: Penn owns outreach + invitation; Sun proposes the Campaign archetype event-agent-tasting-quarterly
  • Trigger: Sun creates 4 Campaigns at start of year; Penn drives invitations 6 weeks ahead
  • Attribution hook: Each invited agent gets a unique m_campaign=agent_<agent-slug>_2026 — every booking they refer for the next 24 months attaches to that slug. Long-tail attribution is the point.

• Tactic 8.3 — RAI event-week "we have weekday availability" LinkedIn post (templatized per major event)

  • Action: One week ahead of each major RAI event (Money20/20, IBC, KubeCon, GreenTech, PLMA — see docs/rai-scheldestraat-strategy.md⁶), publish a LinkedIn post from Michelle's account that names the event, names our weekday availability, and offers group menu / private section / 5-minute walk. Format: short, specific, frictionless. The DM/email is the conversion.
  • Channel: LinkedIn (Michelle's personal account + Michiu company page)
  • Voice anchor: GaryVee (kinetic, present-tense) + Kahneman (the specificity reduces decision friction)
  • OS owner: Penn drafts from template; Roy considers a paired LinkedIn Ads geo-boost for the event week
  • Trigger: Inngest rai.event.upcoming.t_minus_7d (cron-style — propose in §6 pass 2; sourced from rai.nl/en/calendar scrape or manual Sun input)
  • Attribution hook: m_campaign=rai_<event-slug>_2026 on the contact email/booking link; group-booking inquiries tracked manually in Penn's outreach log (the email arrives at events@michiu.nl, not via the website conversion path)

• Tactic 8.4 — The "no phones on the table" supper club, four times a year

  • Action: Four Thursday evenings in 2026, the long table becomes a phone-free dinner. Phones go in a small wooden box at the door. 14 covers. A theme per evening (sake from a single prefecture, a dialogue between Cantonese and Japanese pickling, a "first-time-they-cooked-this-dish" stories evening). The phone-free constraint is the participation — directly riffing the Offline Club / Othership phone-free format Brandwatch flagged²⁸ but rendered as a restaurant.
  • Channel: in-restaurant; ticketed via Zenchef; soft-promoted (this is a slow-burn loyalty mechanic, not a top-of-funnel push)
  • Voice anchor: Godin (the constraint is the tribe signal) + Sutherland (the box at the door is the oblique)
  • OS owner: Sun proposes the Campaign archetype phone-free-supper-quarterly; Zuck builds a teaser asset (which gets the phone-in-box gesture into the discovery loop about the format, paradoxically)
  • Trigger: Quarterly Campaign launch
  • Attribution hook: m_campaign=phonefree_<season>_2026 on the Zenchef link; brand-only on the experience itself; leading indicator: re-booking rate of phone-free attendees within 6 months (Insight cohort Power-Up — these are high-loyalty guests by self-selection)

Trend 3 — Trying is cool again (brands can stop playing it safe)

What it means. Positive mentions of "cringe" surged 25% in 2025 — earnest effort is being rewarded; performative effortless polish is being punished²⁹. Brandwatch cites K-Pop Demon Hunters (Netflix's most-watched animated film despite an unknown cast) as the canonical 2025 example, and the end of "blanding" (minimalist aesthetic sameness). Ghassan Kassabji's framing: "People want brands and products that feel real and reward connection. 2026 will be about meaning, not metrics."²⁹

Why it matters for Michiu. The premium-tier restaurant category has historically been built on a "this came together by magic" presentation — the plate appears, the wine pours itself, the service is invisible. That posture is the worst possible read in 2026. Our cast has the opposite story: a chef who rebuilds her dumpling fold every three years; a pastry lead who fails laminated dough four times before the fifth one works; a sommelier who carries a notebook of every pour she's regretted. The effort is the brand and we have not been showing it. Across all three audience tiers this is corrective: Status Builders reward the visible craft (it IS the differentiator vs. AI-slop), Classic Connoisseurs reward technique-visibility as proof of integrity, Corporate Bookers reward effort-as-competence-signal (a kitchen that shows its work is a kitchen that will not embarrass them at a Money20/20 dinner).

NL-specific: The Dutch "authenticity-and-relatability over polish" pattern³⁰ runs hotter than the global average. Dutch consumers, per Deloitte NL²³ and the DDMA 2026 marketing focus¹⁶, respond especially strongly to relatable human stories — which is the inverse of the "untouched-by-human-hands" aesthetic premium-tier restaurants have defaulted to. The NL signal supports being more visible-effort, not less, especially in long-form (KHN's compact-thoughtful-menu trend¹⁷ AS the operator-side parallel to consumer-side trying-is-cool).

Risk if ignored. We continue to look like every other "elegant Asian-inspired dining" venue in Amsterdam-Zuid, and the people who would have come for the story go somewhere where the chef shows up in the frame.

Tactics

• Tactic 3.1 — "A day in the kitchen" quarterly long-form video

  • Action: A quarterly 8–12 minute video on michiu.nl (with a 60-second teaser on IG/TikTok). Topic rotates: Michelle's 3 a.m. visit to Volendam fish market; the sous breaking down a Wagyu primal in the cold room; the pastry team's 4-hour laminated-dough lab; the FOH lead's setup ritual for a chef's-table evening. No music. Real-time audio. The video IS the proof.
  • Audience tier: CC (primary — they watch long-form) + SB (teaser version converts)
  • Channel: website primary, IG + TikTok teaser
  • Voice anchor: Guidara + Godin
  • OS owner: Zuck (production); Sun proposes the quarterly Campaign archetype day-in-kitchen-quarterly
  • Trigger: Quarterly manual Campaign launch
  • Attribution hook: m_campaign=craft_day_<quarter> on the teaser bio link; full video on michiu.nl feeds memory_documents GEO chunk-set
  • Dietary rule (§1.9.1, SB teaser specifically): the rotation does NOT lead with a pork-primal-breakdown for SB-targeted teaser cuts. Whole-fish breakdown, wagyu primal, dumpling-folding, or laminated-dough lab are the SB-safe leads. A pork-breaking sequence can appear in the full long-form (CC-targeted) but is not the IG/TikTok teaser if the teaser quarter is SB-primary. Zuck swaps the teaser pick at edit time per the quarter's tier-priority.

• Tactic 3.2 — "Show the test menu"

  • Action: When a menu rotation is in progress, publish 2–3 IG carousel posts of test plates that did not make it. The dumpling shape we abandoned. The pairing the sommelier vetoed. The dessert that didn't survive the third version. Caption: one short line of what went wrong. No "behind the scenes" framing. Just: this is what trying looks like.
  • Audience tier: SB + CC
  • Channel: IG carousel
  • Voice anchor: Sutherland (the counterintuitive — showing failures IS the proof)
  • OS owner: Zuck; Sun owns the cadence (every menu rotation triggers)
  • Trigger: Inngest menu.rotation.confirmed (does not yet exist — propose in §6)
  • Attribution hook: Brand-only. Leading indicator: comment quality (Insight listening)

• Tactic 3.3 — The named-dishwasher quarterly profile

  • Action: Once a quarter, profile someone the press never profiles: the dishwasher, the night porter, the prep cook. By name. About their craft (yes, dishwashing has craft). 600–900 words on michiu.nl. Penn pitches a shorter version to Het Parool food section or Foodie Amsterdam — they almost certainly run it because no other Amsterdam premium-tier venue does this.
  • Audience tier: CC (primary — press readers + people who notice integrity) + CB (LinkedIn — "this is a venue that takes care of its people" = competence signal)
  • Channel: website + press + LinkedIn excerpt
  • Voice anchor: Godin (the story is the point)
  • OS owner: Penn (drafts + pitches); Zuck owns the LinkedIn excerpt
  • Trigger: Quarterly Sun Campaign archetype staff-profile-quarterly
  • Attribution hook: Brand-only on website; press cites tracked in Penn outreach log; LinkedIn excerpt → m_campaign=staff_profile_<staff>_<quarter>

• Tactic 3.4 — Michelle's "wrong-first-version" annual essay

  • Action: Once a year — anchor piece on michiu.nl — Michelle writes about a dish she got wrong the first three years and finally understood by year four. Honest, specific, named. 1,500–2,000 words. Anchored in a year, a guest, a specific moment when the change clicked. This becomes the most-cited piece on michiu.nl over time.
  • Audience tier: CC + CB (LinkedIn excerpt — chef thought leadership)
  • Channel: website long-form + LinkedIn excerpt (Penn)
  • Voice anchor: Guidara + Godin
  • OS owner: Penn (interviews + transcribes + drafts); Michelle voices; Julius enforces specificity rule
  • Trigger: Annual Sun Campaign
  • Attribution hook: GEO — primary memory_documents chunk for chef-voice queries; LinkedIn excerpt → m_campaign=chef_essay_<year>

Trend 6 — Employees are brand architects, not just spokespeople

What it means. Only 3% of employees share company content, but those shares drive a 30% engagement lift and 2× the CTR of company-channel content⁹. Cisco's employee-Instagram program is the cited example. Meghan Meeker's framing: "Running a social media team without employee advocacy is like exploring wilderness without a map."⁹ Kantar separately reports a net 61% of marketers planning to increase creator-content investment in 2026¹⁰ — but "creator" is being redefined to include internal voices, not just paid external influencers.

Why it matters for Michiu. Our cast is pre-built and structurally distinct from the cast at most premium-tier venues, because (a) Michelle is comfortable visible (not all chef-owners are), (b) the sommelier has a specialism (sake) that produces its own content gravity, (c) the pastry program has process-visibility built into the craft, (d) Cantonese-Japanese FOH culture is already conversational in a way that translates to camera. This is rare. Most competitors can't run a cast-led content motion because their chefs do not want to be in frame and their FOH do not want to talk on camera. This is the asset we have not been monetizing.

NL-specific: NL has one of the world's highest LinkedIn penetration rates (31%²²) — meaning employee-LED LinkedIn content (Michelle's voice, the sommelier's notebook, the GM's perspective) has more structural surface in NL than almost anywhere else. For the Corporate Booker tier this is decisive. Also relevant: NL TikTok 25–44 cohort growing fastest²² — the older end of the cast (Michelle, the sommelier — not the 22-year-old FOH) has more TikTok latitude in 2026 than the global "TikTok is for the young" framing suggests. Don't cap cast TikTok contribution by age.

Risk if ignored. The 2× CTR lift from employee-shared content is left on the table; the brand presence remains thin (one IG account, one LinkedIn page) when it could be a chorus of cast accounts cross-amplifying; the LinkedIn lane near RAI is ceded to a competitor that figures this out first.

Tactics

• Tactic 6.1 — Monthly cast roster anchor

  • Action: Every month, one cast member is the anchor of the content cadence. Michelle is January (annual anchor); the sommelier is February; the pastry lead is March; sous A is April; the FOH lead is May; sous B is June; the kitchen porter is July (yes — see Tactic 3.3); pastry assistant is August; the bar lead is September; sommelier returns October (autumn sake season); pastry returns November (oseichi prep); Michelle closes December. 12 anchors per year. Each gets 2–3 hours of paid filming/drafting time during their month (see Tactic 6.4). Their content is their voice; Zuck is the coach not the author.
  • Audience tier: SB + CC; CB indirectly (the LinkedIn version of Michelle/sommelier/GM months)
  • Channel: IG primary; TikTok where the cast member is comfortable; LinkedIn for the senior-cast months
  • Voice anchor: GaryVee + Guidara (varies per cast member — the variance IS the structure)
  • OS owner: Zuck (coach + scheduler); the cast member is the author
  • Trigger: Monthly Sun-managed cadence; specific Campaign archetype cast-anchor-monthly
  • Attribution hook: m_campaign=cast_<staff-firstname>_<month> on each cast member's monthly bio link; Insight tracks per-cast-member engagement-lift vs. brand-channel baseline (the 30% / 2× CTR validation loop)

• Tactic 6.2 — Sommelier's bi-weekly notebook

  • Action: Every two weeks, a 200-word post — first-person, from the sommelier's voice — about one sake/wine/pour worth talking about that fortnight. Published on the sommelier's LinkedIn AND as a column on michiu.nl/notebook. Not an "education series." A real fortnightly note from a working sommelier. The frequency builds the archive.
  • Audience tier: CC + CB (LinkedIn)
  • Channel: LinkedIn (primary) + website column
  • Voice anchor: Guidara (the warmth is the expertise)
  • OS owner: Penn (LinkedIn surface) + Zuck (web); the sommelier is the author
  • Trigger: Bi-weekly cadence (24 posts/year)
  • Attribution hook: m_campaign=sommelier_notebook_<dateslug> on any in-post booking link; GEO contribution — the column accrues over 12 months into a substantial sake-program chunk-set in memory_documents

• Tactic 6.3 — Pastry lead's quarterly failure log

  • Action: Quarterly IG carousel from the pastry lead's POV. Six frames: three failed laminated croissants, three failed namelaka attempts, the one that finally worked. Specific (named butter, named temperature, named hydration percentage). The caption is the pastry lead's voice, lightly edited.
  • Audience tier: SB
  • Channel: IG carousel (TikTok if pastry lead wants)
  • Voice anchor: Sutherland (failure-shown is the oblique credibility) + Godin
  • OS owner: Zuck; pastry lead authors
  • Trigger: Quarterly Campaign pastry-failure-log
  • Attribution hook: m_campaign=pastry_failures_<quarter>; brand-only at the engagement level

• Tactic 6.4 — EGC training is a real budget line (internal policy)

  • Action: Internal policy: every cast member who contributes to outbound gets 2 hours per quarter of paid time for content contribution — filming, drafting, voicing, photo-shoots. Not asked-as-a-favor after closing. The line is in the labor cost. Total: ~120 hours/year of paid cast-content time, distributed across 10–12 cast members. This is the structural cost of being a cast-led brand. If this line is cut, all of trend 6 collapses to Zuck doing it himself, which collapses back to brand-channel content.
  • Audience tier: Internal — supports all three
  • Channel: N/A (internal labor policy)
  • Voice anchor: N/A
  • OS owner: Sun (proposes annually in the brief); Insight (tracks compliance — cast members not getting their 2 hours/quarter flag in the weekly digest); Michelle approves
  • Trigger: Quarterly Insight audit
  • Attribution hook: N/A (cost line — measured against trend-6-tactic CTR uplift in §10)

Trend 7 — Strategic rule-breaking is your superpower

What it means. Brandwatch cites Ryanair's irreverent social responses, Ritz's "Ritz is so good, it's annoying" Super Bowl spot, and Hopper Coffee House (a UK independent café using staff-led humor) as 2025 examples³¹. The pattern: brands that consciously break their category's playbook — irreverence, self-awareness, controlled chaos — cut through faster than brands optimizing for category sameness. The qualifier from a Brandwatch survey respondent (October 2025): "Breaking brand rules for cultural relevance might work if it's authentic. If just grabbing attention, it falls flat."³¹

Why it matters for Michiu. The premium-tier restaurant playbook is comprehensively risk-averse: hushed tone, serious presentation, careful copywriting, "we are pleased to welcome you." Every break we make against that — the lunch dice, the no-Valentine's policy, the wrong-first-version essay, Michelle's review-reply tone — compounds. Our existing brand voice IP already breaks the rules locally (review-prompt.ts v2.0 explicitly bans "we hope you'll give us another chance" begging-for-return language and forbids excessive exclamation marks⁵). We have not been telling that story externally. The rule-breaking that already happens inside our reply system can be made visible quarterly as a meta-brand surface.

NL-specific: Dutch advertising preference data⁴ shows NL consumers reward ad equity earned through clarity and directness more than through performative warmth — which aligns with our existing voice rules (no exclamation marks, no begging, specificity over adjectives). The Dutch market is unusually receptive to the dry-and-direct register the rest of the premium-tier category avoids. Lean further into it, not less.

Risk if ignored. We become indistinguishable from the venue-without-irreverence default. We have the cast and the voice IP to be the wry one in the category; if we don't surface it, that position is occupied by a competitor or — worse — we are forced to claim it later through marketing, which (per §1.2) collapses the position the moment it's named.

Tactics

• Tactic 7.1 — The "no-list," published annually

  • Action: Once a year — late January, anchor piece on michiu.nl — publish the explicit no-list. We don't do a Valentine's couples menu. We don't do an orange dessert for King's Day. We don't say "we hope to see you again" in replies. We don't run "FRIENDSANDFAMILY20" promo codes. We don't put the chef's signature dish on the third-party delivery menus. And so on. 12–18 items. Each with one short sentence on why. The piece IS the brand's irreverence made visible.
  • Audience tier: CC + CB (primary — both read long-form + value stated principles); SB will discover and screenshot
  • Channel: website + LinkedIn excerpt (Michelle's account) + press pitch (Het Parool, NRC Achterpagina — both run this kind of piece)
  • Voice anchor: Kahneman (loss-aversion via stated nots) + Sutherland (the oblique status of publishing it)
  • OS owner: Julius drafts (it IS the brand-guardian rules made public); Penn voices and pitches
  • Trigger: Annual Sun Campaign (each January)
  • Attribution hook: GEO — feeds the chef-voice / principles chunk-set; LinkedIn excerpt → m_campaign=nolist_<year>

• Tactic 7.2 — Quarterly review-reply meta-post

  • Action: Every quarter, Penn surfaces one of Siren's reply outputs (with reviewer anonymized) that exemplifies our rule-breaking — a reply where we honestly disagreed, or acknowledged a failure specifically, or declined to thank "kind words." Post on LinkedIn as a 100-word commentary: "Here is the kind of reply we write. We don't say 'we hope you'll give us another chance.' Here's why." Quarterly cadence builds the archive of voice examples that compound on GEO (LLM grounding).
  • Audience tier: CC + CB (primary)
  • Channel: LinkedIn (Michelle's account)
  • Voice anchor: Sutherland + Kahneman
  • OS owner: Siren (the reply itself); Penn (the meta-post)
  • Trigger: Quarterly Sun Campaign
  • Attribution hook: m_campaign=reply_meta_<quarter> on any contained link; GEO contribution to voice/principles chunk-set

• Tactic 7.3 — Naming things slightly wrong-for-a-restaurant

  • Action: Internal guideline applied at Campaign-naming time. When Sun proposes a Campaign or Zuck names a content series, the name should land slightly off-rhythm for a premium-tier restaurant. "The dice" not "Lucky Lunch Roll." "Grandmother Sunday" not "Heritage Sunday Brunch." "Wrong-first-version" not "Chef's Journey." The slight-off naming IS the brand signal — a Status Builder catches it instantly; a casual guest doesn't notice; nobody is alienated.
  • Audience tier: SB (catches the off-rhythm — it's a status signal); CC + CB benign-but-doesn't-care
  • Channel: N/A — applied across every channel at naming
  • Voice anchor: Sutherland (oblique by design)
  • OS owner: Julius (name-review gate at Campaign creation) + cross-helper guideline
  • Trigger: Applied at Campaign creation
  • Attribution hook: N/A — naming guideline

Trend 9 — Trend analysis has gone mainstream (algorithmic literacy is two-way)

What it means. Brandwatch records 29% growth in social-listening conversations (with a 106% increase in new authors) and 54% growth in algorithm/marketing-tactic discussions (with 80% first-time contributors)³²; 64% of shoppers use generative AI tools³²; the Sophia James "Group 7" TikTok experiment is the cited example where an algorithm test went viral as the content itself. The implication: consumers can now read marketing playbooks and call out the ones being run on them.

Why it matters for Michiu. The audience that books at Michiu — especially Status Builders and the younger Classic Connoisseurs — increasingly understands the engineering behind their feed. They know when they're being retargeted. They notice when a restaurant suddenly posts twice a day for two weeks before going dormant. They read promo codes as flags for who you treat as which segment. The cost of using a "marketing trick" is that the trick is visible AS a trick to the people you most want to keep, and gets read as inauthenticity by a tier that rewards authenticity above almost any other variable. The strategic answer is the opposite of what most brands do: surface our own methods. Be the transparent one in the category.

NL-specific: Dutch consumers are particularly sensitized to "is this AI?" / "is this marketing?" framing²³¹⁶. The DDMA 2026 focus on "responsible data use and customer relationships" is exactly the framing that converts Dutch trust into bookings. NL is structurally weather-aligned with transparent listening; transparent-marketing language is structurally weather-against.

Risk if ignored. We adopt the kind of patterned, slightly-too-frequent posting cadence that Status Builders read as marketing-program output; the IG/TikTok audience tunes out. Or we use a promo-code mechanic our audience decodes in 5 seconds; we are publicly identified as the kind of place that runs them.

Tactics

• Tactic 9.1 — Insight's quarterly internal "what changed" digest

  • Action: Every quarter, Insight publishes a 1,500-word internal-only team digest: what changed on IG vs TikTok vs LinkedIn this quarter; what algorithm-side shifts we observed (delivered to the team via the Universal Approval Queue notes); what we did differently and what worked vs. didn't. This is not for external use. Its purpose is to keep our cadence smart — and to ensure when we do break a pattern (Tactic 9.2) we have data behind it.
  • Audience tier: Internal — improves execution for all three tiers
  • Channel: internal — Slack/email + the Marketing OS dashboard
  • Voice anchor: Kahneman (decision-clarity)
  • OS owner: Insight (full ownership)
  • Trigger: Quarterly Insight cron
  • Attribution hook: N/A — operational
  • Notes: The trust-score-per-Power-Up audit metric (docs/marketing-os-build-plan.md §8.4) feeds this digest.

• Tactic 9.2 — The transparency footnote (opportunistic)

  • Action: Occasionally, in a caption that touches a measurement decision (e.g., a save-vs-like signal, a return-rate insight), include a short footnote-style line: "We count saves because they convert; we don't count followers because they don't." Or: "Yes — this post will be retargeted at people who saved it. We tell you because we'd want to know." Frequency: 1–2 per quarter, never patterned. Make it earn its place.
  • Audience tier: SB + CC (both notice; CB neutral)
  • Channel: IG (primary) + occasional LinkedIn
  • Voice anchor: Kahneman + GaryVee (kinetic + transparent)
  • OS owner: Zuck drafts; Julius approves the cadence (no more than 2 per quarter)
  • Trigger: Opportunistic — Zuck flags candidates; Julius gates
  • Attribution hook: Brand-only. Leading indicator: comment quality + reply rate on the footnoted posts vs. baseline (Insight measures)

• Tactic 9.3 — The promo-code guardrail (Roy + Julius hard rule)

  • Action: No promo codes that read as segment-tags to the audience. "FRIENDSANDFAMILY20", "INSTAGRAM10", "WELCOME15" — all banned. If we run a paid offer at all (very rare; mostly we don't), the code is generic and unguessable (m_campaign slug + a short hash) or it's tied to a Campaign-specific gesture that's already known internally. The audience can decode brand-marketing codes faster than we can write them; using them collapses trust faster than the discount earns booking.
  • Audience tier: Guardrail across all three (most-protective of SB + CC trust)
  • Channel: N/A — applies to Roy's Google Ads + Zuck's organic + Clara's lifecycle sends
  • Voice anchor: N/A (guardrail)
  • OS owner: Julius (block-level rule); Roy + Clara comply
  • Trigger: Applied at Campaign creation
  • Attribution hook: N/A

Trend 10 — AI is reshaping how people find brands (GEO) — see §4 for the full plan

What it means. 67% of marketers say consumer search behavior is shifting toward AI/social discovery; half of consumers use AI-powered search; Reddit and LinkedIn are now in the top-5 LLM-cited domains¹⁴. New AI browsers — Arc, Perplexity Comet, Dia — are reshaping how queries get answered. Brandwatch's framing: this is the biggest change to online visibility since search engines were introduced.

Why it matters for Michiu. This is the single highest-leverage section of this entire strategy (per §0). Specific reasoning + full audit + content roadmap + citation strategy + 12-prompt quarterly test suite all live in §4. The two-sentence summary here:

The queries that matter for Michiu — "best omakase in Amsterdam under €150," "restaurant near RAI Amsterdam business dinner," "Cantonese-Japanese restaurant Netherlands" — have no established LLM answer-set yet. The window is now; six months of long-form chef content + Reddit cultivation + Dutch press citations puts us in the answer-set before competitors notice the lane exists.

NL-specific: NL is one of the highest LinkedIn-penetration markets globally (31%)²² AND Reddit + LinkedIn are top-5 LLM-cited domains¹⁴ — meaning the GEO play in NL has a structural advantage no global benchmark restaurant can replicate. Penn's NL-language press citation strategy (Het Parool, NRC, Volkskrant, Misset Horeca, Foodie Amsterdam, Eet.nu, Iens) is the leverage point. Carlos owns the multi-language structured-data layer (NL primary, EN strong-secondary, CN/JP minimal).

Risk if ignored. A competitor figures this out in Q1 2026 and occupies the LLM answer-set. We then have to displace them, which is materially harder than being first into the set.

Tactics summary (full tactic table is in §4):

• Tactic 10.1 — Six long-form essays on michiu.nl over 2026 (chef story, sourcing, sake program, signature-dish origin, Cantonese-Japanese position, RAI corporate dining). Owner: Penn drafts + Michelle voices. Audience tier: CC + CB. Trigger: bi-monthly cadence. Attribution: GEO feed + LinkedIn excerpts with m_campaign=longform_<piece>.
• Tactic 10.2 — Insight Power-Up running the 12-prompt quarterly test suite across ChatGPT / Perplexity / Claude / Gemini / Copilot / Apple Intelligence. Results stored in memory_documents for trend tracking. Owner: Insight. Audience tier: Internal — supports all three. Trigger: quarterly cron.
• Tactic 10.3 — Carlos owns multi-language GBP + Schema.org Restaurant markup + Menu + OpeningHoursSpecification + dietary annotations on michiu.nl. NL primary, EN strong-secondary, CN/JP minimal. Audience tier: CC + CB primarily. Trigger: continuous; quarterly audit.
• Tactic 10.4 — Penn's Reddit + Dutch-press citation cultivation. r/Amsterdam, r/thenetherlands, r/AskCulinary, r/FineDining; Het Parool, NRC, Volkskrant, Misset Horeca, Foodie Amsterdam, Time Out Amsterdam (NL edition). Audience tier: CC + CB. Trigger: ongoing; monthly outreach review. Attribution: m_campaign=press_<outlet-slug> per cite.

See §4 for the audit checklist, full content roadmap, full citation strategy with target outlets ranked by GEO impact, and the 12-prompt quarterly test suite (with NL-language queries explicit).

Trend 11 — Gen Alpha: the next big audience is growing up

What it means. Oldest Gen Alphas turn 16 in 2026 with collective $100B spending power³³. Brandwatch cites 14-year-old Amyah Bennett (4M YouTube subscribers) as the cohort archetype, and Minecraft + Roblox as the expected brand-participation spaces. The cohort expects interactive experiences, trusts creators over brands, and blurs online/offline distinctions.

Why it matters for Michiu. Honestly: not much, in 2026. Michiu is not a 16-year-old's destination. The closest indirect angle — today's older Status Builders' younger siblings — does not buy tasting-menu dinners in 2026. We acknowledge the trend and skip it strategically. Revisit when the cohort enters early adulthood (2028+).

NL-specific: Same conclusion. Dutch Gen Alpha follows the global pattern. No NL-specific signal that changes the strategic skip.

Risk if ignored. None for 2026. The risk emerges in 2028–2030 if we have built no cultural surface area with the younger end of Status Builders by then. Note as a 2028 revisit and move on.

Tactics. None for 2026. Re-evaluate in the 2028 strategy refresh.

One honest caveat: the oldest end of Gen Z (born 1997–2000) is fully inside our Status Builders tier today, and is the most-platform-fluent segment of that tier. When trend 6 (cast-led) content goes onto TikTok and Threads (NL daily-platform-count is dropping but Threads is still rising), the audience receiving it is structurally close to Gen Alpha behaviorally even if they're 25–28 chronologically. That's a Status Builders tactic, not a Gen Alpha tactic. Don't confuse the two.

3. Benchmark scan

[!note] Verification methodology Venues below are verified via live web research (May 2026, pass-4 complete). The only remaining marker is [DESK-RESEARCH-UNRESOLVED] on the Yama entry — see §3.5 for the closing rationale (owner input required). Brand-presence claims (IG follower counts, Michelin status, content cadence) are point-in-time as of May 2026 and will drift; the doc should be re-verified annually as part of the strategy refresh cycle.

3.1 Amsterdam comparison set

3.2 Global Cantonese / Japanese / Asian benchmarks

3.3 Patterns to ADOPT (expanded in pass-4 to nine — Sazenka × 2 + Yardbird + Don Julio additions)

1. The Atomix per-course-card system (specificity made tactile). A printed card per course. Dish name. Ingredient origin. One chef sentence. The diner takes it home. The card becomes (a) a souvenir (for CC), (b) an IG asset (for SB), (c) a verbal memory aid that makes the "Glad you noticed [dish]" review reply (per review-prompt.ts) more likely because the diner can name the dish. This is a strict upgrade on a printed menu — printable on the existing card stock used for the Circle birthday gesture (Tactic 4.3). Implementation cost: small (printing + a 30-minute Michelle-interview-per-dish for the card text). Time to launch: 4–6 weeks.

2. The Tatiana cultural-calendar-cross-programming pattern, applied to Cantonese + Japanese moments (already partially in trend 2 tactics). Tatiana succeeds because the venue is embedded in a cultural institution (Lincoln Center) and moves with its calendar. Michiu doesn't have a single physical institution to anchor against, but it has two cultural calendars (Cantonese festivals + Japanese seasonal). The pattern to adopt: don't just acknowledge these moments — anchor monthly programming against them year-round so that the cultural calendar IS the operating cadence, not an overlay. Trend 2 tactics start this; trend 5 (nostalgia) extends it; §9 (anchor calendar) finalizes it.

3. The Mott 32 signature-dish-as-brand-spine. Across 8 cities, Mott 32 is recognizable by its apple wood-smoked Iberico pork. Same dish, every venue. Michiu does not multi-city, but the principle scales down: one dish that is the answer to "what is Michiu." It appears in our long-form content (Pillar 1 trend 10 + §4), it leads our menu, it is what we feed to the LLM grounding, it is what every press piece references. Today we do not have this dish identified explicitly in our outbound content — naming it is a §6 task (Brand Memory: brand_dishes with is_signature_flag).

4. The Den "playful artifact" pattern (pass-3 addition). Hasegawa's "Dentucky Fried Chicken" — a custom takeout box with the chef's smiling face on it — converts a fast-food joke into a Hasegawa-signature object that exists in the world after the meal ends. The carrot-cut-as-smiley-face has the same property. The artifact is the marketing. This is the physical extension of the Mott 32 spinal-dish pattern (#3): not just one signature dish, but one signature object the guest carries home that re-enters the discovery loop. Direct application: extend Tactic 4.5 (pastry takeaway box) into a Michiu-named, Michiu-marked box that becomes the carried-home artifact. Implementation cost: small. Time to launch: 8–10 weeks (box design + supplier sourcing). Owner: Sun proposes Campaign archetype; Zuck owns content; pastry lead executes.

5. The Ikoyi diaspora-cuisine-at-technique-tier framing (pass-3 addition). Ikoyi positions itself as the West African spice tradition Chef Chan grew up with, rendered with seasonal British craft — NOT "African fusion" (the genre-flattening term, equivalent to "fusion" for us). Two Michelin stars vindicate the framing. The pattern: name the tradition and the technique-tier in the same breath; let press write the diaspora story without commodifying it. Pass-4 update: Ikoyi remains relevant at 2-star, but Sazenka (pattern 6) is now the structural twin at 3-star. Use Ikoyi for position-essay tone; use Sazenka for philosophy-name discipline.

6. The Sazenka named-philosophy framing (pass-4 addition — Michiu's structural twin at 3-star tier). Sazenka calls its approach "wakon-kansai" = Japanese soul + Chinese technique⁵⁰. A named philosophy, two characters, that answers the "why these two cuisines?" question in a phrase. This goes one structural layer deeper than Ikoyi's framing (pattern 5): rather than describing the position in a sentence, name it in a phrase. The named philosophy becomes the LLM-grounding answer, the press-cite tag, and the menu header in one move. For Michiu: Michelle's Cantonese-Japanese position essay (Sep 2026, §4.3) should land a Michiu-coined philosophy-name analogous to "wakon-kansai" — surfaced before Penn pitches Tier-1 press, so the press uses the term rather than coining their own. Implementation cost: low (a writing exercise + owner approval). Time to launch: 4–6 weeks. Owner: Michelle + Penn. The single highest-leverage tactical addition from pass-4 research.

7. The Sazenka four-kanji menu writing (pass-4 addition) — specificity-as-poetry, the inverse of Atomix per-course cards. Sazenka describes each dish in four kanji characters — deliberately, to "stir the imagination of diners and leave them to ponder the possibilities"⁵⁰. This is the mirror of Atomix's per-course-card pattern (#1): Atomix gives more information per dish; Sazenka gives deliberately less. Both work because both are extreme — the middle (a one-sentence ingredient-listing description) is the generic-restaurant-menu default and the AI-slop trap. For Michiu: per-dish menu lines can either go long (Atomix per-course card) or short (Sazenka tight phrase) but never medium. The medium register is the genre default and the rejection surface. Implementation: Michelle + Zuck rewrite the menu copy under the new rule; pair with Tactic 5.1 (chef's-note menu redesign) and pattern 1 (per-course cards) so the three surfaces (menu line + card + IG caption) form a deliberate text-length-and-register ladder, not a homogeneous middle.

8. The Yardbird single-illustrator visual-identity (pass-4 addition). Yardbird collaborates with one artist — Evan Hecox — whose tattoo-like sketches and Hong Kong collages run through menus, merch, IG, and the James-Beard-winning Chicken and Charcoal cookbook for over a decade⁵⁵. The visual language is as recognizable as the food. This is the visual analogue of pattern 3 (Mott 32's spinal-dish): one visual signature alongside one culinary signature. Critically, a single illustrator's hand is the structural defense against the AI-slop visual default (mood-lit polish) — algorithms cannot homogenize a hand that is identifiable. For Michiu: commission a single Dutch or international illustrator on retainer to develop a consistent vocabulary across menu cards, the takeaway artifact box (pattern 4), and IG carousels. Implementation cost: medium (retainer + 6–10 weeks of initial work). Time to launch: 12–16 weeks. Owner: Sun proposes Campaign archetype; Zuck owns content; pastry / packaging lead executes physical surfaces.

9. The Don Julio "Art of Hospitality precedes food rankings" pattern (pass-4 addition). Don Julio won the Art of Hospitality Award in 2018 — before climbing into the World's 50 Best top-10⁵⁷. The narrative order matters: hospitality discipline → award-driven press cycle → food-ranking attention. Pablo Rivero's Latin America's Best Sommelier (2022) → World's Best Sommelier (2024) path is the same shape — the person-level awards compound the venue-level reputation. For Michiu: prioritize Anna's FOH-as-craft surface (and surface-able awards: Art of Hospitality, GM-of-the-year, Sommelier nominations) BEFORE chasing food-only star recognition. Implementation: Anna's FOH playbook + Penn's award-nomination submissions tracker. Time to launch: ongoing — annual award cycles. Owner: Anna + Penn (joint).

Pass-3 observation: pattern 1 (Atomix cards) + pattern 4 (Den artifact) are the same family — making the meal carry a physical object out the door that re-enters the discovery loop. Both extend the §1.1 specificity principle into the post-meal world. Consider them complementary, not duplicative: the card is per-dish (during meal); the artifact is per-visit (after meal).

Pass-4 observation: patterns 1 + 7 are paired opposites — Atomix cards (per-dish long-form) and Sazenka four-kanji (per-dish ultra-short). Both work because both reject the medium-length, ingredient-listing default that AI-slop occupies. Tactical implication: every dish-level text surface in Michiu should be either long-and-specific (per-course card pattern) or short-and-evocative (kanji-tight pattern). Audit every menu surface, IG caption, and press one-liner against this binary.

Pass-4 observation: patterns 3 (spinal dish) + 8 (single illustrator) are paired axes — one is the culinary signature, the other is the visual signature. A venue that nails both has two independent recognizability anchors — twice the surface area for press, LLM grounding, and word-of-mouth. Yardbird does it; Mott 32 does it (a different illustrator-equivalent in their design system); Michiu currently does neither. Both are §6 Brand Memory entries waiting to be made.

3.4 Four patterns to AVOID (pass-4 added the Lung King Heen lesson)

1. The Bougainville / Mr Porter polished-aesthetic register. Both are well-executed locally, both photograph beautifully, both will be increasingly punished in 2026 (Brandwatch trend 1 + DDMA Dutch authenticity preference + Deloitte NL findings on AI-content concern). Their photographic style — high-contrast, mood-lit, color-graded — is the visual grammar that LLMs and AI image-generators reproduce by default. Avoid by inversion: natural light, mid-process shots (not finished plates only), hands in frame, occasional imperfection visible. The trend 1 + trend 3 tactics already prescribe this; do not drift toward the polished-default just because the lighting is "more flattering."

2. The Tatiana celebrity-chef machine. Onwuachi's IG following is real and his Nike/Lexus sponsorships are revenue — but the model requires the chef to be a public figure willing to be the persona. Michelle is owner-chef, not media personality. Pursuing this pattern would mean turning Michelle into something she has not signaled wanting to be, AND it would convert the brand from "the cast is the brand" (trend 6) to "the chef is the brand" — a brittle pivot if Michelle ever wants out of the spotlight. Do not model Michiu's chef-LinkedIn presence on Onwuachi. Model it on Den's Zaiyu Hasegawa — 52K personal-IG followers, chef-led, occasionally playful (the Dentucky-FC box, the smiley-face carrot), never marketing-mode⁴⁹. Hasegawa's bio is one sentence ("cooking to make happiness for people around the world"); his restaurant-level account is restrained; the playfulness lives in the gesture (the box, the carrot), not the framing. Same shape as our gamification §1.3 rule — verified at the Michelin-tier benchmark. Humble Chicken's Angelo Sato is the secondary reference (also 2 Michelin, same playful-sincerity register)⁵³.

3. The Sushi Park radical-restraint model (full version). Saying less is a §1.8 principle — but Sushi Park's "almost no social presence" only works because demand exceeds supply by a wide enough margin that no-marketing IS the marketing. Michiu does not yet have that demand-supply imbalance. Trying to be Sushi Park before earning it would read as a marketing pose, not as confidence. The discipline (less, more weight) is the right read; the full posture is premature.

4. The Lung King Heen hotel-anchored-Cantonese-single-narrator-dependency model (pass-4 addition). The world's first 3-Michelin-starred Chinese restaurant held the crown for 14 consecutive years (2008–2022) and lost a star in the 2023 Hong Kong & Macau guide⁴⁶, despite the technical execution remaining strong on press accounts. The signal in the press cycle: Chef Chan Yan-tak was conspicuously absent from the 2023 Michelin event for the first time in over a decade. The brand had not built a distributed narrative — no IG-native cast presence, no venue-level identity independent of Four Seasons HK, no second-chef succession story in the public surface. When the single narrator stepped back, the brand surface had nothing to fall back on. This is exactly what trend 6 (employees-as-architects) prescribes against. For Michiu: Michelle's preferred quiet posture is correct (Den / Hasegawa model), BUT the cast must still be camera-ready (§1.4) so the brand survives any single-person variance — illness, sabbatical, focus-shift to a second venue, succession. Distributing narrative is the structural defense; the cast is the brand precisely because no single person can be. Use Lung King Heen as the recurring cautionary worked example in §1.4 (cast is the brand) — same cuisine tier, opposite distribution strategy, demonstrably fragile outcome.

3.5 What's still missing — remaining benchmark gaps after pass 4

Pass-4 closed (May 2026):

• Global: Yardbird (HK) ✓, Pak Loh (HK) ✓, Lung King Heen (HK — including the 2023 demotion finding, now §3.4 pattern 4) ✓, Sazenka (Tokyo — now Michiu's nearest structural twin globally; surfaces §3.3 patterns 6 + 7) ✓, Narisawa (Tokyo, expanded from partial) ✓, Quintonil (CDMX — surfaces §3.3 dual-brand observation) ✓, Don Julio (BA — surfaces §3.3 pattern 9) ✓
• Amsterdam: Restaurant DS (De Baarsjes, schoolhouse-aesthetic-tension precedent) ✓, Choux (chef Merlijn van Berlo confirmed; pass-3 had a name guess that did not match) ✓, Flore (the venue formerly known as Bord'Eau — discovered to have been rebranded under Bas van Kranen with no-meat/no-dairy concept, April 2025) ✓, Restaurant Showw (newly identified — Gelrestraat 28, directly next to Amsterdam RAI; 1 Michelin + Sommelier-of-the-Year — the actual RAI-adjacent Michelin peer for the Corporate Booker tier, missed in passes 1–3) ✓

Pattern-count change pass-3 → pass-4: §3.3 ADOPT 5 → 9; §3.4 AVOID 3 → 4.

Single net-new finding most worth flagging: Restaurant Showw is the proximal RAI-adjacent Michelin competitor; the §3.1 inclusion is more important than the global venue additions for Corporate Booker positioning. §2 trend 6 + §5.5 (LinkedIn / press for Corporate Bookers) and the RAI-Scheldestraat strategy should now treat Showw as the named competitor, not just the Scheldestraat trio.

Still open (pass-5+, none gate tactical work):

• Yama — public search did not surface a venue with a public web / social surface in Amsterdam under this name; owner direct input required (Chef Chau guests there occasionally per project_michiu_principals.md — Michelle / Chef Chau is the source). Not closable from desk research.
• Pattern-cluster gaps deferred from pass-3 that genuinely don't gate tactics: Bombay Canteen / Trishna / Indian Accent (London/Mumbai/Delhi); Maido (Lima — Nikkei cuisine, structurally adjacent to Michiu's position); Schloss Schauenstein (CH — quiet-chef-genius model). These would extend §3.2 but the existing global set (Atomix, Tatiana, Mott 32, Lung King Heen, Pak Loh, Sushi Park, Den, Sazenka, Narisawa, Ikoyi, Humble Chicken, Yardbird, Quintonil, Don Julio + Endo as historical note) is already comprehensive for the §3.3 pattern-extraction purpose.

Pattern note: Hong Kong cluster verified comprehensive; the Tokyo cluster's Sazenka surfaced the highest-leverage pass-4 finding (the wakon-kansai named-philosophy framing); the LatAm cluster contributed the dual-brand and hospitality-precedes-rankings patterns. The benchmark scan is now structurally complete enough that future passes should focus on new venues that open or rebrand, not on padding the existing global set further.

4. GEO / AI discovery action plan — THE HIGHEST-LEVERAGE SECTION

[!warning] Why this section matters more than any other Per §0 strategic shift #5: every other tactic in this strategy assumes Michiu is in the LLM answer-set when the right query is asked. If we are NOT in that set, none of the other tactics compensate. The window is open in Q1–Q3 2026; it closes when a competitor surfaces.

4.1 Current-state assessment

The 2026 GEO landscape (verified May 2026):

• Reddit accounts for ~40% of all AI-platform citations across major models. Perplexity is the most Reddit-heavy (24% of total citations); ChatGPT also leans heavily on Reddit, Wikipedia, Forbes, Business Insider⁵⁸.
• AI search engines cite Reddit, YouTube, and LinkedIn most⁵⁹ for the categories that matter to local-business discovery.
• For Perplexity specifically: Yelp (0.8%), TripAdvisor (0.6%), G2 (0.6%) — restaurant-review platforms appear, but at single-digit-percentage rates compared to Reddit's 24%⁵⁸.
• Schema-marked content shows 30–40% higher visibility in AI-generated answers⁶⁰.
• Gartner predicts traditional search engine volume will drop 25% by end of 2026 as users shift to AI-generated answers; AI-referral traffic to small business websites grew 123% in 2025 and is still accelerating⁶⁰.
• NL-specific: Joël Broekaert's NRC reviews can produce four-reservations-per-second spikes for positive reviews⁶¹ — the press citation lever is unusually strong in NL because the Dutch food-press concentration is high and the audience-trust-in-press level remains elevated.

What this means for Michiu's queue: the highest-leverage moves are (a) get into Reddit-cited threads, (b) earn NL-press citations, (c) ship Schema.org Restaurant markup on michiu.nl, (d) publish enough long-form fact-density content that LLMs can attribute Michiu to specific dishes, suppliers, and the Cantonese-Japanese position. NOT TripAdvisor optimization. NOT Google Maps SEO alone. The discovery game has moved.

4.1.1 Michiu's Q1 2026 surface in the discovery layer (pass-4 measurement)

[!warning] Empirical baseline run May 2026 — 0/9 queries surfaced Michiu Running the §4.5 test suite (sample of 9 queries spanning NL + EN, SB + CC + CB intents) returned zero mentions of Michiu in any answer body. Brand-name search ("Michiu Amsterdam restaurant") works — the IG, TheFork, Tripadvisor, Restaurant Guru, and Foursquare profiles all surface, and michiu.nl/en/home-en/ is indexed. Discovery-intent searches do not surface Michiu at all. The §0 shift #5 thesis ("the LLM answer-set has not locked in yet for the queries that matter") is empirically validated — and so is the urgency: competitors are surfacing, just for the wrong cuisine framing.

What surfaces instead of Michiu (the competitive map as LLMs currently see it):

Three concrete signal findings extractable without a successful site fetch (May 2026):

1. Google-surfaced page title is "MICHIU Lounge • Culinary Asian Cuisine" — contains both an outdated brand suffix ("Lounge", carried over from a prior positioning) and the AI-slop framing ("Culinary Asian Cuisine") that §1.1, §3.3 pattern 6, and §3.4 explicitly reject. This is the single most concrete, fixable GEO finding in pass-4 — the title tag is what LLMs ingest as the canonical brand description and it currently undermines every downstream tactic in this document.
2. Instagram bio location is set to "Amsterdam Centrum" while the actual address is Maasstraat 102, Rivierenbuurt / Scheldebuurt (Amsterdam-Zuid). This misalignment hurts every Amsterdam-Zuid / Maasstraat / Rivierenbuurt / Scheldebuurt / near-RAI query — most of which are the §0 shift #2 corporate-dining queries.
3. Yelp categorizes Michiu as "Thai" — wrong category. Yelp feeds Perplexity's restaurant-specific citation set (0.8% per ⁵⁸) so even at its low weight this is a hygiene fix.

The geographic re-framing this surfaces: Michiu is not "Amsterdam Centrum" — Maasstraat 102 sits in the Scheldebuurt / Rivierenbuurt, adjacent to the Scheldestraat 400–600m corridor analyzed in rai-scheldestraat-strategy.md. The §0 shift #2 narrative ("own the RAI-adjacent corporate-dining lane") is geographically more defensible than the strategy document currently states — Michiu is the Scheldebuurt-near-RAI Cantonese-Japanese venue. The IG bio + GBP description + meta tags should all reflect this.

A technical caveat surfaced by this audit: michiu.nl/ consistently returned HTTP 503 to direct WebFetch attempts in this session — likely Cloudflare bot-challenge protection. Worth verifying that LLM crawlers (ChatGPT browse, Perplexity, Google AI Overviews) are not similarly challenged. If they are, the GEO investment in long-form content on michiu.nl cannot pay off until the crawler-access layer is fixed. Carlos / engineering action: verify crawler reachability in Google Search Console / Cloudflare bot-allowlist before publishing essay #1 (Jan 2026).

4.2 Audit checklist

Each item: state (current — pass-4 verified from external signal where possible) → target. Owner in brackets. Verification source noted as [ext] = inferred from external surfaces (Google snippet, IG, Yelp etc.) or [unverified] = pass-4 desk audit could not check directly because michiu.nl returned HTTP 503 to WebFetch. Engineering action (Carlos): verify crawler reachability + run a view-source: audit + update this checklist with [verified] rows.

Website / michiu.nl

• Schema.org Restaurant markup — state: [unverified — site 503 to research crawl; assume incomplete since no rich snippets surface in Google for brand-name search] → target: full markup including name, address, telephone, priceRange, servesCuisine (ordered Cantonese, Japanese — §1.7), acceptsReservations, url, image, hasMenu, geo, containedInPlace=Rivierenbuurt/Amsterdam-Zuid [Carlos]
• Schema.org Menu + MenuSection + MenuItem — state: [unverified] → target: full menu reflected in structured data, updated per rotation; pair with §3.3 pattern 7 (Sazenka four-kanji writing) — every menu item should be either long-and-specific or short-and-evocative, never medium [Carlos + Michelle for copy]
• OpeningHoursSpecification — state: [ext: partial — hours surface in Google snippet (M-F 12-10:30, Sat-Sun 4-10:30) meaning Google has them, but unclear whether as structured schema or hard-coded HTML] → target: structured + machine-readable + JSON-LD [Carlos]
• Dietary annotations on dishes (suitableForDiet schema) — state: [unverified; almost certainly absent — no surface in any test query] → target: noted for vegan / vegetarian / gluten-free dishes + parallel non-pork annotations per the Status Builders dietary-dimension memory [Carlos]
• FAQPage schema on a /about or /faq page — state: [ext: absent — no FAQ rich result surfaces for brand-name queries] → target: live, with 8–12 NL + EN entries covering location (especially "near RAI"), group dining, dietary, Circle (described without naming the program), private dining [Penn + Carlos]
• Author / chef bio with Person schema — state: [ext: absent — Michelle Zhang's name does not surface in any LLM answer about Michiu] → target: Michelle's bio page with Person schema, worksFor = Michiu, named role, founding date, separate Person for Chef Chau as guest-at-Yama context per project_michiu_principals.md memory [Penn]
• AggregateRating markup consuming live Google/Zenchef review data — state: [ext: 4.2/486 reviews surface via Restaurant Guru — external-source dependency, suggests the rating is not embedded on michiu.nl itself] → target: live and accurate [Carlos]
• "No AI here" content-policy footnote (Tactic 1.3) — state: [ext: not surfaced] → target: live + linked from every page footer [Julius drafts + Carlos ships]
• NL/EN language toggle with hreflang markup — state: [ext: separate URL paths exist (/en/home-en/ indexed); hreflang implementation unverified] → target: NL primary, EN strong-secondary, schema-validated, both indexed [Carlos]
• Page <title> and <meta description> — state: [ext: VERIFIED PROBLEMATIC — current title is "MICHIU Lounge • Culinary Asian Cuisine" per Google snippet. Contains an outdated brand suffix ("Lounge") AND the §1.1 / §3.3 / §3.4 banned "AI-slop genre framing" ("Culinary Asian Cuisine")] → target: rewrite to a Sazenka-pattern (§3.3 pattern 6) named-philosophy framing — concrete proposal in Michelle's hands but the current title is the single highest-priority fix in this checklist [Penn drafts + Michelle approves + Carlos ships] — Q1 P0 ⁶²

Google Business Profile (GBP)

• GBP claimed and verified — state: [ext: presumed yes — Google surfaces GBP-style info; verify ownership in Search Console] → target: yes [Carlos]
• Primary category — state: [ext: likely generic — Yelp categorizes Michiu as "Thai" which is wrong, and the LLM-surfaced title says "Culinary Asian Cuisine" not "Cantonese". GBP category is presumed similarly off] → target: "Cantonese restaurant" with secondary "Japanese restaurant" (cuisine ordering matters for query matching — §1.7); also "Asian fine dining" if available as tertiary [Carlos] — Q1 P0
• Description (NL primary, EN secondary) — state: [unverified — view of GBP back-end required] → target: 750 chars NL + 750 EN, naming dishes + price band + group capacity + Scheldebuurt / RAI proximity geographic anchor (per §4.1.1 finding — the Scheldebuurt re-framing) [Carlos]
• Photo cadence — state: [unverified] → target: 2–3 new photos per week (kitchen, plates, room), tagged with NL alt-text [Zuck + Carlos]
• Q&A section — state: [unverified] → target: 6–8 owner-answered questions covering group dining, dietary (incl. non-pork parallel — Status Builders dietary memory), parking near RAI, dress code [Carlos]
• Products attribute (the pastry box-of-four — Tactic 4.5) — state: [unverified] → target: live as a GBP product [Carlos]
• Posts / updates — state: [unverified] → target: weekly post during peak cultural-calendar weeks, otherwise bi-weekly [Carlos]
• Bookings link routed to Zenchef with m_campaign=gbp tag — state: [unverified] → target: tagged [Carlos + attribution pipeline]

Instagram (the live cast surface)

• @michiu_nl bio location — state: [ext: VERIFIED PROBLEMATIC — bio says "Amsterdam Centrum" but actual address is Maasstraat 102, Scheldebuurt/Rivierenbuurt, Amsterdam-Zuid] → target: correct the bio location to "Amsterdam-Zuid · Maasstraat 102 · 5 min van RAI" (or the EN/NL alternation that fits IG's 150-char limit) [Zuck] — Q1 P0 ⁶²
• IG bio link — state: [unverified — assumed Linktree or single URL] → target: tracked link to a landing page that captures m_campaign=instagram_bio then forwards to Zenchef [Zuck + Carlos]

Other location surfaces

• Apple Maps Connect / Apple Business Connect — state: [unverified] → target: claimed + parity with GBP [Carlos]
• Bing Places — state: [unverified] → target: claimed + populated (Bing feeds Copilot answers) [Carlos]
• Eet.nu, Iens, TheFork NL — state: [ext: TheFork verified present at thefork.com/restaurant/michiu-r251285; Eet.nu/Iens unverified] → target: managed; review responses through Siren [Siren + Penn]
• TripAdvisor + Yelp — state: [ext: VERIFIED — TripAdvisor lists neighborhood as "Rivierenbuurt"; Yelp mis-categorizes Michiu as "Thai"] → target: TripAdvisor neighborhood OK; Yelp category fix to "Cantonese, Japanese, Asian Fusion" — Q1 P0 [Siren]
• Foursquare — state: [ext: VERIFIED — present, neighborhood tag "Scheldebuurt", address Maasstraat 102] → target: keep as-is; the Scheldebuurt tag is correct and useful [Siren]
• Restaurant Guru — state: [ext: VERIFIED — 4.2/486 reviews] → target: keep listed; this is the external-source feeding the AggregateRating on michiu.nl, so a refactor of the AggregateRating source dependency is a separate Carlos task [Carlos]
• Wikipedia stub — state: [ext: VERIFIED ABSENT] → target: a verifiable stub article exists (Wikipedia citations carry disproportionate LLM-grounding weight). Must be sourced from real press cites — i.e., earn the press first, then the Wikipedia stub becomes uncontroversial. [Penn — but only after at least 3 NL-press cites exist]

LinkedIn (NL has world-leading penetration²²)

• Michiu company page — state: [unverified — separate search required] → target: active, weekly content per §5 channel playbook [Penn + Zuck]
• Michelle's personal LinkedIn — state: [unverified] → target: posting cadence per Tactics 6.1, 3.4, 7.1, 7.2 (essays + cast features) [Penn]
• Employee-affiliated LinkedIn profiles — state: [unverified] → target: at least 6 cast members list Michiu as employer with current title (the 3% / 30% lift mechanic per Brandwatch trend 6 needs this baseline) [Sun + Insight tracks]

4.3 Content roadmap — 6 long-form essays on michiu.nl over 2026

Bi-monthly cadence. Each essay is the GEO chunk-set anchor for a category of LLM query. Penn drafts, Michelle voices, Julius approves the specificity rule (every essay must name dates, places, people, or measurements).

Cadence rule: publish on the first Tuesday of the listed month at 09:00 CET. NL-language version + EN-language version both live at launch. Each essay is 1,500–2,500 words. Each essay opens with a single dated, named, specific moment in the first 3 sentences (the LLM-grounding hook).

4.4 Citation strategy

Goal: 8–12 cites across NL + global press over 2026, plus active surfaces on 3–4 Reddit threads. All cites get m_campaign=press_<outlet-slug> for attribution; Reddit cultivation is brand-only.

Tier 1 — NL press (highest leverage; Joël Broekaert / NRC alone produces measurable booking spikes⁶¹)

Tier 2 — Global English-language

Tier 3 — Reddit (the single most-cited domain in AI answers across all major LLMs⁵⁸)

Goal: become organically referenced in 3–4 active threads by year-end 2026. Do not astroturf. The cultivation method is:

1. Listen first. Insight Power-Up monitors r/Amsterdam, r/thenetherlands, r/AskCulinary, r/FineDining, r/Sake for queries that mention Cantonese / Japanese / Amsterdam Zuid / RAI dinner. Weekly digest to Penn.
2. Reply when a genuine question exists. From Michelle's personal Reddit account (declared affiliation, not anonymous). One or two replies a quarter. Specific, useful, no marketing.
3. Encourage Circle members organically — when a member tells us they posted on Reddit (rare; happens), thank them. Don't ask them to.
4. Never run a Reddit campaign. Astroturfing is detected, costs trust permanently, and reverses the GEO benefit.

Tier 4 — Hospitality / craft awards pipeline (pass-4 addition — per Don Julio §3.3 pattern 9)

Don Julio's Art of Hospitality Award (2018) preceded the World's 50 Best top-10 climb; Pablo Rivero's Latin America's Best Sommelier (2022) → World's Best Sommelier (2024) path compounded⁵⁷. The narrative order is: hospitality discipline → person-level + venue-level awards → press cycles → food-ranking attention. Awards are independently citeable by LLMs (Wikipedia + press releases + the awarding bodies' own sites) — they generate citations at much lower cost than chasing Michelin or 50 Best directly.

Rule: do not submit to an award before there is a multi-year demonstration in the SOP. A premature submission that doesn't win is a press cycle missed; a submission timed to a maturing operational story is a press cycle earned. Penn owns the submission calendar; Anna owns the operational eligibility surface; Michelle approves each submission individually.

4.5 Quarterly test query suite (12 prompts; NL + EN; Insight-Power-Up-automated)

Run each prompt across ChatGPT, Perplexity, Claude, Gemini, Copilot, and Apple Intelligence every quarter (last week of Mar, Jun, Sep, Dec). Capture: is Michiu mentioned? In what rank? With what attribution (cited source)? Store results in memory_documents.chunk_set='geo_test_<quarter>' for longitudinal tracking.

NL-language prompts (6) — addresses primary-market behavior

1. "Beste Cantonees restaurant Amsterdam" — SB + CC intent
2. "Restaurant bij de RAI Amsterdam voor een zakendiner" — CB intent
3. "Beste omakase Amsterdam" — SB intent
4. "Waar uit eten in Amsterdam-Zuid voor een speciale gelegenheid" — CC intent
5. "Cantonees-Japans restaurant Nederland" — position-test
6. "Restaurant Amsterdam met chef's table" — CC + CB intent

EN-language prompts (6) — addresses international + RAI-event-week traffic

7. "Best Cantonese-Japanese restaurant in Amsterdam" — position-test
8. "Where to take a senior client to dinner in Amsterdam Zuid" — CB intent
9. "Best omakase in Amsterdam under €150" — SB intent (price-banded)
10. "Restaurant near the RAI for a business dinner" — CB intent
11. "Hidden gem restaurant Amsterdam 2026" — SB intent
12. "Where to celebrate a promotion in Amsterdam" — SB + CC intent

Scoring rubric (per prompt × per LLM):

• 3 — Michiu named in top-3 with at least one specific detail (a dish, the position, the chef)
• 2 — Michiu named in answer but without specificity
• 1 — Michiu mentioned only as a list-tail with no detail
• 0 — Not mentioned

Q1 2026 baseline measurement (pass-4, sample of 9 of the 12 prompts run via Google AI-grounded search May 2026):

[!warning] Q1 2026 baseline = 0.00 Aggregate score moves from 0.00 (Q1 2026 measured baseline) to 1.0+ by Q4 2026 (every prompt × every LLM produces some Michiu mention). 2027 target: 2.0+. The §0 strategic-shift-#5 thesis ("the LLM answer-set has not locked in") is empirically validated — but the same measurement also says competitors are surfacing for the queries that matter, so the lane is open in Q1–Q3, narrowing thereafter. Window: 6–9 months.

The leading indicator (weekly Insight dashboard): number of times Michiu was cited in the source attributions shown by Perplexity / ChatGPT / Claude when answering food queries about Amsterdam. This is measurable via the Insight Power-Up scraping the citation list, not just the answer text.

4.6 Immediate Q1 priorities (pass-4 addition — surfaced by the §4.1.1 baseline audit)

Five concrete fixes that the §4.1.1 baseline measurement made surfaceable. Each is small, fast, and unblocks downstream tactics. None of these are roadmap items — they are pre-roadmap hygiene that has to ship before the §4.3 essay schedule has any chance of moving the §4.5 score.

Sequencing: fixes 2, 3, 5, 6 can ship today. Fix 4 needs GBP login. Fixes 1 + 7 are both gated on the Michelle-approval philosophy-name (§4.3 row 5) — the philosophy-name is the only Q1 P0 input that requires owner / chef input, and it unlocks two title/copy fixes simultaneously.

5. Channel playbook

[!tip] Cadence-per-tier is rebuilt around §1.8 Less, with more weight. A weekly piece of substance beats four daily filler posts in 2026 NL. Each channel section names the floor and ceiling cadence — never the average. The floor is the discipline; the ceiling is the brand-safety governor.

5.0 Cross-channel deployment rules + current-state audit (pass-4 addition)

Pass-4 work in §3 surfaced five structural patterns that are channel-agnostic — they govern every surface in §5.1–§5.10 simultaneously. The §4.1.1 baseline measurement also surfaced concrete verified-state findings about Michiu's actual surface in each channel. Both belong here before any per-channel detail.

5.0.1 Four cross-channel deployment rules

1. The Sazenka philosophy-name (§3.3 pattern 6) is the through-line everywhere. Once Michelle approves the Michiu-coined named philosophy (gated as §4.3 row 5 + §4.6 P0 #1), it appears: in the michiu.nl <title>, the GBP description, the IG bio, the TikTok bio, the LinkedIn company-page tagline, the press one-liner, and the first sentence of every long-form essay. Single phrase, every surface, identical wording. The single-phrase-everywhere rule is what makes a named philosophy grounding-worthy to LLMs — fragmented framings produce fragmented attribution.
2. The Yardbird single-illustrator vocabulary (§3.3 pattern 8) is the visual through-line. One commissioned artist's hand runs across IG carousel cards, TikTok end-cards, GBP photo overlays, takeaway-artifact box design (Tactic 4.5 + §3.3 pattern 4 Den), menu cards (§3.3 pattern 1 Atomix), LinkedIn cover image. Algorithms cannot homogenize a hand that is identifiable — this is the structural defense against the AI-slop visual default (§3.4 pattern 1). Until commissioned, IG + TikTok content style stays mid-process / hands-in-frame / natural-light per the current §5.1 + §5.2 principles.
3. The Quintonil dual-brand presence (§3.2) — Anna shows up alongside Michelle on every cast-eligible surface. Anna's FOH-hospitality voice should appear in: IG cast-monthly anchors (§5.1 pillar 2), LinkedIn cast features, in-restaurant chef's-table moments (§5.3), the in-room copy on the chef's-note menu (Tactic 5.1). The Quintonil structure (three named handles — chef + manager + venue) at #3-World-50-Best tier is the empirical proof of resilience.
4. The Lung King Heen distribution-failure (§3.4 pattern 4) governs every channel's cadence ceiling. No week's cadence on any channel may be 100% Michelle-fronted. A single-narrator-dependent surface is structurally fragile — the LKH demotion is the worked example at the same cuisine tier. Mechanical rule for §5.1 + §5.2 + §5.5: at least 30% of monthly content carries a cast voice that is not Michelle. Zuck enforces; Insight tracks.

5.0.2 Current state across channels (May 2026 verified)

Source: web-search snippets + directory listings + a handful of search-result-extracted bio fragments. Sites under *.michiu.nl are 503-blocking direct WebFetch (suspected Cloudflare bot challenge — see §4.6 P0 #5). Native social platforms (IG, TikTok) are SPA-rendered and similarly opaque to crawlers — every finding below is from the externally-indexed signal.

[!warning] Two pass-4 findings that should be flagged to owner immediately (1) Founding year. Multiple external sources (Creditsafe; the businessrestaurants.nl listing) report Restaurant Michiu B.V. as incorporated in 2012 — 14 years of operation. The §3.2 Pak Loh "future-reference 2046 horizon" framing assumed Michiu is too young to invoke heritage; the verified 14-year track changes that calculus. The 2026 RAI-event-week + cultural-calendar work has more heritage to lean on than the strategy currently credits. Action: confirm with Michelle whether the Michiu name has been at Maasstraat 102 continuously since 2012, or whether there was a concept-reset in between — the answer determines whether the heritage card is fully or only partially playable. (2) €25/person packages on businessrestaurants.nl. The listing offers morning / afternoon / evening packages at €25/p. This is materially below the Status Builders + Classic Connoisseurs + Corporate Bookers price-band assumed throughout this strategy. Action: confirm with Michelle whether (a) the €25 packages remain an active offering, (b) they are an entry-level path that funnels to higher-tier visits, or (c) they should be retired/repositioned. If they remain active and visible on a B2B-directory listing, they undercut the §0 shift #2 corporate-dining premium positioning Penn is being asked to pitch.

5.1 Instagram (Zuck-owned)

Principles

• Specificity is the moat. Name the dish, the supplier, the year, the person.
• Saves > likes. Reels that get saved > Reels that get watched once.
• No grid-matching aesthetic obsession. The feed should look like the kitchen, not a mood board.
• One language per post (NL or EN — never both in caption; alt-text always NL).
• Status Builders are the audience here. Tag tactics accordingly.
• Bio location must read Amsterdam-Zuid · Maasstraat 102 · 5 min van RAI (per §4.6 P0 #2 — currently says "Amsterdam Centrum" — Q1 P0 fix).
• Cast voice ≥ 30% of monthly cadence (§5.0.1 rule 4 — Lung King Heen governor). At least one of every three posts is not Michelle-fronted.
• Visual identity locked to the single commissioned illustrator's vocabulary once §3.3 pattern 8 (Yardbird) is implemented. Until then: mid-process, hands-in-frame, natural-light — never the polished-default register.

Three content pillars

1. Craft visible (~50% of cadence) — hand-folded dumpling clips, plate close-ups with hands in frame, mid-process shots. Powers Tactic 1.1 + 3.2 + 6.1 + 6.3. Voice: Guidara + Sutherland.
2. Cast on camera (~30%) — Tactic 6.1 monthly cast anchors, sommelier picks (6.2 short-form versions), pastry team. Voice: GaryVee + Guidara.
3. Moments + cultural calendar (~20%) — Mid-Autumn, sakura, Lunar New Year, RAI event-week dinners (when Penn-led LinkedIn lands a CB booking, Zuck gets the asset). Voice: Godin.

Cadence

• Floor: 2 posts/week (Reels primary; carousel secondary)
• Ceiling: 4 posts/week during cultural-moment weeks
• Stories: daily during service-active days, but no obligation. Stories die in 24h — don't burn cast energy on them.
• Posting times: 11:30 + 17:30 CET (NL audience peak)

Power-Ups for Zuck (named for §6)

• craft-clip-weekly — Tactic 1.1
• supplier-carousel-rotation — Tactic 1.2
• cast-monthly-anchor — Tactic 6.1
• pastry-failures-quarterly — Tactic 6.3
• transparency-footnote-gate — Tactic 9.2 (Julius co-owns the cadence gate)

5.2 TikTok (Zuck-owned, secondary to IG but rising in NL 25–44 cohort²²)

[!warning] Existing TikTok content is the baseline to change, not extend Pass-4 audit (May 2026): @michiu_nl TikTok is active, and the representative recent-post style ingested via search is the AI-slop genre (multi-emoji + adjective-stack + hashtag pile — see §5.0.2 table). Every principle below is a rejection of the existing content cadence. Sun + Zuck Q1: audit + retire the legacy posting pattern before publishing the first §3.3-pattern-aligned video. Do not auto-cross-post legacy IG content here.

Principles

• TikTok in NL is no longer just youth. The 25–44 cohort is the fastest-growing²² — that's our Status Builders primary + the younger end of Classic Connoisseurs.
• Native audio. Native pacing. Don't repurpose IG Reels with TikTok captions; rebuild for the platform.
• Vertical kitchen-process content + ambient audio + 1-line captions is the working format. No music libraries.
• Lower polish ceiling than IG. TikTok punishes polish in 2026.
• Captions: zero emoji in the caption body (one emoji per post maximum, only when it carries semantic content — never as decoration). Hashtag stack capped at three hashtags. Adjective-stack ("highest quality", "best", "amazing") is the §1.1 ban; nouns + dates + named ingredients only.
• Cast voice ≥ 30% (§5.0.1 rule 4 — same as §5.1). The §11.1 hypothesis 6 ("cast member willingness to be on TikTok") gates how aggressive this can be — Sun cast 1:1s in Q1 resolve the constraint.

Three content pillars

1. Kitchen process (~60%) — 15–30s clips, ambient audio, single-line caption. The dumpling fold, the wok, the dessert assembly.
2. Cast voices (~25%) — short-form versions of Tactic 6.1 (the sommelier's 30-second sake pick; the pastry lead's "this is what failed today").
3. Off-rhythm (~15%) — Tactic 7.3 in action. Posts that don't read as "restaurant marketing." The dishwasher's 3am Spotify playlist. The empty room at 16:30 before service.

Cadence

• Floor: 1 post/week
• Ceiling: 3/week during high-content moments (menu rotation, cultural calendar)
• Best posting time: 19:00–21:00 CET (NL TikTok evening peak)

Power-Ups for Zuck

• tiktok-kitchen-process — automated capture protocol + scheduler
• cast-tiktok-shortform — extension of Tactic 6.1

5.3 In-restaurant / offline (Sun owns Campaign archetypes; FOH executes)

This is the most-aligned channel for the 2026 Dutch mood (§1.8 / §0 shift 6) AND the lane where the Corporate Booker tier converts.

Principles

• The room IS the channel. Every gesture compounds.
• Felt-never-told everywhere — the dice, the Circle, the positioning (§1.2).
• Photograph-ability is incidental; the moment is for the guest first.
• The cast's authority — sommelier explaining a pour, Michelle plating at the counter — is the asset.

Three content pillars (in-restaurant programming)

1. The dice + variable-reward gestures — Tactic 4.1 (lunch dice), Tactic 4.2 (sake pour), Tactic 4.3 (Circle birthday), Tactic 4.5 (pastry box).
2. Cultural-calendar moments — Mid-Autumn pop-up (2.1), Lunar New Year long table (2.2), Sakura dessert window (2.3), Grandmother Sundays (5.2), Phone-free supper club (8.4).
3. B2B-converting moments — Quarterly event-agent tasting (8.2), chef's-table dinners (8.1), RAI event-week group bookings.

Cadence

• Daily: the dice (Tue–Fri lunch) — once the Campaign launches
• Weekly: standing chef's-table availability (3–4 dinners/week)
• Monthly: at least one cultural-calendar or Grandmother Sunday moment
• Quarterly: phone-free supper club + event-agent tasting + grandmother Sunday + heritage-dish re-issue (4 quarterly anchors that compound)

Power-Ups for Sun (Campaign archetypes — names per §6)

• lunch-dice-2026 (the artifact + protocol — initial launch Power-Up)
• cultural-moment-bookcalendar (cultural calendar → Zenchef pre-booking windows)
• event-agent-tasting-quarterly (8.2)
• phone-free-supper-quarterly (8.4)
• grandmother-sunday-quarterly (5.2)
• chefs-table-capture-protocol (8.1 — Zuck co-owns)

5.4 Email + WhatsApp + Michiu Circle (Clara-owned outbound)

Clara is the lifecycle helper. Email via Resend; WhatsApp via WhatsApp Business adapter (social.HANDOFF.md). The Circle is felt, never announced (§1.2 hard rule #1) — Clara's outbound must NEVER name the tier.

Principles

• Two channels for two registers: WhatsApp is warm + immediate; Email is considered + considered-rare.
• Marketing opt-in flag is mandatory before any send — GDPR + the helper governance.
• Every send is human-approved (Universal Approval Queue — §1.5).
• Specificity rule applies — no "we miss you" templates; the line must reference something.

Three content pillars / flows

1. Birthday flow (Tactic 4.3) — Clara surfaces guest 14 days ahead → human-handwritten card → mailed → arrival gesture in kitchen.
2. Lapsed-guest re-engagement — Clara surfaces guests who haven't visited in 6 months AND have a marketing_opt_in=true flag AND were not lapsed-by-choice (no negative review). Penn co-drafts; tone: warm, specific, no offer attached.
3. Sun-triggered micro-opportunities — Tactic 4.4 rainy-Tuesday push; future Power-Ups (Lunar New Year priority send, RAI-event-week last-minute availability).

Cadence

• Per guest: never more than 4 marketing touches per year (the Dutch less-but-meaningful principle applied to outbound). Birthday + one Lunar New Year priority send + at most 2 opportunistic sends.
• Channel split: birthday card = mail (artifact); rainy-Tuesday = WhatsApp (immediacy); lapsed re-engagement = email (considered).

Power-Ups for Clara

• clara.birthday.window_open (14-day-ahead trigger)
• clara.lapsed.detected (6-month-no-visit, opt-in, no-negative-review composite)
• clara.lny_priority_send (Lunar New Year Circle priority — Tactic 2.2)
• clara.rainy_tuesday_send (composite event from Sun's micro-opportunity Power-Up — Tactic 4.4)

5.5 LinkedIn + Press (Penn-owned) — see §4.4 for the full citation strategy

Pass-4 expansion: LinkedIn is materially separate from press cites — it is a direct distribution channel to the Corporate Booker tier (NL has the world's #1 LinkedIn penetration²²), not just a press-excerpt surface. The §5.0.2 audit found no Michiu company page exists in May 2026 — that's the single highest-leverage §5 add. Press cites and LinkedIn share Penn as helper-owner and share the essay corpus as content, but the audience and cadence are distinct.

Principles (LinkedIn-specific)

• Two-track structure: Michiu company page + Michelle personal page (the Quintonil dual-brand pattern, §3.2). Once Anna voice-distribution work (§3.3 Quintonil derivative) lands in §6, a third surface — Anna or named FOH lead's personal LinkedIn — opens up. Aim for three named-person handles around the venue.
• Posting cadence is once-weekly minimum, twice-weekly during cultural-moment / RAI event weeks. The 2026 NL "less, more weight" mood (§1.8) applies less here than to other channels — LinkedIn is where Corporate Bookers actually look; under-posting loses the lane.
• Essays + cast features + RAI event-week openings. No "we made delicious food today" content. Every post earns its place by carrying a specific moment (a dated event, a named guest who agreed, an essay paragraph, a chef's-table availability window for an upcoming RAI conference).
• Track every post + reply with m_campaign=linkedin_<post-slug> so the §6.6 attribution loop closes on whichever LinkedIn surface produced a Corporate Booker booking.

Principles (press-specific)

• NL press is the highest-leverage outbound channel in 2026 (per ⁶¹).
• Pitch on a moment, not on a general "tell our story" — every pitch carries a specific dated angle.
• One pitch at a time per outlet. Multiple simultaneous pitches read as marketing-bombing.
• Penn maintains the outreach log — every contact, every pitch, every cite tracked with m_campaign=press_<outlet-slug>.

Content pillars (five — split into LinkedIn-primary + press-primary):

LinkedIn-primary (Corporate Booker–facing, weekly cadence)

1. RAI event-week openings (CB tier, §0 shift #2) — short LinkedIn posts naming the conference, the event-week dinner window Michiu has open for 8–20 covers, and the contact path. Pre-published 3–4 weeks ahead of each RAI calendar moment; Penn-drafted, Michelle-approved when the dinner anchor includes her presence. Highest-leverage LinkedIn pattern.
2. Cast features as social proof (the Quintonil dual-brand demonstration) — monthly profile of one cast member: Michelle, Anna or named FOH lead, sommelier, pastry lead. These compound the §1.4 / §3.4 pattern-4 cast-distribution defense.
3. Long-form essay excerpts as LinkedIn long-posts — the §4.3 6-essay cadence cross-publishes here as 600–900-word LinkedIn-native posts (NOT as outbound links to michiu.nl — LinkedIn's algorithm punishes outbound). Penn's essay_excerpt_linkedin Power-Up handles the rewrite.

Press-primary (broader audience, monthly cadence)

4. Cultural-moment pitches (trends 2 + 5 + 8) — pre-empted 4–6 weeks ahead per outlet's editorial cycle. NL Tier 1 outlets per §4.4 table.
5. Industry-press operator angle (Misset Horeca, Entree, MarketingTribune) — the Marketing OS itself is a story; Michelle on visible-effort kitchen culture; the no-list as industry leadership.

Cadence

• LinkedIn:
  • Floor: 1 post/week on the Michiu company page; 2 posts/week on Michelle's personal page (essays + commentary).
  • Ceiling: 3/week on company page during RAI event weeks (Tactic 8.3); 4/week on Michelle's during cultural-moment weeks.
• Press:
  • Monthly: at least one active pitch in flight to an NL outlet.
  • Quarterly: review citation map; identify which outlets have NOT yet cited Michiu; pitch them next.

Power-Ups for Penn

• linkedin_post_rai_window (cross-references Sun's RAI-event-calendar to auto-draft event-week availability posts) — pass-4 added
• linkedin_cast_feature_monthly (the Quintonil-pattern named-handle rotation across the cast) — pass-4 added
• press_pitch_window_alert (alerts Penn N weeks ahead of each cultural moment)
• press_outreach_log (tracks every pitch + outcome)
• essay_excerpt_linkedin (auto-formats long-form essays as LinkedIn-ready excerpts — not outbound links)
• editorial_calendar_sync (Penn's calendar sync with the outlet editorial cycles)
• awards_nomination_calendar (the §4.4 Tier-4 awards pipeline calendar — Art of Hospitality, Michelin Sommelier, GaultMillau NL, Bib Gourmand, sustainability) — pass-4 added

Q1 P0 actions for Penn (in priority order):

1. Create the Michiu LinkedIn company page — currently missing per §5.0.2 audit. Logo + cover image (single-illustrator vocabulary once §3.3 pattern 8 commissioned; placeholder natural-light photo until then) + tagline (the philosophy-name once Michelle approves, §4.3 row 5) + about section (300 chars NL + 300 EN, named cuisine position + RAI proximity + named chef).
2. Confirm + claim Michelle's personal LinkedIn URL — possible michelle-zhang-07a9ba4 match in search but unverified. Get the URL from Michelle directly.
3. Update the businessrestaurants.nl listing copy — replace "China, Japan, Thailand, and many other diverse Asian countries" with the Michiu-coined position; add explicit "5 minutes van RAI / Amsterdam-Zuid" geographic hook (currently absent — see §5.0.2 audit).

5.6 Google Business Profile + multi-language (Carlos-owned)

Principles

• NL primary, EN strong-secondary, CN/JP minimal. Most queries we want to win are NL-language.
• The GBP description is the most-read paragraph Michiu has — every word earns its place.
• Photos are dated and dish-named in alt-text — feeds GEO grounding.
• Quarterly description refresh; never auto-update.

Three content pillars

1. Description + Q&A maintenance — the 750-char NL + 750-char EN canonical text. Q&A pre-answered with 6–8 entries.
2. Photo cadence — 2–3 new photos/week, named (michiu-amsterdam-zuid-cantonese-hokkaido-uni.jpg), alt-tagged in NL primary.
3. Posts + offers — weekly during cultural-moment weeks; bi-weekly otherwise. Carlos uses GBP Posts for moment-specific availability (Tactic 8.3 RAI-event-week LinkedIn version cross-posts here as GBP "Event" type).

Cadence

• Photos: 2–3/week
• Posts: 1–2/week
• Description: quarterly review
• Q&A: monthly audit (Carlos answers any new guest questions within 48h)

Power-Ups for Carlos

• gbp_photo_weekly_post (Zuck shares; Carlos cross-posts with structured alt-text)
• gbp_post_event_window (cross-references Sun's Campaign calendar to publish GBP event posts during moments)
• multi_lang_description_sync (NL/EN/CN/JP variants maintained)
• schema_markup_audit_quarterly (Schema.org structured data audit against michiu.nl)

5.7 Google Ads (Roy-owned)

Principles

• We use ads only where the closed-loop attribution closes — GCLID → Zenchef → POS €.
• No segment-tagged promo codes (Tactic 9.3 hard rule).
• Search > Display. Maps > Search > everything else.
• Geo-targeting tight: Amsterdam-Zuid 2km radius + RAI 1km radius during event weeks; nothing else.

Three campaign types

1. Always-on local search — "Cantonees restaurant Amsterdam Zuid", "restaurant near RAI", "best omakase Amsterdam". CPC-bid; targets CC + CB tiers primarily.
2. RAI event-week boosts — synchronized with the RAI calendar; geo-fenced to RAI 1km radius; English ad copy; CB tier exclusive. See Tactic 8.3.
3. Customer Match audience refresh — quarterly upload of opted-in customer hashes to Google for lookalike modeling. NEVER without opt-in.

Cadence

• Always-on: continuous
• RAI event-week boosts: triggered by Roy via rai.event.upcoming.t_minus_7d Inngest event
• Customer Match refresh: quarterly

Power-Ups for Roy

• gcld_capture_pipeline (site-side script — pairs with click_tracking table)
• rai_event_geo_boost (cron + Inngest event triggered)
• customer_match_quarterly_refresh (Roy's audience-rebuild Power-Up)
• negative_keyword_audit_monthly (filter out cheap-eats / kebab / takeaway / delivery queries that bleed budget)

5.8 GEO / AI discovery — cross-reference §4

Cadence + content roadmap + citation strategy + quarterly test queries: all in §4. Helper ownership:

• Carlos: Schema.org markup, GBP, Apple Maps, Bing Places, multi-lang structured data
• Penn: long-form essays (6 bi-monthly), NL press cites, Reddit cultivation
• Insight: quarterly 12-prompt test suite (NL + EN), citation surface tracking, weekly digest of where Michiu is being mentioned in LLM source attributions

5.9 Cadence summary by tier (the §1.8 application)

Reading this table: the Status Builder tier has the most channel surface but the lightest per-touch weight (Sutherland-style); the Corporate Booker tier has the narrowest surface but the highest per-touch weight (Kahneman-style decision design). Classic Connoisseurs are between, dominated by in-restaurant + press + GBP + the considered email — they almost never see an IG post and we should design for that, not against it.

6. Marketing OS integration (the machine layer)

[!note] How to read this section Each subsection below is structured so the engineering team can paste the contents directly into a Supabase migration, a seed file, or a Power-Up specification. Where existing migrations or files are referenced, the path is concrete (supabase/migrations/, src/marketing-os/, etc.). Pass-4 sync (May 2026): §6.0 below is the new "what already shipped vs. what is still spec" inventory — read it first; §6.1–§6.7 retain their original migration-paste shape but are now annotated with the actual migration numbers and shipped-status flags.

6.0 Implementation state (pass-4 sync, May 2026)

This section was written in pass-2 as forward-looking spec. Since then the marketing-os lane has shipped a large amount of it — but with different migration numbers, an expanded scope (Julius audit log, RLS account-predicate hardening, helper-proposal queue, Campaign object), and a new structural envelope (Campaign) that was not yet in the pass-2 §6 draft. The split below is the read-in-context aid.

Sourced from: .claude/lanes/handoffs/marketing-os.HANDOFF.md at the time of this pass + supabase/migrations/ directory inventory + src/marketing-os/helpers/*/power-ups/ registries.

✅ Shipped on main (May 2026)

🟡 Wired-but-dormant (foundation shipped, upstream / external dependency pending)

🔴 Spec-only (not yet built)

• §6.3 Sun micro-opps beyond cultural_moment_t_minus_6_weeks: rainy_tuesday_lunch, sakura_window_forecast, rai_event_t_minus_7, lapsed_circle_birthday_window, cancellation_cascade_alert, menu_rotation_confirmed — all defined in §6.3 but not yet implemented
• §6.4 Power-Ups: many of the 11 listed are still pending (see §6.4 table — pass-4 adds a Status column)
• §6.5 Campaign archetype seeds (5 named: lunch-dice-2026, midautumn-chachaanteng-pop-up, lny-long-table, rai-event-week-corporate, longform-essay-bimonthly) — none instantiated yet
• §4.3 6 long-form essays — content not drafted
• §4.6 P0 fixes 1–7 — all 7 are concrete pending actions (5 in §4.6, 2 added in §5.0 — title-tag, IG bio, Yelp category, GBP category, Cloudflare crawler-allowlist, LinkedIn company page, about-us body rewrite)

Pass-4-derived schema additions (proposed in §6.8 below)

Three new tables / columns surfaced by §3 + §4 + §5 work that did not exist in the pass-2 §6 draft:

• brand_audiences.philosophy_name column — surfaces the Sazenka-pattern (§3.3 #6) Michiu-coined philosophy once Michelle approves it. Recommended migration 0060_brand_audiences_philosophy_name.sql.
• brand_visual_identity table — captures the Yardbird-pattern (§3.3 #8) signature-artist + visual-vocabulary entries. Recommended migration 0061_brand_visual_identity.sql.
• awards_pipeline table — captures the Don Julio Tier-4 awards-nomination calendar from §4.4 + §5.5. Recommended migration 0062_awards_pipeline.sql.

Each is spec'd in §6.8 at the migration-paste level.

6.1 Julius rule additions — brand_banned_phrases migration

✅ Shipped as 0038_banned_phrases_2026_felt_not_told.sql (pass-2 named 0030 — actual was 0038; numbering shifted as the OS-02 + OS-03 Brand Memory bedrock landed first). 27 entries seeded; live-editable via /admin/marketing-os/memory/banned-phrases (OS-08b CRUD). The 22 block-level + 5 warn-level enforcement runs through checkBannedPhrases() (src/brand/review-prompt.ts v2.0 + src/brand/load-brand-memory.ts). The block below remains the canonical reference for what the file seeded — do not re-apply; future additions go through the admin UI or a new migration.

Append to existing brand_banned_phrases table (do not replace). Historical pass-2 spec migration name retained for traceability: supabase/migrations/0030_banned_phrases_2026.sql → actual landed as 0038_banned_phrases_2026_felt_not_told.sql.

// Format consumed by checkBannedPhrases() — append-only to the existing list.
const julius_2026_additions = [
  // Positioning felt-not-told (§1.2 hard rule #2)
  { phrase: "Amsterdam's New Home for Success", severity: "block", reason: "positioning felt-not-told — never outbound", added_for: "trend-2 + §1.2" },
  { phrase: "the new home for success", severity: "block", reason: "positioning reformulation", added_for: "§1.2" },
  { phrase: "where Amsterdam celebrates", severity: "block", reason: "positioning reformulation", added_for: "§1.2" },
  { phrase: "Amsterdam's destination for success", severity: "block", reason: "positioning reformulation", added_for: "§1.2" },
  { phrase: "Amsterdam's destination for winners", severity: "block", reason: "positioning reformulation", added_for: "§1.2" },
  { phrase: "Amsterdam's destination for achievement", severity: "block", reason: "positioning reformulation", added_for: "§1.2" },

  // Gamification felt-not-told (§1.2 hard rule #3 / §1.3 gesture-not-system)
  { phrase: "gamification", severity: "block", reason: "gamification felt-not-told — system framing", added_for: "trend-4 + §1.3" },
  { phrase: "gamified", severity: "block", reason: "gamification felt-not-told", added_for: "§1.3" },
  { phrase: "gamify", severity: "block", reason: "gamification felt-not-told", added_for: "§1.3" },
  { phrase: "rewards program", severity: "block", reason: "system framing", added_for: "§1.3" },
  { phrase: "loyalty rewards", severity: "block", reason: "system framing", added_for: "§1.3" },
  { phrase: "loyalty program", severity: "block", reason: "system framing", added_for: "§1.3" },
  { phrase: "earn points", severity: "block", reason: "system framing", added_for: "§1.3" },
  { phrase: "level up", severity: "block", reason: "system framing", added_for: "§1.3" },
  { phrase: "unlock rewards", severity: "block", reason: "system framing", added_for: "§1.3" },
  { phrase: "unlock a perk", severity: "block", reason: "system framing", added_for: "§1.3" },
  { phrase: "play and earn", severity: "block", reason: "system framing", added_for: "§1.3" },
  { phrase: "spin to win", severity: "block", reason: "system framing", added_for: "§1.3" },
  { phrase: "win prizes", severity: "block", reason: "system framing", added_for: "§1.3" },
  { phrase: "play our game", severity: "block", reason: "system framing", added_for: "§1.3" },
  { phrase: "members-only rewards", severity: "block", reason: "system framing + Circle felt-not-told", added_for: "§1.2 + §1.3" },
  { phrase: "redeem your reward", severity: "block", reason: "system framing", added_for: "§1.3" },

  // Warn-level on adjacent marketing-speak (gamification halo)
  { phrase: "exclusive perks", severity: "warn", reason: "adjacent marketing-speak; usually drift signal", added_for: "§1.3" },
  { phrase: "VIP perks", severity: "warn", reason: "adjacent marketing-speak", added_for: "§1.3" },
  { phrase: "member benefits", severity: "warn", reason: "adjacent marketing-speak", added_for: "§1.3" },
  { phrase: "points balance", severity: "warn", reason: "adjacent marketing-speak", added_for: "§1.3" },
  { phrase: "tier upgrade", severity: "warn", reason: "Circle tier disclosure risk", added_for: "§1.2" },

  // AI-slop tells (trend 1 — defensive)
  { phrase: "AI-powered", severity: "warn", reason: "trend 1 AI-slop tell when used about our content", added_for: "trend-1" },
  { phrase: "elevated dining experience", severity: "block", reason: "compound of two banned phrases; AI-slop classic", added_for: "trend-1" },
  { phrase: "thoughtfully curated", severity: "block", reason: "compound of curated + thoughtful; AI-slop tell", added_for: "trend-1" },
  { phrase: "carefully selected", severity: "warn", reason: "vague substitute for specificity rule (§1.1)", added_for: "trend-1 + §1.1" },
];

Total: 27 entries. 22 block-level, 5 warn-level. These do not replace the existing banned list — they extend it.

6.2 Per-helper voice distribution shifts — helper_voice_distributions deltas for 2026

✅ Shipped as 0039_voice_distributions_2026.sql. Live-editable via /admin/marketing-os/memory/helper-voice-distributions (OS-08b). Julius drift-monitor mode wired through julius_audit_log (0046) and surfaces in the helper home pages (e.g. /admin/marketing-os/helpers/siren shows target vs. actual distribution over a 90-day window). The Echo → Siren rename (0051) updated this table's rows in-place.

Format: percentage shifts vs. v1 baselines (in helper_voice_distributions). Positive = more weight in 2026; negative = less. Applied via a migration that updates the existing rows.

const voice_deltas_2026 = [
  // Siren: nudge toward Sutherland for nostalgia + Kahneman for trend-9 transparency
  { helper: "siren", voice: "sutherland", delta: +5, reason: "trend 5 nostalgia + trend 7 oblique tone" },
  { helper: "siren", voice: "kahneman", delta: +3, reason: "trend 9 algorithmic-literacy / honest disagreement" },
  { helper: "siren", voice: "guidara", delta: -8, reason: "less generic warmth; more specificity per §1.1" },

  // Anna: nudge toward Kahneman for trend 9 transparency; less GaryVee enthusiasm
  { helper: "anna", voice: "kahneman", delta: +5, reason: "trend 9 + frictionless concierge decision design" },
  { helper: "anna", voice: "garyvee", delta: -5, reason: "Dutch register prefers calm over kinetic for inbound DM" },

  // Penn: heavier Godin for long-form essay year
  { helper: "penn", voice: "godin", delta: +10, reason: "6 long-form essays (§4.3) — story-shaping is the spine" },
  { helper: "penn", voice: "kahneman", delta: +5, reason: "no-list (Tactic 7.1) + reply-meta (7.2) require loss-aversion framing" },
  { helper: "penn", voice: "guidara", delta: -10, reason: "press writing needs less warmth, more clarity" },
  { helper: "penn", voice: "sutherland", delta: -5, reason: "press writing needs less oblique, more direct" },

  // Zuck: lean into Sutherland for trend-7 off-rhythm naming + GaryVee for TikTok rise
  { helper: "zuck", voice: "sutherland", delta: +7, reason: "trend 7 strategic-rule-breaking + naming guideline (Tactic 7.3)" },
  { helper: "zuck", voice: "garyvee", delta: +3, reason: "TikTok NL 25-44 cohort rise (§5.2)" },
  { helper: "zuck", voice: "guidara", delta: -5, reason: "less warmth, more specificity" },
  { helper: "zuck", voice: "godin", delta: -5, reason: "less story-arc on social; more single-moment captures" },

  // Clara: minimal shift — lifecycle outbound stays Guidara-heavy because warmth is the entire value
  { helper: "clara", voice: "guidara", delta: 0, reason: "preserve warmth — birthday and re-engagement need it" },
  { helper: "clara", voice: "kahneman", delta: +3, reason: "decision-design language for opt-out clarity" },
  { helper: "clara", voice: "garyvee", delta: -3, reason: "less kinetic; more considered" },

  // Insight: shifted entirely Kahneman — measurement work IS decision design
  { helper: "insight", voice: "kahneman", delta: +10, reason: "trend 9 + measurement transparency (§10)" },
  { helper: "insight", voice: "godin", delta: -5, reason: "less story-shaping; more decision-relevant signal" },
  { helper: "insight", voice: "garyvee", delta: -5, reason: "internal-facing — calm, not kinetic" },

  // Julius: pure-Kahneman drift (guardrail = decision design)
  { helper: "julius", voice: "kahneman", delta: +10, reason: "expanded banned-phrase list = stronger decision-design role" },
  { helper: "julius", voice: "guidara", delta: -10, reason: "guardrails are not warmth" },

  // Sun: light shift toward Godin for strategic-narrative work
  { helper: "sun", voice: "godin", delta: +5, reason: "campaign briefs are story-arcs" },
  { helper: "sun", voice: "kahneman", delta: +5, reason: "campaign trade-off decisions need loss-aversion framing" },
  { helper: "sun", voice: "sutherland", delta: -5, reason: "less oblique at strategy level; more direct trade-off statement" },
  { helper: "sun", voice: "guidara", delta: -5, reason: "less warmth at strategy level" },

  // Carlos: very stable — local-SEO work is structured
  { helper: "carlos", voice: "kahneman", delta: +3, reason: "structured-data work is decision-design-adjacent" },
  // (Other Carlos voices unchanged.)

  // Roy: leans further Kahneman — ads attribution is loss-aversion framed
  { helper: "roy", voice: "kahneman", delta: +5, reason: "GCLID + Customer Match = decision-design tools" },
  { helper: "roy", voice: "godin", delta: -3, reason: "less story-arc; more direct copy" },
];

Reconciliation note: Julius must enforce these in drift-monitor mode — flagging when a helper's actual output voice distribution diverges from the target by >10 percentage points over a 30-day rolling window. Insight surfaces in the quarterly digest.

6.3 Sun micro-opportunity Power-Ups — Inngest event-driven triggers

✅ First live Sun loop: cultural_moment_t_minus_6_weeks is the first Power-Up in this section to actually emit drafts into the Universal Approval Queue end-to-end. Wired via: (a) cultural_moments table 0042 + admin CRUD editor (OS-18f/g); (b) Inngest topic sun.cultural_moment.opened + function processCulturalMomentOpened (OS-18b); (c) helper_proposals table 0052 + idempotent upsert via dedupe_key = ${moment_id}:${moment_year} (OS-18c); (d) cron route /api/cron/sun-cultural-moments at 0 7 * * * UTC; (e) proposal-expiry cron at 0 2 * * * UTC (OS-18d). The promote-to-Campaign downstream verb is live too: a cultural_moment_brief proposal can promote to a Campaign row (0053, in code; not yet applied live) that pre-fills slug + dates + tracking-code from the moment payload. The remaining 6 micro-opps below are still spec.

Each Power-Up is a typed Inngest event subscription + composite query + draft template. Sun runs the detection; the output routes to the Universal Approval Queue.

const sun_micro_opportunities = [
  {
    name: "rainy_tuesday_lunch",
    event_topic: "weather.amsterdam.daily_forecast",
    condition_query: `
      SELECT 1 FROM forecast f, reservations r
      WHERE f.zone = 'amsterdam_zuid'
        AND f.rain_mm >= 4
        AND f.window = 'lunch'
        AND f.date BETWEEN now() AND now() + interval '24 hours'
        AND (SELECT COUNT(*) FROM tables WHERE available_at(f.date) AND daypart='lunch') >= 6
    `,
    action_template: "Sun drafts WhatsApp via Clara to opted-in customers within 3km billing-address geofence; no-discount; offer warmth + specific dish",
    target_tier: "SB + CC",
    attribution_slug: "m_campaign=rainytuesday_<YYYY-MM-DD>",
    tactic_ref: "4.4",
  },
  {
    name: "sakura_window_forecast",
    event_topic: "seasonal.sakura.vondelpark_forecast", // cron-style + external API
    condition_query: "vondelpark_bloom_forecast.peak_date BETWEEN now() AND now() + interval '14 days'",
    action_template: "Sun creates Campaign archetype `sakura-namelaka` for Zuck + pastry team; pre-books pastry supplier",
    target_tier: "SB",
    attribution_slug: "m_campaign=sakura_namelaka_<year>",
    tactic_ref: "2.3",
  },
  {
    name: "rai_event_t_minus_7",
    event_topic: "rai.event.upcoming",
    condition_query: "rai_calendar.event_date - now() = interval '7 days' AND rai_calendar.event_tier IN ('major', 'international')",
    action_template: "Sun briefs Penn for LinkedIn post template; Roy for geo-boost; Zuck for GBP event post",
    target_tier: "CB",
    attribution_slug: "m_campaign=rai_<event-slug>_<year>",
    tactic_ref: "8.3",
  },
  {
    name: "lapsed_circle_birthday_window",
    event_topic: "clara.birthday.window_open",
    condition_query: `
      SELECT customer_id FROM customers c
      WHERE c.marketing_opt_in = true
        AND c.birthday_md BETWEEN to_char(now(), 'MM-DD') AND to_char(now() + interval '14 days', 'MM-DD')
        AND c.last_visit_date < now() - interval '180 days'
    `,
    action_template: "Sun + Clara draft handwritten card; surface to UAQ for Michelle approval",
    target_tier: "CC",
    attribution_slug: "brand-only (no UTM; gesture is the channel)",
    tactic_ref: "4.3",
  },
  {
    name: "cancellation_cascade_alert",
    event_topic: "reservation.cancelled",
    condition_query: `
      -- detect 3+ cancellations for the same service in 24h, triggering a fill push
      SELECT service_id, COUNT(*) c
      FROM reservation_cancellations
      WHERE cancelled_at > now() - interval '24 hours'
      GROUP BY service_id
      HAVING COUNT(*) >= 3
    `,
    action_template: "Sun + Clara draft same-day WhatsApp to opted-in geofenced customers; no discount; offer warmth",
    target_tier: "SB + CC",
    attribution_slug: "m_campaign=fill_<service-id>_<YYYY-MM-DD>",
    tactic_ref: "(extension of 4.4)",
  },
  {
    name: "menu_rotation_confirmed",
    event_topic: "menu.rotation.confirmed",
    condition_query: "menu_rotations.published_at IS NOT NULL AND menu_rotations.notified_at IS NULL",
    action_template: "Sun briefs Zuck for test-menu-carousel posts (Tactic 3.2) + Penn for cultural-moment essay timing",
    target_tier: "SB + CC",
    attribution_slug: "m_campaign=menurotation_<slug>",
    tactic_ref: "3.2 + 5.1",
  },
  {
    name: "cultural_moment_t_minus_6_weeks",
    event_topic: "cultural_calendar.moment.upcoming",
    condition_query: "cultural_moments.date - now() = interval '6 weeks' AND cultural_moments.tier = 'primary'",
    action_template: "Sun briefs Penn for press pitch + Zuck for in-restaurant pop-up promotion timeline",
    target_tier: "SB + CC",
    attribution_slug: "m_campaign=moment_<slug>_<year>",
    tactic_ref: "2.1, 2.2, 2.3, 5.2",
  },
];

Total: 7 Power-Ups for Sun in 2026. Implementation order (Q1 priority): rainy_tuesday_lunch (P0 — see Trend 4 NL-specific note) → rai_event_t_minus_7 → cultural_moment_t_minus_6_weeks. The rest land Q2.

6.4 New Power-Ups for the library (14 — owner-tagged; pass-4 added 3 LinkedIn Power-Ups)

Status column added pass-4. None of the 11 strategy-derived Power-Ups in this table have been individually wired yet — what HAS shipped (May 2026) is the underlying helper foundations + a separate analytics-Power-Up tier per helper (Siren 4/7, Anna 4/6, Zuck 2/10, Sun 3+1 cron/8, Roy 1 rollup). The §6.4 entries below are strategy-tactic-derived Power-Ups that bind to specific §2 tactics; the analytics Power-Ups are diagnostic / operational. Both tiers will co-exist in src/marketing-os/helpers/<helper>/power-ups/.

Plus the Sun micro-opportunities (§6.3) and Carlos/Penn/Insight/Roy specific Power-Ups in §5.

6.5 Campaign-object archetype templates (5 named — 2026 launch)

🟡 Campaign object shipped in code at 0053_campaigns.sql (May 2026); migration NOT YET APPLIED to live Supabase — pending operator authorization for supabase db push. Admin surface at /admin/marketing-os/campaigns/ is built (list / new / detail / lifecycle transitions); the promote-from-proposal flow links Sun's cultural_moment_brief proposals to Campaign creation with pre-filled slug + dates + tracking-code. The 5 archetype templates below are not yet seeded — a seed migration must follow once 0053 is applied. The campaign.start_date_reached + campaign.end_date_reached Inngest topics were registered in OS-12 but now have a real table backing.

Once 0053 is applied + archetypes seeded, the §6.5 list becomes the authoritative starter set. Per CLAUDE.md hard rule #6 reaffirmed inline: posts within a campaign still flow through the Universal Approval Queue; the Campaign is an organizational envelope, not an autonomy unlock.

const campaigns_2026 = [
  {
    archetype: "lunch-dice-2026",
    primary_helper: "sun",
    secondary_helpers: ["zuck", "carlos", "insight"],
    target_tier: "SB",
    channels: ["in-restaurant", "ig", "gbp"],
    attribution_slug: "lunch_dice_2026",
    cadence: "ongoing (launch Q1)",
    success_metric: "lunch-daypart Tue-Fri 4-week trailing covers vs. 2025 baseline + organic IG mentions of the dice",
    tactic_ref: "4.1",
  },
  {
    archetype: "midautumn-chachaanteng-pop-up",
    primary_helper: "sun",
    secondary_helpers: ["zuck", "penn"],
    target_tier: "SB + CC",
    channels: ["in-restaurant", "ig", "press"],
    attribution_slug: "midautumn_chachaanteng_2026",
    cadence: "annual (late September)",
    success_metric: "ticket sell-through + press cites + new-customer ratio in reservation cohort",
    tactic_ref: "2.1",
  },
  {
    archetype: "lny-long-table",
    primary_helper: "sun",
    secondary_helpers: ["clara", "zuck", "penn"],
    target_tier: "CC + SB",
    channels: ["in-restaurant", "email", "whatsapp", "ig", "press"],
    attribution_slug: "lny_longtable_2026",
    cadence: "annual",
    success_metric: "Circle-priority send conversion rate + ticket sell-through + press cites",
    tactic_ref: "2.2",
  },
  {
    archetype: "rai-event-week-corporate",
    primary_helper: "penn",
    secondary_helpers: ["sun", "roy", "zuck"],
    target_tier: "CB",
    channels: ["linkedin", "google-ads", "gbp", "direct-email"],
    attribution_slug: "rai_<event-slug>_2026",
    cadence: "triggered per RAI major event (10-20/year)",
    success_metric: "group bookings attributed + event-agent relationships warmed",
    tactic_ref: "8.3",
  },
  {
    archetype: "longform-essay-bimonthly",
    primary_helper: "penn",
    secondary_helpers: ["zuck", "carlos"],
    target_tier: "CC + CB",
    channels: ["website", "linkedin", "press"],
    attribution_slug: "longform_<piece-slug>_2026",
    cadence: "bi-monthly (6 essays/year)",
    success_metric: "time-on-page on michiu.nl + LLM citation surface count (Insight) + press-pickup count",
    tactic_ref: "10.1 + §4.3",
  },
];

6.6 Closed-loop measurement plan per tactic class

✅ click_tracking table live at 0043_click_tracking.sql. Roy's click-tracking-summary Power-Up surfaces the 30-day funnel: total clicks, per-click_type mix, match rate via reservation_id IS NOT NULL, upload-status counts, top 5 m_campaign slugs by clicks. Conversion-upload to Google Ads is dormant pending the Google Ads developer-token approval (external). The Zenchef click-id pass-through resolution (§11.1 hypothesis #1) remains the gating decision for whether the primary attribution path or the SHA-256 hashed-email/phone fallback path is used; both are schema-ready.

6.7 Brand Memory ingestion map

Goal: when a human edits this document, the Git-backed vault-sync cron picks up the diff and updates the right Brand Memory typed row or memory_documents chunk. ✅ Vault-sync pipeline live as of OS-06a/b/c (cron at /api/cron/vault-drift-check daily 09:00 UTC; admin UI at /admin/memory/vault-sync; webhook at /api/webhooks/vault-sync with HMAC-SHA256 verification).

Migration ordering — pass-4 reality (May 2026):

What actually landed (left column) vs. what the pass-2 §6.7 originally proposed (right column):

6.8 Pass-4 schema additions

Three new tables / columns surfaced by §3 + §4 + §5 pass-4 work. Each is spec'd at the migration-paste level. Apply order: 0060 → 0061 → 0062 (no dependencies between them — order is for migration-number sequencing only).

[!note] Migration number offset Original pass-4 spec proposed 0054 / 0055 / 0056 but the parallel marketing-os session claimed 0054_short_links.sql for the Zuck dynamic UTM Power-Up during this session. Numbers shifted to 0060 / 0061 / 0062 to leave buffer for any in-flight parallel-session migrations between 0054 and 0059. Whoever ships these next should re-check the migration directory before applying and adjust if needed.

6.8.1 brand_audiences.philosophy_name column

Surfaces the Sazenka-pattern (§3.3 #6) Michiu-coined philosophy once Michelle approves it. The single phrase becomes the LLM-grounding answer (§5.0.1 rule 1), the press-cite tag, and the first line of the §4.3 Sep-2026 position essay. Stored on brand_audiences (per-tier) because the Status-Builders-facing framing of the philosophy may differ in register from the Classic-Connoisseurs-facing or Corporate-Bookers-facing variant — same root meaning, calibrated voicing per tier.

-- supabase/migrations/0060_brand_audiences_philosophy_name.sql
ALTER TABLE public.brand_audiences
  ADD COLUMN philosophy_name TEXT,
  ADD COLUMN philosophy_name_rationale TEXT;

COMMENT ON COLUMN public.brand_audiences.philosophy_name IS
  'The Michiu-coined named philosophy (e.g. Sazenka "wakon-kansai" pattern, §3.3 #6). Per-tier so the framing register can be calibrated. Single phrase, 2-4 words. Once approved by Michelle, deploys identically to <title>, GBP description, IG bio, TikTok bio, LinkedIn tagline, press one-liner, essay openings (§5.0.1 rule 1).';

COMMENT ON COLUMN public.brand_audiences.philosophy_name_rationale IS
  'The structural reasoning behind the philosophy_name choice. References §3.3 pattern 6 (Sazenka) + §4.3 row 5 + §5.0.1 rule 1. Surfaced to Penn when pitching press so the tagline is defensible.';

Apply only after Michelle has approved the philosophy-name (§4.6 fix #1 + #7 gate). Until then, the column is NULL across all 3 audience rows and every downstream surface keeps using interim placeholder copy.

Helper impact: Penn / Sun / Zuck / Carlos all read brand_audiences.philosophy_name via loadBrandMemory() snapshot. Julius enforces consistency — flags any outbound copy that proposes a competing philosophy framing.

6.8.2 brand_visual_identity table

Captures the Yardbird-pattern (§3.3 #8) single-illustrator visual vocabulary across IG / TikTok / GBP / takeaway-artifact / menu cards / LinkedIn cover. The point is structural defense against the AI-slop visual default (§3.4 pattern 1): algorithms cannot homogenize a hand that is identifiable.

-- supabase/migrations/0061_brand_visual_identity.sql
CREATE TABLE public.brand_visual_identity (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  account_id TEXT NOT NULL DEFAULT 'michiu' REFERENCES public.accounts(id),

  signature_artist_name TEXT,
  signature_artist_contact TEXT,
  signature_artist_retainer_summary TEXT,

  vocabulary_summary TEXT NOT NULL,
  -- Free-text summary of the visual language: line weight, color palette, recurring motifs, dominant medium

  surface_coverage JSONB NOT NULL DEFAULT '{}'::jsonb,
  -- Tracks which surfaces have been migrated to the signature vocabulary:
  -- { "ig_carousel": true, "tiktok_endcard": false, "gbp_photo_overlay": false,
  --   "takeaway_box": false, "menu_card": false, "linkedin_cover": false }

  reference_image_urls TEXT[] DEFAULT ARRAY[]::TEXT[],
  -- Stored references to the canonical artist samples — used by Zuck Power-Ups for style-match prompting

  status TEXT NOT NULL DEFAULT 'planning'
    CHECK (status IN ('planning', 'commissioned', 'active', 'rotating', 'archived')),

  created_at TIMESTAMPTZ NOT NULL DEFAULT now(),
  updated_at TIMESTAMPTZ NOT NULL DEFAULT now()
);

ALTER TABLE public.brand_visual_identity ENABLE ROW LEVEL SECURITY;

CREATE POLICY brand_visual_identity_account_predicate ON public.brand_visual_identity
  FOR ALL TO authenticated
  USING (account_id = public.current_account_id())
  WITH CHECK (account_id = public.current_account_id());

CREATE INDEX brand_visual_identity_account_status_idx
  ON public.brand_visual_identity (account_id, status);

-- One row per active vocabulary (typically exactly 1 active row per account at a time).
-- Future rotations create a new row with status='rotating' alongside the existing 'active' row.

Helper impact: Zuck reads surface_coverage to know which content streams already use the signature vocabulary and which still default to natural-light/hands-in-frame placeholder. The Power-Ups craft-clip-weekly, supplier-carousel-rotation, chefs-table-capture-protocol, pastry-failures-quarterly, linkedin_cast_feature_monthly (pass-4) all become surface-coverage-aware once a row is active.

6.8.3 awards_pipeline table

Captures the Don Julio Tier-4 pattern (§3.3 #9 + §4.4 + §5.5): hospitality-discipline → person-level + venue-level awards → press cycles → food-ranking attention. Awards are independently citeable by LLMs at much lower cost than chasing Michelin or 50 Best directly.

-- supabase/migrations/0062_awards_pipeline.sql
CREATE TABLE public.awards_pipeline (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  account_id TEXT NOT NULL DEFAULT 'michiu' REFERENCES public.accounts(id),

  award_track_slug TEXT NOT NULL,
  -- e.g. 'art_of_hospitality', 'michelin_sommelier_nl', 'gault_millau_nl',
  -- 'bib_gourmand_nl', 'asia_50_best_sustainable', 'michelin_green_star'

  award_track_display_name TEXT NOT NULL,
  awarding_body TEXT NOT NULL,
  -- Worlds 50 Best / Michelin Guide NL / GaultMillau Nederland / etc.

  submission_year INTEGER NOT NULL,
  -- The cycle year being targeted

  submission_window_opens_at DATE,
  submission_window_closes_at DATE,
  ceremony_date DATE,

  primary_helper_slug TEXT,
  -- Typically 'penn' for submission ownership

  eligibility_owner TEXT,
  -- 'anna' for hospitality awards; 'sun' for sustainability; 'penn' for press
  eligibility_evidence JSONB DEFAULT '{}'::jsonb,
  -- { "sop_refs": ["foh.circle_birthday", "foh.window_seating"], "essay_refs": ["sourcing-2026"], "press_cite_ids": [...] }

  status TEXT NOT NULL DEFAULT 'tracked'
    CHECK (status IN ('tracked', 'preparing', 'submitted', 'shortlisted', 'won', 'declined', 'lost')),

  decided_by_email TEXT,
  decided_at TIMESTAMPTZ,
  -- Michelle's per-submission approval (per §5.5 rule: "Michelle approves each submission individually")

  m_campaign_slug TEXT,
  -- Per §4.4 Tier-4 table — 'press_aoh' / 'press_michelin_sommelier' / 'press_gaultmillau' etc.

  notes TEXT,

  created_at TIMESTAMPTZ NOT NULL DEFAULT now(),
  updated_at TIMESTAMPTZ NOT NULL DEFAULT now()
);

ALTER TABLE public.awards_pipeline ENABLE ROW LEVEL SECURITY;

CREATE POLICY awards_pipeline_account_predicate ON public.awards_pipeline
  FOR ALL TO authenticated
  USING (account_id = public.current_account_id())
  WITH CHECK (account_id = public.current_account_id());

CREATE INDEX awards_pipeline_year_status_idx
  ON public.awards_pipeline (account_id, submission_year, status);

CREATE INDEX awards_pipeline_track_year_idx
  ON public.awards_pipeline (account_id, award_track_slug, submission_year);

-- The §5.5 Q1 P0 Power-Up `awards_nomination_calendar` queries this table for
-- imminent submission windows (where submission_window_opens_at - now() <= lead_days).
-- The §3.3 pattern 9 (Don Julio) rule "do not submit before the operational story
-- is mature" is enforced at the application layer — Penn flags a submission
-- as ready only when the eligibility_evidence array has the required SOP/essay
-- count for that award track.

Helper impact: Penn owns the submission calendar; Anna owns the eligibility surface for hospitality-tier awards; Sun owns sustainability awards; Michelle approves each submission individually. The awards_nomination_calendar Power-Up (§6.4 pass-4 added) reads from this table.

Sequencing note for engineering: the three pass-4 migrations (0054 / 0055 / 0056) are independent of the Campaign object live-apply gate (0053). They can be authored and applied separately. 0054 alone is gated on Michelle's philosophy-name approval; 0055 and 0056 can be applied with NULL-able rows that fill in as the operational stories mature.

7. EGC framework

EGC = Employee-Generated Content (the term Brandwatch uses⁹). Distinct from UGC (guest-generated) which is its own surface (already lightly managed via Tactic 8.1's chef's-table-with-permission capture). This section is internal-cast only.

7.0 Pass-4 alignment — where §5 cross-channel rules land in cast content

§7 is the surface where §5.0.1's four cross-channel deployment rules get most directly enforced — the cast is the human production source for IG / TikTok / LinkedIn / press content, and Julius's pre-queue gate (0046_julius_audit_log.sql) is the enforcement layer. The four rules, re-stated as cast-facing guardrails:

1. The Michiu-coined philosophy-name (Sazenka pattern, §3.3 #6) appears at first mention in every cast-authored long-form piece — once Michelle approves it. Operationally: Julius blocks any long-form draft that introduces the cuisine position without using the canonical phrase (warn-level, not block-level, in Q1 while the phrase is bedding in).
2. The signature-illustrator visual vocabulary (Yardbird pattern, §3.3 #8) applies to every cast-contributed visual asset — once the artist is commissioned and brand_visual_identity.status='active' (per §6.8.2). Until then: natural-light / hands-in-frame / mid-process placeholder per §5.1 + §5.2 principles.
3. Quintonil dual-brand presence (§3.3 / §5.0.1 rule 3) — the named FOH lead is a co-author alongside Michelle. This is the most consequential §7 change: the FOH-lead row in §7.1 below has been elevated to two anchor months (was one) and the per-quarter time allocation raised. Quintonil's Alejandra Flores has her own IG handle (@ale_quintonil) alongside Jorge Vallejo's (@jorgevallejo) and the venue's (@rest_quintonil) — three named handles at #3-World-50-Best tier. Michiu's structural parallel: Michelle (chef) + named FOH lead (hospitality) + the venue handle. Anna helper carries the FOH-voice in the OS; the human is the actual brand-co-architect.
4. Lung King Heen distribution rule (§3.4 pattern 4) — no week's cadence is 100% Michelle-fronted. §7.2 cadence already distributes across cast, but the rule needs to be explicit: if a Michelle anchor month coincides with a press cycle she's also leading, the parallel cast-anchor cadence must continue at floor.

7.0.1 Cast roster — pass-4 verification needed

The §7.1 table below lists 9 cast positions by role, not by name. Pass-4 audit (May 2026) could not verify which of these positions are currently staffed at Michiu and which are aspirational. Owner-confirmation needed before this section ships to operational SOPs. The Michelle Zhang row is verified (per project_michiu_principals.md memory); every other row needs Michelle to either confirm the named individual occupying the role or down-scope the section if a role is currently vacant. The Anna helper voice (OS layer) can stand in for the FOH-lead human voice until the human is named and onboarded, but the OS voice without a named human-counterpart misses the Quintonil pattern's structural point.

7.1 Who contributes what

Total target paid EGC time per year: ~96–108 hours across cast (raised in pass-4 by the +2 hrs FOH-lead Quintonil elevation), distributed as Tactic 6.4 specifies. This is the labor-budget line — if cut, trend 6 collapses (per §6.4 footnote).

7.2 Cadence

• Monthly anchor (one cast member is the centerpiece per Tactic 6.1) — 12/year, distributed across the §7.1 anchor calendar. FOH-lead gets two anchor months in pass-4 (Quintonil dual-brand pattern, §5.0.1 rule 3). 13/year effectively.
• Bi-weekly: sommelier's notebook (24/year — Tactic 6.2)
• Weekly: Zuck-coached IG craft clips (52/year — Tactic 1.1 + cast-cameo rotation)
• Weekly (LinkedIn — pass-4 added per §5.5 expansion): at least one cast-feature LinkedIn post per week (52/year); rotates across the cast per the linkedin_cast_feature_monthly Power-Up registry (§6.4 pass-4 row). Michelle's personal LinkedIn cadence (2/week per §5.5) is in addition to this rotation
• Quarterly: pastry failure log (4/year — 6.3); kitchen-porter / dishwasher / prep-cook profile (4/year — 3.3); review-reply meta post (4/year — 7.2)
• Annual: Michelle wrong-first-version essay (1/year — 3.4); no-list essay (1/year — 7.1)

7.3 Editorial guardrails

Every cast-authored output passes through Julius before the Universal Approval Queue. Julius's pre-queue gate runs against julius_audit_log (0046_julius_audit_log.sql — shipped May 2026) and renders as JuliusBadge on every review / DM / post detail page, so the operator sees Julius's read on every draft before clicking Approve. Per D11/D16: Julius is advisory only — never blocks; operator decides.

Julius enforces:

• Banned vocabulary (brand_banned_phrases — original list + §6.1 additions; live-editable via /admin/marketing-os/memory/banned-phrases)
• First-person plural rule (we / our kitchen — never third-person)
• Three felt-never-told rules (§1.2): Circle, positioning, gamification
• Specificity rule (§1.1): named dish / supplier / year / person — abstract claims blocked
• Philosophy-name discipline (pass-4 added, §5.0.1 rule 1) — once Michelle approves the Michiu-coined philosophy-name (§4.3 row 5 + §6.8.1 brand_audiences.philosophy_name), Julius warns on any long-form draft that introduces the cuisine position without using the canonical phrase. Q1 starts as warn-level (Julius is bedding in the new vocabulary across cast); promotes to block-level Q2 once distribution stabilizes.
• Visual identity discipline (pass-4 added, §5.0.1 rule 2) — Zuck's cast-coaching workflow includes a one-line reminder per submission about the active visual vocabulary state (per brand_visual_identity.surface_coverage — see §6.8.2). Pre-active state defaults to natural-light / hands-in-frame / mid-process placeholder.
• Voice distribution (§6.2 per-helper deltas): each cast member's contributions are funneled through the helper whose voice distribution best matches the cast role (sommelier → Penn/Zuck; pastry → Zuck; Michelle long-form → Penn; Michelle short-form → Zuck; FOH → Anna/Zuck — Anna voice distribution elevated in pass-4 per Quintonil dual-brand)
• Multi-language compliance: NL primary in any guest-facing surface; EN secondary version produced for LinkedIn / international press / RAI-event week. CN/JP only for GBP / Schema descriptions, not for cast-authored content (the cast doesn't author in those languages).

7.4 Light-touch training notes

At onboarding (any new cast member who will contribute to outbound):

• 30-min walkthrough of the three felt-never-told rules (with a printed one-pager).
• 30-min walkthrough of the specificity rule with worked examples from review-prompt.ts (Hokkaido uni not premium uni; 45-day dry-aged Wagyu not carefully aged beef).
• 15-min walkthrough of the approval-queue workflow: you draft, you submit, a human approves, then it ships. Nothing autoposts. This is not bureaucratic — it's the brand.
• 15-min walkthrough of the §5.0.2 TikTok worked example (pass-4 added): show the cast the actual @michiu_nl TikTok post the pass-4 audit found in May 2026 — "Did you ever try Toro?🤤🤤🤤🤤 Try the highest quality Sashimi at Michiu Amsterdam #toro #sashimi #amsterdam #sushilover #michiuamsterdam #japanesefood" — and walk through what makes it the AI-slop genre: (a) multi-emoji decoration, (b) adjective-stack ("highest quality"), (c) hashtag-pile (6+ hashtags), (d) generic question framing. Then show the rewritten version using the §5.2 principles: a single named-ingredient noun + a date + one functional emoji max + ≤3 hashtags. This is the most direct concrete teaching moment available from real Michiu content.

Ongoing:

• Insight's quarterly internal "what changed" digest (Tactic 9.1) serves as ongoing-training surface — it's where the cast learns what worked and what drifted.
• When Julius blocks a phrase, the queue shows the cast member which rule fired AND links to a one-sentence explanation. Blocks are teaching moments, not gatekeeping. The julius_audit_log (0046) keeps the long-tail; /admin/marketing-os/memory/julius (when built) surfaces it for the cast's own reference.
• Worked-example library lives in Brand Memory — the cast can search "show me approved sommelier replies from this quarter" and use them as voice anchors.
• Pass-4 addition: when brand_visual_identity.status transitions to active (§6.8.2), Zuck holds a 30-min cast review of the signature vocabulary with sample cards. Until that transition, the visual placeholder rules from §5.1 + §5.2 stand.

8. Decision rules

Each rule is a small tree the team can apply in 30 seconds without escalating. Designed to make most calls without owner involvement; the escalation criteria in §8.4 name the rest.

8.1 When to participate in a cultural moment vs. skip

Four-question gate. Apply in order. Any "no" = skip.

1. Authority test. Do we have authentic authority to comment on this moment? (Cantonese / Japanese cultural calendars: yes. Amsterdam-Chinatown / Zeedijk history: yes. King's Day, Valentine's Day, Pride: no — at most acknowledge silently in service. International commercial holidays we don't sit inside: no.)
2. Tier test. Does it serve at least one of our three audience tiers directly? (Mid-Autumn → SB + CC, yes. King's Day with a fusion angle → SB nominally but reads as trendjacking, no.)
3. Time test. Can we execute well in the available window (typically ≤6 weeks for press; ≤2 weeks for in-restaurant)? (Yes for moments we've pre-planned in §9. No for last-minute trend chases.)
4. Julius test. Can Julius approve the framing without warn-level flags on the draft copy? (If the only way to write the moment is using marketing-system language, the moment isn't ours.) ✅ Julius is wired into review approvals as of pass-4 (0046_julius_audit_log.sql + JuliusBadge rendering on every review/DM/post detail page); operator sees Julius's read pre-approval. Advisory only per D11/D16.

All four yes → participate. Any no → skip (and document in Sun's brief why, so the same moment isn't re-litigated next year).

8.2 When to invest offline vs. online

Default: offline-first. The room IS the channel (§5.3). Offline tactics compound through guest stories that re-enter online organically.

• In-restaurant moment first when the tactic involves a gesture, an artifact, or a sensory experience. (The lunch dice, the Circle gestures, the cultural-calendar pop-ups, the phone-free supper club, the chef's-table dinners — all offline-first.)
• Online-first when the audience cannot physically be in the room: Corporate Bookers planning ahead via LinkedIn (8.2/8.3); long-form essays building the GEO moat (§4.3); cast roster monthly anchors that reach the SB tier where they are.
• Never invent an online-only version of something that should be physical. The most common failure mode: turning the Circle into an email-and-points system, turning the dice into a digital "spin to win" game. Both would break the felt-not-told rules and collapse the mechanic.

8.3 When to break a rule vs. follow one

A rule break is justified only when both are true:

1. The break is in service of a Status Builder signal moment (trend 7 — the off-rhythm naming, the disagreement-reply, the no-list — all break the restaurant-marketing-default for a reason).
2. Julius (or Sun, or Michelle for the owner-judgment cases) can articulate the principle behind the break in one sentence.

If the break is "for attention" or "because everyone else is" — skip. Per §1.5, brand safety > efficiency, and per §1.4 the cast IS the brand — a rule-break that isn't grounded in a stated principle drifts the brand voice the cast inherits.

8.4 When to escalate to owner approval vs. let the helper draft go through the standard queue

Most outputs route to the Universal Approval Queue (UAQ — 4 surfaces as of pass-4: review-reply / dm-reply / post / proposal, via helper_proposals table 0052) and are approved by the next available human reviewer (Michelle, FOH lead, or Sun). Escalate to Michelle-specifically when:

• The output touches Michelle's public persona surface (her LinkedIn posts, her quoted long-form, any press attribution to her by name).
• A new Campaign archetype is being created (the 5 in §6.5 are seeded once 0053_campaigns.sql is applied live; new ones need Michelle).
• A Julius rule modification is proposed (additions, severity changes, removals — now editable via /admin/marketing-os/memory/banned-phrases).
• Pricing or Circle architecture changes (any change to tier mechanics, point values, redemption thresholds).
• A felt-not-told boundary is in tension (e.g., a press question that asks us to name the positioning publicly).
• Crisis or allergen-incident related outputs.
• Three pass-4-derived Michelle-only escalations:
  • The philosophy-name approval (§4.3 row 5 + §5.0.1 rule 1 + §6.8.1 brand_audiences.philosophy_name). Now load-bearing in five places; nothing downstream of §4.6 P0 #1 / #7 / #6 can ship until Michelle approves the canonical phrase. This is the single highest-leverage owner-decision in the document.
  • Cast-roster confirmation (§7.0.1 + §7.1). 8 of 9 §7.1 rows need either named-individual confirmation or down-scoping. Without this, §7 is aspiration; with it, §7 is operational SOP. Resolves naturally in the Sun cast 1:1s in Q1 (§11.1 hypothesis #6).
  • Migration 0053_campaigns.sql live-apply authorization. The Campaign object exists in code; the admin surface works; promote-from-proposal flow is built. supabase db push is held for explicit operator authorization per CLAUDE.md hard rule on Supabase changes. Until applied, every §6.5 archetype + every Sun proposal that wants to promote-to-Campaign waits.

Default routing is to UAQ standard queue. Escalation is the exception, not the norm — but the trigger list is explicit so cast and helpers know when to flag.

8.5 When a cross-channel deployment rule (§5.0.1) is at risk

Pass-4 added four cross-channel deployment rules in §5.0.1 (philosophy-name single-phrase-everywhere; Yardbird single-illustrator visual identity; Quintonil dual-brand; Lung King Heen distribution governor). These rules are by design uniform across surfaces — that's their structural value. Decision rule for when a single channel is about to violate one:

Rule of resolution: when a deployment-rule risk surfaces, the first response is delay, don't substitute. The rules are uniform-across-surfaces by design — running a substitute on one channel (a competing framing, a placeholder illustrator, a Michelle-only week) creates fragmentation that costs more to undo later than the delay costs now. Per §1.5: brand safety > efficiency.

9. 2026 anchor calendar

Helper ownership tagged. Cultural moments are anchored to canonical dates where known (e.g., Lunar New Year 17 Feb 2026; Mid-Autumn 25 Sept 2026). RAI events should be cross-checked against rai.nl/en/calendar quarterly; specific event lineups verified in pass 3.

9.1 Month-by-month anchor calendar

9.2 Cadence beats (recurring rhythms, year-round)

9.3 Pre-2026 prerequisites (engineering — must land before mid-Q1)

• ✅ public.click_tracking migration shipped at 0043_click_tracking.sql (May 2026). Roy click-tracking-summary rollup Power-Up live; conversion-upload dormant pending Google Ads developer-token (external).
• 🟡 Zenchef widget click-id pass-through still unresolved (marketing-attribution-strategy.md:42 open question; §11.1 hypothesis #1). Schema-ready on both primary (click-id) and SHA-256 hashed-email/phone fallback paths.
• 🔴 WhatsApp Business adapter activation still gated on Meta business verification (external; see social.HANDOFF.md).
• 🔴 Sun's rainy_tuesday_lunch Power-Up — still spec. The Sun loop that actually shipped is cultural_moment_t_minus_6_weeks (the first end-to-end live draft-emission loop). rainy_tuesday_lunch remains §6.3 spec, Q1 P0.

Without these, the §9 calendar still runs, but Tactics 4.4, 8.3 (Roy ad attribution), and most of §10 measurement become hypothetical.

9.4 Q1 P0 sequencing (pass-4 — the actual immediate calendar)

The §9.1 month-by-month table assumes the §4.6 + §5 + §6 pass-4 Q1 P0 fixes are done. They are not — every item below is currently pending. Sequencing matters: fixes 1 + 7 unlock from the same Michelle-approval input, and that input cascades to five surfaces (§4.6 P0 #1, P0 #7, P0 #6, §5.0.1 rule 1, §6.8.1 philosophy_name column). All other items are independent.

The sequence collapses to two waves:

1. Wave 1 (Week 1) — independent fixes: five fixes ship in parallel without owner input (IG bio, Yelp category, GBP category, Cloudflare allowlist, LinkedIn company page). Each is < 2 hours. Total wall time if all five run in parallel: 1 day.
2. Wave 2 (Week 2+) — philosophy-name-gated: Michelle approves the philosophy-name → three downstream copy ships (title tag, about-us body, businessrestaurants.nl) + three migrations (0060/0061/0062). Total wall time after approval: ~3 days.

The §9.1 calendar Jan/Feb anchors assume Wave 1 + 2 are done. If they're not done by end of Week 2, slip the Jan essay launch (§4.3 row 1) to mid-Feb to accommodate.

10. Measurement

Three layers — leading indicators (act on weekly), lagging indicators (review monthly), anti-metrics (deliberately ignore). Plus: the single dashboard widget Michelle looks at on a Monday morning.

10.1 Leading indicators (Insight weekly digest)

10.2 Lagging indicators (monthly review with owner)

10.3 Anti-metrics (deliberately do not optimize for)

• Follower count on IG / TikTok / LinkedIn — vanity. We have explicitly chosen save-rate over reach.
• Raw IG reach without save-rate context — reach without resonance is bot-territory.
• Generic "engagement rate" as a single number — meaningless without the underlying signal split.
• Number of posts per week as a goal — §1.8 explicitly inverts this. Cadence is a brand decision, not a default.
• Impressions / CTR on Google Ads without conversion attribution — Roy's metric is attributed-€, not click-volume. Cheap clicks that don't book are negative ROI.
• Email open rate for Clara's sends — opens are unreliable post-Apple Privacy Protection; measure on click-through to a booking action only.
• TripAdvisor ranking — secondary at best; the discovery game has moved to LLM citation surface (§4) and to NL press.

10.4 The single weekly dashboard widget Michelle should look at on Mondays

The widget is one composite line per major audience tier × per attributed lane:

SB lane:        saves last week + organic IG mentions of the dice + new-visit conversions tagged m_campaign=<organic_slugs>
CC lane:        GBP review velocity + Siren reply-time SLA hits + return-rate trailing 90d for the 45+ cohort
CB lane:        LinkedIn impressions (Michelle's account + company page) + Penn outreach in-flight count + RAI-event-week group inquiries
Health row:     Michelle-fronted cadence % (trip-wire at 80%) + philosophy-name coverage % + LLM citation surface count
   (pass-4)

Four rows. One number per row, one trend arrow, color-coded for delta vs. trailing 4-week average. 30 seconds to read; tells Michelle which tier is moving, which is stalled, AND whether the deployment-rule infrastructure is on-budget. Owner: Insight builds it (Q1). The "health row" is the pass-4 addition — without it, the three tier lanes can drift without anyone noticing the structural rules are slipping.

11. Open questions

11.1 Q1 2026 hypotheses to test

1. Zenchef widget click-id pass-through. Open question per marketing-attribution-strategy.md:42 — does the widget allow custom metadata in the booking flow? Resolution gates the entire §6.6 attribution mechanism. Owner: engineering + Zenchef contact. Q1 priority.
2. WhatsApp Business opt-in coverage. What % of current customers rows have marketing_opt_in=true AND a valid WhatsApp number? Determines whether Tactic 4.4 is meaningful at launch or starts thin. Owner: Insight one-off query. Q1.
3. Lunch dice → lunch cover lift. First-instance gamification hypothesis: does the dice produce a measurable lunch-daypart cover lift Tue–Fri vs. baseline, within 8 weeks of launch? Owner: Insight cohort tracking. Q1 launch, Q2 measurement.
4. Sun rainy-Tuesday Power-Up conversion rate. How many WhatsApp pushes convert into same-day reservations within 4 hours of send? Owner: Insight + Clara. Q1.
5. Het Parool active critic status. RESOLVED in pass 3 (2026-05-11): Het Parool's current restaurant critic is Mara Grimm; Gilles van der Loo also contributes to Het Parool culinair. NRC: Joël Broekaert active. Volkskrant: Hiske Versprille (succeeded Mac van Dinther). §4.4 NL press table updated with verified contact-points; Penn's outreach can proceed.
6. Cast member willingness to be on TikTok. §5.2 assumes the older end of cast (Michelle, sommelier) has more TikTok latitude than the global "TikTok is for the young" framing suggests — but the cast members have to want to be there. Owner: Sun + cast 1:1s. Q1.

11.1.1 Pass-4 owner-decisions surfaced (May 2026)

Items below are owner-decisions, not hypotheses — they require Michelle's input rather than data collection. Listed in priority order.

1. Philosophy-name approval (§3.3 #6 / §4.3 row 5 / §4.6 P0 #1 + #7 + #6 / §5.0.1 rule 1 / §6.8.1). Now load-bearing in five document surfaces. The Sazenka-pattern Michiu-coined philosophy-name is the single highest-leverage Michelle-input across the whole strategy. Until this lands, two title/copy fixes + the LinkedIn tagline + the position-essay framing + a Brand Memory schema column all wait. Suggested Q1 P0 owner-session: 90-min writing exercise with Penn, decision criteria are §3.3 #6 (two- or three-word framing analogous to "wakon-kansai") + §1.7 (Cantonese-first ordering). Estimated time: 1 working session.
2. Cast-roster confirmation (§7.0.1 / §7.1). 8 of 9 §7.1 rows need named-individual confirmation. Resolves naturally in Sun cast 1:1s in Q1 (Sun-led, see #6 above). Until resolved, §7 is aspiration; with it, §7 ships as operational SOP.
3. 2012 founding date / heritage continuity (§5.0.2 + §3.2 Pak Loh future-reference). Multiple external sources (Creditsafe + businessrestaurants.nl) verify Restaurant Michiu B.V. incorporated 2012. Owner question: has the Michiu brand been at Maasstraat 102 continuously since then, or was there a concept reset? Answer determines whether the heritage card is fully or partially playable for press (§4.4) and future-press (Pak Loh reference, §3.2).
4. €25/p packages on businessrestaurants.nl (§5.0.2). Currently visible on a B2B-targeted directory and may undercut the §0 shift #2 corporate-dining premium positioning. Owner question: (a) remain active offering, (b) entry-level funnel to higher-tier visits, or (c) retire/reposition. Penn cannot pitch the corporate-dining premium narrative cleanly while a €25/p offering is the directory-visible entry.
5. Migration 0053_campaigns.sql live-apply authorization (§6.5 / §6.0 / §8.4). Campaign object exists in code; admin surface built; promote-from-proposal flow works in dev. supabase db push held for explicit operator authorization per CLAUDE.md Supabase-discipline rule. Until applied, the Sun proposal queue → Campaign envelope flow is one step short of end-to-end.
6. Dutch LinkedIn personal profile claim (§5.0.2). Possible match michelle-zhang-07a9ba4 surfaced in search but not verifiable from snippet. Confirm or share the actual URL so Penn can begin the §5.5 cadence on Michelle's personal page.

11.2 Things this doc deliberately does not answer

• Whether to expand to a second Michiu location. Out of scope. SaaS B1 seeds prepare the codebase for multi-tenancy, but the strategic question of opening a second venue is owner-only and outside this strategy's horizon.
• Whether to pursue Michelin. The strategy focuses on building the brand surface that makes a Michelin star more likely IF pursued, not on the participation question itself. Defer to owner.
• Gen Alpha. Per §2.11 — honest low-fit; revisit in the 2028 strategy refresh.
• Catering / private events beyond chef's-table / group dining at the venue. Out-of-venue catering is a different business model; if pursued, would need its own strategy doc.
• Delivery / takeaway expansion. Trend 4.5 (pastry box) is the only takeaway-mode tactic; broader delivery is a different ROI calculation and would need owner direction.
• Influencer paid partnerships. The strategy explicitly chooses cast-led EGC over paid influencers (§1.4 + trend 6). Could revisit in 2027 if cast-EGC ROI plateaus.

11.3 Capabilities the OS needs to acquire to unlock deferred answers

Pass-4 sync (May 2026): most §11.3 capabilities have shipped. Status column added; only the genuine remaining external / cross-team dependencies remain pending.

Iteration protocol (end-of-pass-1)

Per the v4 prompt's required closing structure:

Three sections I'm least confident about (and why)

1. §2 Trend 4 / Tactic 4.4 (rainy-Tuesday Sun push). The mechanic is sound, but I'm making an assumption about WhatsApp Business opt-in coverage in our customers table that I have not verified. If most current customers have not opted in, the WhatsApp leg is small and email becomes primary — which weakens the kinetic-warmth voice anchor (email is slower-feel than WhatsApp). Validate opt-in rate before promoting this from "propose" to "approved Power-Up."
2. §0 strategic shift #2 (own corporate-dining lane near RAI). The rai-scheldestraat-strategy.md analysis is internally strong, but the revenue projection (€60–90k/year incremental weekday) leans on a 3-groups-per-event-week assumption that has not yet been validated against real event-agent conversion rates. The shift is directionally right; the size of the prize is a hypothesis.
3. §2 Trend 5 / Tactic 5.1 (chef's-note menu redesign). Hardest one to get the voice right. A single italic line per dish that does NOT feel mawkish, does NOT feel marketing-y, and IS specific to a year/place/person is genuinely difficult writing. The current draft examples ("Café Lan Fong Yuen, 1996"; "the cabbage cut at the angle he insisted on") need Michelle-validation before they're published.

Five sources I most want to verify (or weren't able to access)

1. Brandwatch DMT 2026 — full PDF cited examples. I have the headline content via the report's web view; the full PDF likely has additional named brand examples and direct quotes that would sharpen specific tactics. Pulling the PDF would let me cite more precisely on trends 3, 7, 9.
2. NRA 2026 State of the Industry — full report (paywalled). The free press summary names the headline statistics; the full report has the regional and segment cuts that would refine the higher-income-driving-growth claim for Amsterdam-Zuid specifically.
3. McKinsey 2026 restaurant consumer report — methodology. I cited the bifurcation finding; verifying sample size and EU vs. US split matters because if the bifurcation is US-only, the Amsterdam application is weaker.
4. Sprout Social 2026 Index — Threads-vs-X DAU data. Cited the 141.5M Threads vs. 125M X figure; would want to verify whether this is global, US, or platform-reported numbers because EU usage may differ.
5. Kantar Media Reactions 2025 — TikTok ad-spend-intent figure. Cited 61% of marketers planning to increase creator-content investment in 2026; want to verify whether this is global or split by region, and whether the food/hospitality vertical specifically tracks.

Recommended order of pass-2 follow-up

1. Tier-tag every existing tactic in §2 trends 1/2/4/5/8 (one of: SB / CC / CB / all-three). The audience tier × trend grid is in §1.9; the mapping is mostly mechanical, but a few tactics will reveal they don't actually serve who I imagined — that's the value of doing it.
2. §4 GEO action plan (highest-leverage per §0 shift #5). Pre-requires: live web research on Dutch food press citation patterns (Het Parool, NRC, Volkskrant, Misset Horeca, Foodie Amsterdam); verification of current Michiu structured-data state on michiu.nl. Helper(s) most relevant: Penn (citation strategy) + Carlos (structured data + GBP) + Insight (test-query Power-Up). NL-language query coverage is a hard requirement.
3. §2 trends 3, 6, 7, 9, 10, 11. Each completes the §2 structure with the same per-tactic structure + NL-specific bullet. Trend 11 (Gen Alpha) should be short — honest low-fit.
4. §3 benchmark scan. Live web research on Amsterdam + global benchmark venues. Verify current state — do not assume. Add a small Randstad-specific subsection: ADAM (Amsterdam/Rotterdam/Den Haag/Utrecht pop-up), De Silveren Spiegel (historic NL premium), Choux, plus the Yamazato / Sazanka / Bougainville / Yama set already in scope.
5. §6 Marketing OS integration (the typed-rules section). Compiles to Brand Memory migrations + Power-Up specs; depends on §2 trends 3/6/7/9/10/11 being complete because the tactics in those trends generate the Power-Up list. Must also include the reconciliation between the 5-persona legacy doc + 6-audience messaging matrix + the new 3-tier canonical structure (§1.9) — recommend brand_audiences table rows = 3 (the tiers), with legacy personas folded as channel-pattern metadata.
6. §5 channel playbook, with explicit "cadence per tier" rebuilt around §1.8 (less, with more weight). Then §7/§8/§9/§10/§11. Tactical close-out; pulls forward from §2 + §6.

Three Brand Memory ingestion risks (schema-gap surfaces for engineering)

1. sop.risk is currently a free-text field; this strategy assumes one concrete failure mode per trend. If the engineering team wants risk to be enumerated (low/med/high + category), the Pillar 1 entries need restructuring. Recommend: keep free-text for now, add a risk_severity enum column in migration 0030 if filtering by severity becomes useful.
2. The "voice anchor" field on each tactic is per-tactic-multi-voice (lead + secondary). Brand Memory helper_voice_distributions is currently per-helper-distribution. To ingest tactic-level voice tags, we either need a new join table (tactic_voice_anchors) or we ingest tactics as memory_documents chunks with metadata. Recommend the latter for pass-2 — lower migration cost, RAG retrieval gives us the join at query time.
3. m_campaign slugs proposed in tactics are not yet a typed entity. Currently they live as freeform UTM strings. If Sun's Campaign-archetype templates (§6) are to enforce a slug-uniqueness rule (so two campaigns can't claim the same m_campaign=lny_longtable_2026), we need a campaigns.tracking_slug unique column. Recommend adding to the next Campaign-object migration.

Footnotes