Chef Joe at Roadhouse — social launch playbook

0. Start here

The job is to launch Chef Joe at Roadhouse on social. Everything else in this document supports that or waits behind it.

The umbrella brand question is closed for now. Vivere Colorado launches on social at a later date under a different name, with To Live CO as the working candidate. Section 6 keeps that research so it is not stale when the date comes, and nothing in it holds up the launch.

Chef Joe is not a greenfield build. The site is live, the Instagram handle already exists, the menu is in print and the Google listing is already specified. What follows is a set of corrections and claims, in the order they have to happen.

The eight decisions

1. One string everywhere: chefjoeatroadhouse. The handle, the business name and the domain are the same words. You already own the Instagram handle under exactly that string.
2. Buy chefjoeatroadhouse.com and make it the primary. The site moves onto it; everything else redirects.
3. Buy chefjoesroadhouse.com today. It is printed on the order-ahead sheets already in people's hands and nobody has registered it. That is the one urgent purchase on the list.
4. joesdeltaroadhouse.com stays yours as a redirect. It reads as owning the partner's name, so it never becomes the brand home. It has to come out of the site's canonical, share and schema tags, which point at a parking page right now.
5. Instagram is a conversion, not a new account. Rename, rewrite the bio, switch to a business account, set the avatar. Never "start fresh" — that releases the handle.
6. Two feeds run for real. Chef Joe on Instagram, mirrored to Facebook. TikTok and YouTube are claimed and parked. One person posts everything and also cooks.
7. No clock hours anywhere until you rule. Three sources give three different answers, and the days disagree too. A wrong hour on a Google listing costs more than a missing one.
8. Nothing implies alcohol on a Chef Joe surface — not a word, not a photo, not a platform category name. TikTok's category is Food & Beverage. We say live music and arcade, never tavern.

What is already done

Shipped and verified tonight, 21 September, on Mimi's:

Both deploys were verified on their unique deploy URLs and on the live domain.

The Chef Joe fact base is also done: every candidate domain checked against the registry, every handle checked on Instagram, TikTok, YouTube and Facebook, the company's standing confirmed, and the brand art inspected. Section 7 records what was checked and what could not be.

What is blocked on you

Three answers release most of the work. The full list is in section 2.4.

• The hours ruling. Blocks the Google listing, the Facebook page and fourteen places on the site.
• The two domain purchases. Buying is yours to do. Nothing binds or redirects until the names are held, and one of them is unowned while being printed.
• The alcohol ruling on Chef Joe. The Spiked Shake row and the full-bar drinks note are still on the site and on the newest sheet. Mimi's is already clear.

One more thing needs to leave your outbox before accounts go public: the written note to TW and Miles covering ownership if the partnership ends, and their consent to "Roadhouse" in the handle, the domain and the Google listing name. Claiming a handle is the moment that question gets expensive. Section 5.9 has the asks.

1. Chef Joe at Roadhouse

This is the brand that launches first. The site is already built and live, the Instagram handle already exists, the menu one-pager is already in print, and the Google Business Profile spec is already written. Nothing here is a greenfield decision — it is a set of corrections and claims, in order.

Spelling is Chef Joe everywhere. No apostrophe-s. "at Roadhouse" states where the trailer sits; it does not say who owns it.

Three things gate the whole section and appear in every sub-section below:

• No clock hours on any profile until Joe rules. Three sources disagree (site JSON-LD: Sun 11:00–19:00 / Mon 14:00–20:30; the 21 Sept one-pager: Sunday 11am–7pm / Mon–Wed 12–5pm; the printed coupon and a Roadhouse graphic: Sundays 10:30am–7pm). The days disagree too — Sun & Mon versus Sun–Wed — so the bios below name no days either. Until Joe rules, the only day signal is a dated OPEN TODAY Story posted on the service day itself — never a permanent highlight, a profile field or a page of the site, all of which age silently (§1.3 Instagram).
• Nothing implies alcohol. Not a word, not a photo, not a platform category name. TikTok is Food & Beverage, never a "Restaurants & Bars" variant. We say "live music & arcade", never "tavern".
• Phone separation holds. (970) 462-2817 on Chef Joe surfaces only. The Roadhouse's number appears on Roadhouse surfaces only — including inside a "Hosting at Delta Roadhouse?" block on a Chef Joe page. Link to their page; never print their number on ours. (970) 209-8978 goes on nothing.

1.1 Domains

Where the architects split: one proposed chefjoedelta.com as primary; two proposed chefjoeatroadhouse.com. Take chefjoeatroadhouse.com — the handle already exists under that exact string, so name = handle = URL with nothing to explain.

Resolving the three-host mess. Right now the brand has three addresses and none of them is the one people are told to type:

1. The site is served at chef-joes-roadhouse-trailer.pages.dev (HTTP 200). Its sitemap and robots point there.
2. The site's canonical, og:url, og:image and JSON-LD url point at joesdeltaroadhouse.com — a Squarespace parking page. Every Facebook and Instagram link preview therefore tries to fetch an image from a page that does not serve it, and Google is being handed a parking page as the brand's canonical address.
3. The printed order-ahead sheet says chefjoesroadhouse.com, which resolves to nothing at all because nobody has registered it.

The fix is one primary and two redirects:

• chefjoeatroadhouse.com is the primary. Bind it to the chef-joes-roadhouse-trailer Pages project in Cloudflare. It becomes canonical, og:url, the og:image host, JSON-LD url / image / hasMenu, the sitemap host, the GBP website field, the link in every bio, and the URL on every reprint.
• chefjoesroadhouse.com 301s to it, host-wide. Register it today. It stays registered permanently because printed sheets do not expire — but it never appears in print again, since the "s" contradicts the no-apostrophe-s spelling.
• joesdeltaroadhouse.com 301s to it, host-wide. Never printed, never linked, never spoken. To move it, DNSSEC must be disabled at Squarespace first — changing nameservers with DNSSEC still active breaks resolution for the domain entirely. Order: disable DNSSEC at Squarespace → wait for the DS record to clear → move nameservers to Cloudflare → add a redirect rule.
• chef-joes-roadhouse-trailer.pages.dev stays alive as the origin, and nothing else. Point the site's own tags — canonical, og:url, og:image, JSON-LD url / image / hasMenu, sitemap — at this host now rather than leaving them on the parking page, because once the og:image tag is rewritten to this host (the §1.5 fix, site/index.html:31) a scraper can fetch the card from it — which it can never do while the tag names the Squarespace page. But the pages.dev string is never published: it contains chef-joes-, the apostrophe-s spelling this section bans from print, so it does not go in a bio link, the Facebook or YouTube website field, or the GBP website field. Those fields stay empty until chefjoeatroadhouse.com resolves. Nothing is lost by waiting — the accounts stay private and unposted until the partners' written OK lands, and the GBP is not made search-visible until the photos are in. If a destination is genuinely needed before DNS resolves, give the phone number, never the pages.dev string.

One more host to kill: the retired Pages project chef-joes-roadhouse still serves an old build with a working /api/order writing into an unwatched KV. Delete it or redirect it. Joe's own private-events build still links it — _campus-roadhouse/private-events/index.html:797 — and so does Vivere Colorado Food Trailer/_share/partnership-hub/public/index.html:328. Both are in Joe's repos: he edits and redeploys them himself, no ask to the partners required. The anchor text at :797 also reads "Chef Joe’s at Roadhouse" — the banned apostrophe-s spelling — and must be corrected in the same edit.

Buy order today, in one sitting: chefjoeatroadhouse.com, then chefjoesroadhouse.com. The second one is the urgent one — it is the only domain in this table that is already in print and unowned.

1.2 The handle family

One string everywhere: chefjoeatroadhouse. 18 characters — inside every platform's limit (TikTok's is 24). It matches the business name, the primary domain and the sign.

Say this plainly: Instagram is a conversion, not a creation. Joe made @chefjoeatroadhouse on 21 Sept as a personal account under the display name "Joseph". Do not create a second one and do not let anyone "start fresh" — the handle is held, and re-creating it means releasing the string for the minutes it takes. The work on Instagram is: rename the display field, replace the bio, switch to a Professional → Business account, link the Facebook Page, set the avatar. Everything in §1.3 Instagram assumes that account.

Everything else in this table is a fresh claim except Threads, which appears by itself once the Instagram account is converted.

1.3 Per platform

Instagram — convert the existing account

The primary fed account. Delta County's food discovery happens in Instagram search and location tags, and it is the one surface a solo operator can feed from a phone at the service window.

Display name: Chef Joe at Roadhouse

Bio — 130 / 150 characters:

Smash burgers & triple-cook tallow fries from the trailer in the courtyard at Delta Roadhouse. 215 Ute St, Delta CO. Order ahead ↓

Link in bio: leave the field empty until chefjoeatroadhouse.com resolves, then https://chefjoeatroadhouse.com/#order. Do not publish the pages.dev string — it contains chef-joes-, the apostrophe-s spelling this section bans (§1.1). Nothing is lost by waiting: the account stays private and unposted until the partners' written OK lands (step 14). One link only — no link-tree service; the site already carries the menu and the campus rail.

Category: Food Truck. Never Restaurant, Bar or Pub.

Contact fields: Phone (970) 462-2817, shown. Address 215 Ute Street, Delta, CO 81416, shown — 215 always, never 209. Email blank until a bookings inbox exists on the primary domain; the site's email:bookings value is null today and a personal Gmail does not belong on a consumer profile.

Hashtags: exactly five per post, never more. Fixed core #chefjoeatroadhouse #deltacolorado #smashburgers plus two topical from #tallowfries #westernslope #foodtrailer.

Highlights and pinned posts: - Pinned 1 — THE MENU: one carousel from the 21 Sept sheet, item names only, no prices (prices change; the site carries them). Single & Double Smash Meal, Tallow Fries, Joe's Way, Gochujang Chicken Salad, Bang Bang Chicken, 3-Cheese Grilled Cheese, Kids Slider, Milkshake. No THE SMOKE card, no Cream Cheese Ball card, no Spiked Shake card. - Pinned 2 — HOW ORDER-AHEAD WORKS: four frames — pick what you want, pick a pickup time, pay at the window, it's hot when you get there. - Pinned 3 — WHERE WE ARE: the courtyard, 215 Ute Street, the A-frame. - Highlight THIS WEEK — empty until Joe rules the hours (UNKNOWN-NEEDS-INPUT). An Instagram highlight is permanent and shows no date, so a Story added three weeks ago reads as today's hours to someone standing at the window — it is a published hours field, not a temporary note, and "nothing goes stale" is the opposite of true. Until the ruling: on each service day Joe posts a plain OPEN TODAY Story with the date written on the graphic, and adds it to the highlight only after deleting the previous one, so the highlight never holds more than one dated card. After Joe rules, the same clock hours go into this highlight, the GBP hours, the Facebook hours and every site place in one sitting (§1.5). - Highlight ORDER AHEAD — a screen recording of the order flow. - Highlight EVENTS — one Story per catered event, after the event, photos of the food and the room only. This is where catering lives on social. It gets no account of its own.

Profile and cover image: Must be made — no square Chef Joe mark exists. Build a 1080×1080 master: "CHEF JOE" stacked in Anton 400 (never synthesised bold), bone #E5D6BD on ink #0C1F39. The only lockup on disk — C:/Users/sutli/Desktop/Developer/videos/chefjoe-sunday-sep20/assets/chefjoe-lockup.png, 1620×460 — is horizontal and contains the Delta Roadhouse guitar pick, which is the partner's mark and may not be Chef Joe's. Crop the type half, rebuild it stacked, and never use pick-navy-879.png or any pick-* asset as a Chef Joe avatar. Export the same master at 1024×1024 on white for the GBP logo slot.

Config steps, in order, with the app open: 1. Open the existing @chefjoeatroadhouse account. Confirm the handle field reads exactly chefjoeatroadhouse. 2. Edit profile → change Name from "Joseph" to Chef Joe at Roadhouse. 3. Paste the bio above. Confirm it fits (150 limit) and that no day or hour appears in it. 4. Settings → Account type and tools → Switch to professional account → Business (not Creator — Business exposes the Order Food action button, the address field and the Food Truck category, and it is what the scheduler needs for API posting). 5. Category → Food Truck. 6. Create the Facebook Page first (next sub-section), then return here: Settings → Accounts Centre → link the Instagram account to the Page "Chef Joe at Roadhouse". Never link it to the Vivere Web Page or the Delta Roadhouse Page. 7. Contact options → Phone (970) 462-2817 shown; Address 215 Ute Street, Delta, CO 81416 shown; Email left blank. 8. Action button → Order Food → the order-ahead URL above. Leave the button off until the domain resolves; the pages.dev string is not published. 9. Upload the 1080×1080 avatar. 10. Privacy → Tags and mentions → allow tags and mentions from everyone, and set "Manually approve tags" ON. Tagging and mentions still work — the Roadhouse and Mimi's can tag the trailer freely; the tag simply waits for one tap before it appears on the Chef Joe profile. @delta_roadhouse is a bar that posts drinks and bar nights, and an auto-approved tag puts their glassware into the Tagged tab of a Chef Joe surface, which R5 forbids. This also matches the Facebook Page, which already reviews tags before they appear (Facebook step 8). 11. Accept Collab invitations from @delta_roadhouse and @_mimis_est2024 only. 12. Security → two-factor by authenticator app on Joe's phone. Print the backup codes and keep them with the trailer paperwork and the registrar login. Recovery email: Joe's own inbox — never a Mimi's or Vivere Web address. 13. Connect to the scheduler as a new Instagram connection, only after step 6. Do not reuse 55698 (Mimi's) or 58435 (@vivereweb). Record the new connection id. 14. Hold the account private and empty until TW & Miles have confirmed in writing that "Chef Joe at Roadhouse" may use their mark. The name, the domain and the sign all contain "Roadhouse"; the written OK is the thing that makes the whole family safe, and it costs one message to ask. Convert the account now, post nothing until the reply lands.

Facts used: "Smash burgers & triple-cook tallow fries" — site title and h1, plus the one-pager's three-stage cook description (SOURCED). "The trailer in the courtyard at Delta Roadhouse" — site JSON-LD description (SOURCED). 215 Ute Street, Delta, CO 81416 — site footer/JSON-LD and the 21 Sept one-pager (CONFIRMED, R7). "Order ahead" — the site's own CTA (SOURCED). (970) 462-2817 — CONFIRMED, R6. Handle exists, created 21 Sept, personal, 0 posts — browser-checked 21 Sept (CONFIRMED). Days and hours — omitted, UNKNOWN-NEEDS-INPUT.

Facebook — create a new Page

Delta County organises on Facebook, and Facebook Events is the right primitive for special nights. The Page is also the technical parent of the Instagram Business account, the scheduler connection and Collab permissions. It is a standalone Page, not a location Page under Delta Roadhouse — a location Page puts the asset on their side and implies their licence covers the food.

Display name: Chef Joe at Roadhouse · Username: /chefjoeatroadhouse

Bio (the short intro field) — 97 / 101 characters:

Smash burgers & triple-cook tallow fries from a food trailer in the courtyard at Delta Roadhouse.

About (the long field) — 205 / 255 characters:

Smash burgers and triple-cook tallow fries from a food trailer in the courtyard at Delta Roadhouse, 215 Ute Street, Delta, Colorado. Real food, locally sourced and hand made. Order ahead and skip the line.

Link: Website field → leave empty until chefjoeatroadhouse.com resolves, then https://chefjoeatroadhouse.com/. The pages.dev string is never published (§1.1). Until then the action button is Call now → (970) 462-2817; switch it to Order Food → /#order the day the domain binds.

Category: Food Truck (primary only). Do not add Bar, Pub, Restaurant or Caterer as a Page category — catering is described in the About text and the Services tab, not as a category. Never add "Serves alcohol" or any bar amenity.

Contact fields: Phone (970) 462-2817. Address 215 Ute Street, Delta, CO 81416 with the map pin on — this is a listing field, so it carries the true address. Email blank. Price range $$ (matches the site's JSON-LD priceRange). Hours fields left blank until Joe rules.

Hashtags: none. House rule — Facebook captions end with the order-ahead URL instead, tagged ?utm_source=facebook&utm_medium=social.

Pinned and featured: - Pinned: the same MENU carousel as Instagram, names only, no prices, caption pointing at the order-ahead link. - Featured: the "How order-ahead works" post. - Services tab: "Order ahead — pickup at the courtyard window" and "Events — Chef Joe cooks for events hosted at Delta Roadhouse; ask at the venue." Mimi's Sweet Treats is a separate LLC with a 50/50 owner and may not be named on a public Chef Joe surface until Naomi confirms it in writing — the same gate this section applies to the GBP description. Once that confirmation is on file, and only then, the line becomes "Events — Chef Joe cooks for events hosted at Delta Roadhouse and for parties at Mimi's Sweet Treats; ask at the venue." No rates, no prices; the catering rate value is null and stays null until the P&L answers it. - Facebook Events: one per special night, created the week before. If the Roadhouse is hosting, they create it and add the Chef Joe Page as co-host — never the other way round. A co-host inherits their event copy, so read the description before accepting, and decline the co-host if it names a drink, a free-drink offer or the bar — the 27 Sept football coupon (§1.5) shows that copy already exists. Event copy on our side names the game in type only and never the beer.

Profile and cover image: same 1080×1080 CHEF JOE avatar as Instagram (must be made). Cover 820×312: a centre crop of site/assets/photos/plate-smash-fries.webp (1600×900, the only landscape photo on disk) until the 20 Sept shoot's trailer/courtyard frames land. No draft, no bar, no Roadhouse logo in frame, and no Roadhouse photo at all without their written OK.

Config steps: 1. Create the Page from Joe's personal profile. Page name exactly Chef Joe at Roadhouse. 2. Set the username to chefjoeatroadhouse immediately — usernames unlock as soon as the Page exists, and this is the string Instagram and the domain both use. 3. Category → Food Truck. Price range → $$. Leave Hours blank. 4. Paste the short bio and the About text above. 5. Address 215 Ute Street, Delta, CO 81416, map pin on. Phone (970) 462-2817. Email blank. 6. Upload the avatar and the cover crop. 7. Settings → Page roles: Joe is the only admin, Full control. Naomi gets no role here — this is not a Mimi's asset. Adding a backup admin is an open question for Joe; if yes, it should be Joe's own second login, never a Roadhouse partner. 8. Turn on "Allow others to tag photos" and "Allow people to mention the Page"; review tags before they appear on the Page. 9. Link the Page's Instagram account to @chefjoeatroadhouse so Collab posts and cross-posting work. 10. Add the Page to the existing Facebook scheduler connection 39225. That connection will then carry three pages — Mimi's 377584465431192, Vivere Web 1141952239011602 (the default), and this new one. Record the new pageId the day it exists and pass it explicitly on every single post. The default is the agency page; a post that forgets the pageId lands on @vivereweb, which breaks R1. Before the first scheduled Facebook post, send one test post to an audience of Joe only and confirm where it lands. 11. Two-factor on Joe's personal profile by authenticator app — the Page's real security is the profile's.

Facts used: JSON-LD description, hero copy, footer address and phone, site CTA (all SOURCED from the live site). "Real food, locally sourced and hand made" — the agreed positioning line (SOURCED). priceRange $$ — site JSON-LD (SOURCED). Standalone Page not a location Page — prior build decision (SOURCED). Scheduler connection 39225 and the three pageIds (SOURCED). Facebook username availability — LIKELY FREE, UNVERIFIED.

TikTok — reserve only, post nothing

Claim the string so it is never squatted. TikTok search matters for under-30s in Montrose and Grand Junction, but a solo operator cannot feed a third format, and TikTok posts cannot be edited or deleted through an API — a TikTok that posts twice and stops looks worse than one that never started.

Display name: Chef Joe at Roadhouse

Bio — 73 / 80 characters:

Smash burgers & tallow fries. The courtyard at Delta Roadhouse, Delta CO.

Link in bio: leave empty until the domain resolves, then https://chefjoeatroadhouse.com/#order. The pages.dev string is never published (§1.1). The link field requires a Business account.

Category: Food & Beverage. This is binding and it is the one point where an architect was overruled: one proposal said to pick TikTok's "Restaurants & Bars" naming. A category containing the word "Bars" on a Chef Joe surface breaks R5, which bans implying alcohol including inside a platform category name. Select Food & Beverage and nothing else.

Contact fields: no phone, no email, no address — TikTok has no address field and the shared line does not belong on a surface that does not need it. The bio names the courtyard and the city only.

Hashtags (for the day it posts): #chefjoeatroadhouse #deltacolorado #smashburgers #tallowfries #westernslope plus #fyp.

Pinned: nothing until a clip exists. The avatar, bio and link are the entire surface. When it does go live, pin the griddle clip from the 20 Sept shoot.

Profile image: the same 1080×1080 CHEF JOE square.

Config steps: 1. Register with Joe's phone number, using the same login email as the Instagram account so recovery lives in one place. 2. Set the handle to chefjoeatroadhouse (18 of 24 characters allowed). 3. Switch to a Business account — required for the bio link field. 4. Category → Food & Beverage. 5. Paste the bio. Leave the link field empty until the domain resolves. Upload the avatar. 6. Two-factor on. 7. Do not connect it to the scheduler. A connected-but-empty TikTok tempts filler posting. 8. The rule for the day it posts: re-upload the Instagram Reel as-is. Never shoot anything TikTok-only. Nothing posts here until Instagram has run 90 days without a missed week.

Facts used: menu strings from the live site and the 21 Sept one-pager (SOURCED). Handle free on TikTok — browser-checked logged out 21 Sept (CONFIRMED). Category ruling — R5 plus three judge must-fixes (binding).

YouTube — reserve only

Handle reservation and nothing more. Shorts re-uploads come much later, if ever. Zero cadence.

Display name: Chef Joe at Roadhouse

Channel description — 244 / 1000 characters:

Chef Joe at Roadhouse. Smash burgers and triple-cook tallow fries from a food trailer in the courtyard at Delta Roadhouse, 215 Ute Street, Delta, Colorado. Real food, locally sourced and hand made. Order ahead and skip the line. (970) 462-2817.

Link: channel links → leave empty until the domain binds, then https://chefjoeatroadhouse.com/. The pages.dev string is never published (§1.1). Do not write the domain into the description until it resolves either.

Category / channel keywords: food trailer, smash burgers, Delta Colorado, Western Slope. Country: United States.

Contact fields: the phone and street sit inside the description text only; YouTube has no NAP fields and none should be invented.

Hashtags: not applicable until content exists.

Profile and cover image: the same 1080×1080 CHEF JOE square. Banner 2048×1152 from plate-smash-fries.webp if one is wanted; otherwise leave it blank rather than ship a stretched crop.

Config steps: 1. Create the channel as a Brand Account under Joe's Google account — not a renamed personal channel. The Mimi's channel (UCYjprG_JWnGyl8LCB6MRLBQ) is a renamed personal channel carrying personal playlists; do not repeat that. 2. Use the same Google account that will own the Google Business Profile, so one login manages GBP and YouTube. 3. Claim the handle @chefjoeatroadhouse. 4. Paste the description. Set the channel name to Chef Joe at Roadhouse. 5. Upload the avatar. Set country and keywords. 6. Do not connect it to the scheduler. Post nothing.

Facts used: site JSON-LD and footer (SOURCED). Handle free on YouTube — browser-checked 21 Sept (CONFIRMED). Mimi's channel id (CONFIRMED).

Threads — reserve only, never open the app

Threads is created automatically from the Instagram account with the same handle, so claiming it costs one tap and holds the string. It is never authored directly.

Display name: Chef Joe at Roadhouse

Bio — 85 / 500 characters:

Smash burgers & triple-cook tallow fries. The courtyard at Delta Roadhouse, Delta CO.

Link: same as Instagram. Category: inherits Instagram. Contact fields: none. Hashtags: none. Pinned: none. Profile image: inherits the Instagram avatar.

Config steps: 1. After the Instagram account is converted, accept the Threads profile creation prompt. Confirm the handle carried over as chefjoeatroadhouse. 2. Paste the bio above (it stays day-free and hour-free). 3. Turn on "Share to Threads" on the Instagram side so Instagram posts reach it with one toggle and no extra authoring. 4. Do not delete the profile. Do not open the app to post.

Facts used: same as the Instagram bio. Threads cannot be checked logged out — the handle is inherited, not claimed, so there is nothing to verify beforehand.

Google Business Profile — create, after a duplicate check

The highest-value surface here. Somebody searching "burgers delta co" or "chef joe delta" on Maps finds this listing or finds nothing. Build it to the existing GOOGLE-BUSINESS-PROFILE-BUILD.md spec with six corrections: THE SMOKE out of the description (the spec has it at :142), the "with the Delta Roadhouse tavern open" line out (:145), hours left empty, the opening date left unset, no catering service area, and the logo slot changed (the spec names site/assets/brand/pick-navy-879.png at :184, which is the Roadhouse's pick).

Business name: Chef Joe at Roadhouse — exactly, no descriptors. Not "Chef Joe at Roadhouse – Smash Burgers Delta CO". Keyword-stuffed names are a policy violation and a suspension trigger.

Description — 601 / 750 characters:

Real food, locally sourced and hand made, from a trailer in the courtyard at Delta Roadhouse.

Smash burgers built on American Wagyu, smashed hard on a screaming griddle with Joe's own rub and sweet onions. Fries cooked in three stages and finished in beef tallow, to order. The menu runs past the usual trailer fare: gochujang chicken salad, bang bang chicken, loaded Joe's Way fries, a three-cheese grilled cheese, kids sliders and milkshakes.

In the courtyard at 215 Ute Street, Delta. Order ahead online and pick up at the window.

Catering for events hosted at Delta Roadhouse. Ask at the venue.

R4 bounds catering to two channels: events Delta Roadhouse hosts, and Mimi's parties. A line promising "parties and events across Delta and Montrose" advertises a standalone catering offering on the highest-authority public surface the brand has — exactly what R4 exists to prevent — so it is not in the version above.

If Naomi confirms in writing that Chef Joe may name Mimi's on a public listing, the last paragraph becomes "Catering for events hosted at Delta Roadhouse, and for parties at Mimi's Sweet Treats. Ask at the venue." — that version runs 641 / 750 (637 − 100 + 104; recount in the field before pasting). Ship the first version until that confirmation exists.

Links: Website → leave empty until DNS binds, then https://chefjoeatroadhouse.com. Menu link → likewise empty until then, and afterwards the same host + /#menu. The pages.dev string is never published (§1.1), and the listing is not made search-visible before the photos are in anyway, so nothing is lost by waiting. Food-ordering link → leave empty, until the Roadhouse's Clover "JOE'S MENU" category stops selling cones and soda under the Chef Joe brand.

Categories: Primary Food truck. Secondary Caterer. Secondary Hamburger restaurant. All three are distinct from the Roadhouse's venue categories and from Mimi's Ice cream shop.

Contact fields: Phone (970) 462-2817 and no additional numbers. Email: none. Address 215 Ute Street, Delta, CO 81416, United States — shown, as a storefront, because the trailer is a fixed pad with permanent signage. No catering service area — do not add Delta / Montrose / Delta County as a service area. R4 bounds catering to Roadhouse-hosted events and Mimi's parties, and §1.5 still lists "whether Chef Joe takes independent off-site events at all" as an open question; publishing a multi-county service area answers it on Google's behalf. UNKNOWN-NEEDS-INPUT until Joe answers it. Hours: leave empty. Opening date: leave unset — UNKNOWN-NEEDS-INPUT. Google shows that field to customers and no source states when the trailer first served; ask Joe for the actual first-service date and enter it only then. An "opened September 2026" on a trailer that was already trading is a wrong fact in a listing Google scores for consistency.

Attributes — YES: Takeout · Outdoor seating · Family-friendly · Casual · Quick bite · Catering available · Wheelchair-accessible (confirm the courtyard in person first). NO: Delivery (the sheet's "call to arrange delivery" is a phone offer with no radius, fee or minimum — it is not a listing claim; note that the sheet already in businesses' hands says "Delivery Available" and "Order ahead · We deliver", so the listing and the print will disagree — fold the delivery wording into the reprint decision below) · Dine-in · Reservations · Serves alcohol. On "Serves alcohol", prefer leaving it unset if the interface allows: Google surfaces some negative attributes as a visible chip, and the goal is no alcohol word on the listing at all, not a "No alcohol" badge. Check what actually renders after publish.

Photos and posts: Logo slot = the square CHEF JOE wordmark on white (must be made — not pick-navy-879.png). Cover = trailer/courtyard exterior from the 20 Sept shoot. Food ×3 = plate-smash-fries.webp, smash-griddle.webp, fries-tallow.webp. Menu photo = a clean re-render of the 21 Sept sheet without the Spiked Shake line and without the printed domain until it resolves. Google Posts: one per service week — a photo plus two sentences plus the order link, the same content as the Monday Instagram post. Seed three Q&A entries answered from the site copy only: "Do you take orders ahead?", "Where do I park?", "Is it kid-friendly?"

Config steps: 1. STEP 0 — duplicate check, before anything is created. Search Google Maps for Chef Joe, Chef Joe's, Joe's Catering, Vivere Colorado and 215 Ute Street. If any stray listing exists, claim and merge it. Never create a second. A duplicate is far harder to remove than to prevent. 2. Also search for any Vivere Web profile carrying (970) 462-2817. A phone number shared across two profiles is a suspension trigger. If one exists, change the agency's number, never the trailer's. 3. STEP 1 — written OK from TW & Miles on file for the name "Chef Joe at Roadhouse", because it contains their mark. 4. STEP 2 — create from one Google account. The same account owns this profile and the YouTube Brand Account, and, if Naomi agrees, eventually manages Mimi's listing as well — so Google sees one operator, not three rivals. Which Google account: UNKNOWN-NEEDS-INPUT. 5. Enter the name exactly. Enter the categories in the order above. 6. Enter the address as a shown storefront. No service area. 7. Enter the phone. Leave the food-ordering link empty. Leave website and menu links empty until DNS binds, then add them. 8. Paste the description. Leave the opening date unset. 9. Set every attribute above, explicitly, except "Serves alcohol" — leave that unset if the interface allows, and check after publish that no alcohol word renders on the listing. 10. Leave hours empty. When Joe rules, enter them here, on Facebook, in the Instagram THIS WEEK highlight, and in every one of the fourteen site places listed in §1.5 — in one sitting. Change all of them or none of them. 11. Upload the photo minimum set. Do not make the profile search-visible until the photos are in. 12. Verification will probably be video. Record one unbroken take on a service day: the trailer, the A-frame, once installed, reading CHEF JOE AT ROADHOUSE, the courtyard, the 215 Ute street context, the cooking equipment, and Joe operating it. 13. After it verifies, and only then, replicate the byte-identical NAP to Apple Business Connect, Bing Places and Yelp. Also submit the free Delta County Tourism calendar listing (tourism@deltacounty.com, 970-874-2108 — SOURCED, _research/02-roadhouse-profile.md:438) with the same string.

The suspension risk of stacking listings at one address. Google does not forbid two businesses at one street number, but it does suspend listings that look like one business filing twice. The defence is distinctness on every axis, and it must hold before submission:

The only thing the Roadhouse row has to establish is that their number is not (970) 462-2817. Their digits are theirs to publish, not ours to transcribe, and no Chef Joe or Mimi's surface ever carries them (R6).

The A-frame panel exists as a 21 Sept print design at _print/aframe-open-2026-09-21/ and reads OPEN · WAGYU SMASH BURGERS · CHEF JOE AT ROADHOUSE — correct spelling, verified in the file. It is not confirmed printed, installed or permitted: the 3 Sept brand-meeting checklist still carries the open question to TW & Miles, "Can we put an A-frame at the street, and is signage on the fence allowed?" Separate visible signage is the whole evidence base for two listings at 215 Ute, so print the panel, install it, photograph it, and get the placement OK in writing from TW & Miles before the GBP is submitted — not after.

No two rows share a phone, a category, a website or an entity. Two share a street number, which Google permits for genuinely distinct businesses with separate visible signage — which is why the A-frame is not decoration, it is the evidence. The canonical NAP strings, byte-identical wherever they appear:

• Chef Joe at Roadhouse / 215 Ute Street, Delta, CO 81416 / (970) 462-2817
• Mimi's Sweet Treats / 209 Ute Street, Delta, CO 81416 / (970) 874-3163

Never create a fourth listing at these addresses — not for catering, not for an umbrella brand, not for "Mimi's at Roadhouse". Catering is the secondary category on this one profile and nothing else.

Facts used: "Real food, locally sourced and hand made" — agreed positioning (SOURCED). American Wagyu, Joe's own rub, sweet onions; three-stage tallow fries; gochujang chicken salad, bang bang chicken, Joe's Way, three-cheese grilled cheese, kids sliders, milkshakes — all from the 21 Sept one-pager, which is the menu source of truth (R3, SOURCED). THE SMOKE and the Cream Cheese Ball are gone and appear nowhere (R3). Address and phone (CONFIRMED, R6/R7). Categories and attributes — existing GBP build spec (SOURCED). Entity in good standing — Colorado SoS, read 21 Sept (CONFIRMED). Hours — UNKNOWN-NEEDS-INPUT. Opening date — UNKNOWN-NEEDS-INPUT. Owning Google account — UNKNOWN-NEEDS-INPUT. A-frame printed / installed / permitted — UNVERIFIED. Delta Roadhouse's phone number — UNVERIFIED, deliberately not transcribed (R6). Off-site catering service area — UNKNOWN-NEEDS-INPUT (R4).

Website — use the existing build, fix it first

https://chef-joes-roadhouse-trailer.pages.dev is live and consistent on name, phone and address, but it is behind the newest menu and it points at three hosts. It is the build that chefjoeatroadhouse.com will serve — the destination of every bio link and the website the GBP is scored against — so it must be true before the domain binds and before any handle is promoted. The full fix list is §1.5.

Title tag — 69 characters:

Chef Joe at Roadhouse — Smash Burgers & Triple-Cook Fries · Delta, CO

Meta description — 158 / 160 recommended:

Smash burgers and triple-cook tallow fries from a trailer in the courtyard at Delta Roadhouse. Order ahead and skip the line. 215 Ute Street, Delta, Colorado.

Schema: one FoodEstablishment; servesCuisine Burgers, American; priceRange $$. Catering stays a Service (serviceType Catering) whose provider is that same FoodEstablishment — never a second entity.

Contact fields: (970) 462-2817; 215 Ute Street, Delta, CO 81416 in the JSON-LD, the footer, /book/ and the 404 page; the campus rail may say "215 & 209 Ute Street". Email stays the honest "Email TBD" chip until an inbox exists.

Config steps: 1. Do the §1.5 fixes in one commit, from inside site/, deployed with deploy-prod.ps1. Deploying from the project root makes every Function vanish. 2. Stage named paths. Never git add -A. 3. Keep noindex on every page until both (a) the primary domain resolves to Cloudflare Pages and (b) the Roadhouse Clover "JOE'S MENU" category is corrected. Then lift it on all four pages at once. 4. Keep the CSP self-only. No pixels, no embeds — the privacy page promises none. 5. Verify the OG image actually renders in a Facebook link preview after the host change, before any bio link goes public.

Facts used: site title, JSON-LD description, footer, phone, address (all SOURCED from the live build). Live status HTTP 200 (CONFIRMED, 21 Sept).

1.4 Posting cadence and cross-promotion

One operator who also cooks. Joe physically posts everything himself, on the same days he is running a griddle. The plan has to survive a bad Sunday, so it is built around what the service day already produces rather than around what a content calendar would like.

The week:

Ceiling: 2 feed posts + 3 Stories per week. TikTok 0–1 per week and only as a repost of the Monday Reel, and only after 90 clean Instagram days. YouTube 0. Threads 0 authored.

The floor is the important number: one Story on every service day. A ten-second phone clip at the griddle — no edit, no caption fuss. This is the cheapest possible signal that the trailer is open, and it is what stops the Instagram account from reading as closed on a week when nothing else ships. A profile with a Story from this morning looks open. A profile whose last post is nine days old looks shut, whatever the bio says.

Instagram Collab mechanics. A Collab post appears on both accounts' grids and pools the likes, comments and reach into one post — so a launch post co-posted with @delta_roadhouse (151 followers) reaches their audience natively instead of asking Joe's audience to go look somewhere else. How it works: compose the post on @chefjoeatroadhouse → on the tagging screen tap Invite collaborator → add the other account → the post stays pending on their grid until they accept. Both accounts must be Business or Creator accounts, which is why the Instagram switch in §1.3 matters.

Rules for it: invite @delta_roadhouse on courtyard posts and @_mimis_est2024 on anything that touches both counters. Accept Collab invitations from those two accounts and nobody else. Never Collab a post that shows a drink, a bar or a Roadhouse licence claim. And a Collab is an invitation, not an assumption — if they do not accept, the post still stands on its own.

Cross-promotion beyond Collab is just tagging: tag @delta_roadhouse in the caption when the courtyard is the subject, let them tag the trailer back and approve the tag if the photo is clean (tag approval is on — a tavern account posts glassware, and R5 keeps it off a Chef Joe surface), and re-share anything they post that features the trailer. Never cross-post with @vivereweb in either direction and never list Chef Joe as an agency case study — R1 keeps those two worlds apart permanently.

The review rule: cadence down, never ambition up. On the first Sunday of each month, count what actually shipped in the last four weeks. If two of those four weeks missed the plan, next month's plan becomes the lowest number that actually shipped — for example 1 feed post plus Sunday Stories. The plan is never raised because a week went well. A good week is capacity, not a commitment; a schedule that ratchets upward after every good week is how a one-operator feed dies in eight weeks. The only number that may go up is the one Joe raises deliberately, in writing, after a month where the plan shipped every week.

1.5 Site fixes

All paths are relative to the Chef Joe site repo. Deploy from inside site/ with deploy-prod.ps1; stage named paths only.

Three things that are not site fixes but block the same launch, so they belong on the same list: the written OK from TW & Miles on the use of "Roadhouse" in the name, the domain and the sign; the correction of the Roadhouse's Clover "JOE'S MENU" category, which is what keeps the GBP food-ordering link empty and noindex switched on; and the printed football coupon for Sun 27 Sept, which is a Chef Joe alcohol offer already in circulation.

The 27 Sept coupon. It is built in this repo — _print/coupon-football-2026-09-27/, a 3-up HTML plus PDF plus gen-coupon.py — and its headline reads "Free Lagerado with the purchase of any meal from Chef Joe", with "Ice cream specials & milkshakes by Mimi's Sweet Treats" underneath and the small print "The Lagerado is poured by Delta Roadhouse under their liquor licence — 21+, valid ID required." R5 forbids a free-beer offer tied to a Chef Joe purchase, and forbids naming Mimi's on an alcohol piece. Actions, before 27 Sept:

1. Pull the printed batch.
2. If the Roadhouse still wants the offer, they reprint it as a Delta Roadhouse piece — their name in the headline, their licence, and Chef Joe is not the purchase trigger.
3. Delete or archive coupon-football-2026-09-27/ out of the Chef Joe repo so a re-render cannot resurrect it.
4. Nothing from it goes on the Instagram, Facebook, TikTok, YouTube or GBP surfaces, and the Facebook Event for that night names the game only.

Chef Joe's own 27 Sept line is already safe and sourced — the one-pager's "Sun 27 Sept · open late — Broncos vs Rams".

2. Launch sequence, checkpoints and open questions

2.1 Where the three proposals disagreed, and what this section runs with

2.2 Launch sequence

Nothing in this table depends on a row below it. Anything gated on an answer says so in "Depends on" and stalls there rather than shipping wrong.

2.3 Checkpoints

Attorney — not on the Chef Joe launch path, but start it now because it is the slowest item

Naomi — CEO, 50/50 owner of Mimi's Sweet Treats LLC (a separate entity)

Ask once, as one batch. Resolved already tonight and not to be re-asked: the canonical TikTok (@mimis.sweettreats320, fixed) and the Facebook Page identity (377584465431192 and profile.php?id=61562002972726 are the same object, 301 confirmed).

TW and Miles — owners of Delta Roadhouse, holders of the liquor licence

Nothing containing "Roadhouse" — no further handle, no GBP name, no domain binding — is claimed or made public until their reply is in writing. @chefjoeatroadhouse already exists as a personal account (display name "Joseph", bio "chef Joe at Roadhouse!", 0 posts, 0 followers) and stays empty and unpromoted until then; whether it is set to private is UNVERIFIED — it was readable logged out on 21 Sept.

(These asks are numbered RH-n. "R5" elsewhere in this pack means Joe's ruling R5 — the alcohol rule — not RH-5.)

2.4 Open questions for Joe

Each is a one-line answer. Each blocks named work that is otherwise sitting still.

1. Hours of record. Sun 11–7 / Mon 2–8:30 (the site's JSON-LD and menu-data), Sun 11–7 / Mon–Wed 12–5 (your 21 Sept one-pager), or Sun 10:30–7 (the printed coupon, the Roadhouse graphic and index.html:549, which prints 10:30am–7pm on the live site today — so the site already contradicts its own JSON-LD)? And is Sunday open 11:00 or 10:30? — Blocks: hours in all seven site places, the GBP, the Facebook Page, Clover, the courtyard page's Chef Joe row, and /api/order, which refuses Tue/Wed orders today. Until answered, no clock hour goes on any surface and the GBP and Facebook Page ship with the hours field empty.
2. Primary domain. Confirm chefjoeatroadhouse.com as primary — name, handle and URL one string — with chefjoesroadhouse.com (printed 9×), chefjoedelta.com, chefjoecolorado.com and joesdeltaroadhouse.com all 301'd to it. joesdeltaroadhouse.com reads as the partner's mark plus a possessive, so it is a redirect and never the brand home. — Blocks: the domain bind (which also waits on RH-1 and RH-3 in writing), the DNSSEC disable at Squarespace, the sheet re-render, and lifting noindex.
3. Spiked Shake and the drinks note. Do both come off the site, menu-data, the order allowlist and the next sheet render now, per R5? And does the drinks note become "Fountain soda is available from Delta Roadhouse" or disappear entirely — it may not say "tavern", "bar" or "draft". — Blocks: the 22–23 Sep site pass and the sheet re-render; both are live R5 violations until it ships.
4. "Built by Vivere" footers. Two decisions, not one. (a) Replace on index, /book/ and privacy with the interim "Delta, Colorado" in the 22–23 Sep pass, so the word Vivere is off the consumer surface immediately — yes or no? (b) Does the line later become "A To Live CO venture · Delta, Colorado", with "Vivere Colorado LLC" kept only on a /legal page, on B2B paper and in Organization.legalName? That second half cannot ship until A1 and A5 clear. — Blocks: (a) the same site pass; the word Vivere is on a consumer surface until it ships. (b) the October To Live CO publication.
5. Bookings email. Create book@chefjoeatroadhouse.com on the new domain, with SPF, DKIM and DMARC set at Cloudflare — and who reads it? — Blocks: replacing "Email TBD" on /book/, the GBP contact field, and the Resend wiring that stops /api/quote leads sitting unread in KV.
6. (970) 209-8978. Mimi's own files record this as Naomi's personal number while one handoff lists it as a booking line. Confirm it appears on nothing — or tell me whose line it is and which brand it belongs to. — Blocks: nothing ships with it either way; today it is UNKNOWN-NEEDS-INPUT and banned from every surface. Answering it closes the only unresolved phone fact on the campus.
7. Who posts when you cannot. One operator who also cooks: name the person who posts the Story on a service day you are slammed, or accept that the floor is one Story per service day and nothing else. — Blocks: the entire October cadence (nothing is committed until this is answered) and the Sun 25 Oct count. This is the failure mode — not the reserved handles, but Chef Joe Instagram going dark for three weeks in October and reading as closed.
8. The umbrella name — deferred, answer when you are ready (section 6). "To Live CO" (capital CO), "ToLiveCO" or "To Live Co."? Handles are toliveco regardless — except on Facebook, where /toliveco is taken and the reservation goes to /tolivecolorado. And do you authorise the attorney spend for A1–A4 above? — Blocks nothing on the Chef Joe launch. Blocks only: the wordmark, the handle reservations going public, the footer line and the trade-name filing.
9. Delivery. The sheet says "Delivery Available / Call to arrange delivery" with no radius, fee, minimum or lead time. Real consumer offer, or phone-only? — Blocks: the GBP Delivery attribute (No today) and whether the site says anything at all.
10. Catering doors. Is direct off-site work still offered (weddings elsewhere, corporate drop-off), or is /book/ reduced to a router to the two hosts — Delta Roadhouse for their events, Mimi's for hers? — Blocks: the /book/ rebuild and the Nov–Dec holiday-party routing.
11. The Google account. Which single account owns the Chef Joe GBP, the YouTube Brand Account and, with Naomi, the Mimi's profile? — Blocks: the Thu 24 Sep GBP creation. Creating it from the wrong account is expensive to undo.
12. Courtyard accessibility. Is the courtyard wheelchair-accessible? — Blocks: one GBP attribute, currently marked "confirm first". Guessing it is a false claim on a public listing.

3. Mimi's Sweet Treats — the move

Mimi's is the only campus brand with history, followers, a review base and a working posting pipeline. It is moving, not expanding: 320 Main Street closes, 209 Ute Street opens Thursday 1 October 2026. Nothing is renamed. No handle is abandoned. "Mimi's at Roadhouse" is a location line on a page, never a second brand, a second account, a second domain or a second Google listing.

3.1 Already shipped tonight — DONE, do not redo

These landed on 21 Sept, were deployed to production and verified on the unique deploy URL and on www.mimissweettreats.com. The repo's 51 previously unpushed commits are now pushed to GitHub. (CONFIRMED)

The alcohol removal is not cosmetic. The liquor licence belongs to Delta Roadhouse (TW and Miles). Nothing on a Mimi's surface may sell, picture, name or imply alcohol — including a platform category name. Mimi's TikTok category is Food & Beverage, never Restaurants & Bars, and the word "tavern" is never used by us; say "live music & arcade". (Ruling R5)

The alcohol sweep is not finished. Commit 6dd0e1a touched roadhouse.html only. Two surfaces are still live and still in breach — roadhouse.html:1091 uses the banned word "tavern", and local-guide.html carries a whole "Craft Beer Country" section with named breweries. Both are ready-now rows in 3.6. Do not treat R5 as closed until they ship.

3.2 What stays and what changes

Stays: the name, the LLC, the logo (assets/mainlogo.webp), every handle, the scheduler connections, the domain www.mimissweettreats.com, the phone (970) 874-3163, the contact email on file (address UNVERIFIED — read it off the site's contact page before entering it anywhere), and the Google listing itself.

Changes: the street address on every record (320 Main → 209 Ute), the bios (none currently exist on file for any Mimi's account — UNVERIFIED that the live accounts are blank, check each before pasting), the closure bar on the site, the third-party citations, and the cadence.

Address policy (R7): listings, schema and account address fields carry the true address, 209 Ute Street, Delta, CO 81416. Marketing captions may say "the courtyard at 215 Ute" for the campus as a whole. The bios still carry the street number rather than a vague "on Ute Street" — NAP consistency across Google, Facebook, Apple and Yelp is the whole point of the move fix, and a vague bio helps nothing.

Canonical NAP string — byte-identical in every structured field: address fields, listings, directory submissions and site JSON-LD (Google, Facebook, Instagram, Apple, Yelp). Not in character-limited bios, where the street abbreviates to "209 Ute St" and the city line may lose its ZIP; the business name and the phone number never change:

Mimi's Sweet Treats
209 Ute Street, Delta, CO 81416
(970) 874-3163

Phone rule (R6): (970) 874-3163 only. Delta Roadhouse's number never appears on a Mimi's surface. Chef Joe's (970) 462-2817 never appears on a Mimi's surface. (970) 209-8978 turns up in one handoff as a booking line but Mimi's own files suggest it is Naomi's personal number — UNKNOWN-NEEDS-INPUT, put it on nothing.

Tracked, not a consumer surface: _docs/wholesale-program/cold-quality-products/index.html:837 carries Chef Joe's (970) 462-2817 on a Mimi's-branded wholesale document. It is B2B paper and Joseph Sutliff signs it as Chief of Operations, so it is defensible — but log it here so it is not discovered later as an R6 breach.

Hours: no clock hours go on any Mimi's surface. The site itself says new hours will be posted before opening; the 209 Ute hours have never been set. UNKNOWN-NEEDS-INPUT (Naomi). Do not carry the old Main Street hours forward — they are wrong for the new building and they are currently live on Yelp.

3.3 Handles — keep every one

No renames. A username change costs a platform-imposed lock-out period on both Instagram and TikTok (duration UNVERIFIED — check each app's own warning), a printed QR code, every site link (22 confirmed for the TikTok handle alone) and a scheduler re-auth; a prettier string is the benefit. It is not close. The prettier strings are also mostly gone: @mimissweettreats on Instagram belongs to a London wedding-cake business (574 followers) and @mimissweettreats on YouTube belongs to a stranger (browser-checked logged out, 21 Sept — SOURCED).

Facebook — the "ID mismatch" is not a mismatch. A 301 redirect confirms Page id 377584465431192 and profile.php?id=61562002972726 are the same Page (CONFIRMED, 21 Sept). There is nothing to resolve. The only Facebook identity task left is setting a vanity username so the site stops linking a raw numeric URL. facebook.com/mimissweettreats availability is UNVERIFIED — Facebook returns the same "content isn't available" for free and restricted names when logged out. Joe checks it in the Page's own username field, which tells the truth.

TikTok — the dotted account. The site links are already fixed, so nothing is bleeding. No file proves the dotted account exists at all, so this is conditional: Joe tries the login once. If it does not exist, or is not his, there is nothing to do. If it exists with fewer followers, set its bio to "Moved → @mimis.sweettreats320", stop posting, leave it up 90 days. If it somehow has materially more followers, reconnect the scheduler to it and record the new id — followers are the asset, the connection is a ten-minute job.

3.4 Per-platform: bio, link, address, hours

Every bio below is written to be true on the day it is pasted and to survive 1 October with one small edit. None contains hours. None contains a price, a flavour or a date that is not already published on the site.

Instagram — @_mimis_est2024

Display name, exactly, with nothing appended: Mimi's Sweet Treats (19 of 30 characters). No city suffix — the NAP name has to be byte-identical on every surface, and the city already sits in the bio and the address field.

Interim bio, now through 30 Sept — 124 / 150:

Homemade ice cream, milkshakes & sweet treats · Delta, CO
Reopening Thu 1 Oct — 209 Ute St, in the arcade at Delta Roadhouse

Durable bio, paste on 1 Oct — 127 / 150:

Homemade ice cream, milkshakes & sweet treats · Delta, CO
209 Ute St · in the arcade at Delta Roadhouse
Parties: (970) 874-3163

• Link: https://www.mimissweettreats.com/links.html — the file exists in both the repo root and dist/, and its map query already reads query=Mimi%27s+Sweet+Treats+209+Ute+Street+Delta+CO (verified on disk, 21 Sept). What is still UNVERIFIED is whether it resolves in production; load the URL after the next deploy. If it 404s, point the bio at https://www.mimissweettreats.com/ until it does.
• Category: Ice Cream Shop.
• Address field: 209 Ute Street, Delta, CO 81416 — set it the same day the Google address changes, not before.
• Hours: leave empty. The "Hours" story highlight is the only place hours will ever appear, and it stays empty until Naomi sets them.
• Highlights: THE MOVE (build-out + reopening card) · MENU · PARTIES (links parties.html, phone 874-3163) · THE COURTYARD (Chef Joe across the courtyard). Retire any "second location" framing — it is a move.
• Pinned: the reopening announcement — date and address, no hours. Replace on 1 Oct with "We're open at 209 Ute".
• Hashtags: exactly five — #mimissweettreats #deltacolorado #icecream + two topical. The duplicated #icecream in the 17 Sept caption looks like a bug in social_card_v3.py rather than a style choice — UNVERIFIED, open the file before changing anything.
• Tagging: @chefjoeatroadhouse (Joe already owns it, created 21 Sept) and @delta_roadhouse on courtyard posts. Accept a Collab from either.

Facebook — Page 377584465431192

Page bio (short field) — 85 characters; field limit UNVERIFIED (Facebook shows the counter in the field — the checked limit for the longer short-description field is 255):

Homemade ice cream, milkshakes & sweet treats · 209 Ute St, Delta CO · (970) 874-3163

About / intro — 198 / 255:

Homemade ice cream, milkshakes and sweet treats in Delta, Colorado. Closed while we move — reopening Thursday, October 1 at 209 Ute Street, in the arcade at Delta Roadhouse. Parties: (970) 874-3163.

• Link: https://www.mimissweettreats.com/ (UTM optional; it does not affect search).
• Category: Ice Cream Shop primary, Dessert Shop secondary. Never Bar, never Restaurant.
• Address: edit the existing Page to 209 Ute Street on 1 Oct. Do not create a "Mimi's at Roadhouse" Page and do not create a location Page under Delta Roadhouse.
• Hours: leave "No hours available". Enter them in the same sitting as Google and the site JSON-LD, once Naomi sets them.
• Closure status: use a pinned post, not Facebook's temporary-closure flag. The flag is not a citation Google reads, so it buys nothing a pinned post does not.
• Admins: Naomi and Joe, both full control, both on 2FA. It is her company too.
• Pinned: the move announcement with the date and the address.
• Event: "Reopening day — Thursday 1 October", venue set to Mimi's own address, not to the Delta Roadhouse Page.

TikTok — @mimis.sweettreats320

Interim bio — 72 / 80:

Homemade ice cream & milkshakes · Delta CO · reopening 1 Oct, 209 Ute St

Durable bio, paste on 1 Oct — 75 / 80:

Homemade ice cream & milkshakes · Delta, CO · 209 Ute St at Delta Roadhouse

• Link: links.html once it is confirmed live, otherwise the homepage.
• Category: Business → Food & Beverage. Never Restaurants & Bars (R5 — the ban reaches inside a platform's category names).
• Address / phone: off. City only.
• Pin: the move video once it exists; nothing new is required before then.
• Do not post the rendered September captions. TikTok posts cannot be edited, and they sign 320 Main Street. (Caption count and the exact wording are UNVERIFIED after tonight's two commits — open the render folder before touching any of them.)

YouTube — @mimissweettreatsco

Channel description — 290 / 1000:

Mimi's Sweet Treats — homemade ice cream, milkshakes and sweet treats in Delta, Colorado, family-owned and run by Naomi and Joseph Sutliff. Reopening Thursday, October 1 at 209 Ute Street, in the arcade at Delta Roadhouse. Parties and large orders: (970) 874-3163 · www.mimissweettreats.com

• Rename the channel to "Mimi's Sweet Treats" (drop "Joseph Sutliff"). Set the four personal playlists — Aloha vibes only, Download, Cooking good vibes, Favorites — to private.
• Add the channel URL to the JSON-LD sameAs on index.html and roadhouse.html. It is missing today.
• Zero cadence. Shorts only when a Reel already exists.

Threads

Auto-created with the Instagram account and cannot be checked logged out. Mirror the Instagram interim bio now; swap to the durable bio on 1 Oct in the same sitting as Instagram. Post nothing, revisit if it ever earns attention. (The durable bio states 209 Ute as the current address — pasting it today would publish the new location nine days before the shop is in it.)

Website — www.mimissweettreats.com

Meta description, now through 30 Sept — 140 characters:

Homemade ice cream, milkshakes and sweet treats in Delta, Colorado. Reopening October 1 at 209 Ute Street, in the arcade at Delta Roadhouse.

Meta description, from 1 Oct — 117 characters:

Homemade ice cream, milkshakes and sweet treats at 209 Ute Street, in the arcade at Delta Roadhouse, Delta, Colorado.

(The familiar "160 characters" is an SEO convention, not a platform-enforced limit — Google truncates on pixel width. Do not treat it as a hard ceiling.)

• Canonical: keep the www form everywhere. The canonical tag already says www; the caption footer string and _README print the bare form. Fix those two, 301 bare → www, and every citation then matches one string.
• Schema @type: change index.html from Restaurant to IceCreamShop. The Google primary category is Ice cream shop and roadhouse.html already says IceCreamShop — one type across the site and the listing is the fix, and deferring it just leaves the contradiction live.
• openingHoursSpecification: absent today. Add it on 1 Oct, when hours exist. Not before.
• Deploy path: deploy-staging.ps1 → Naomi/Joe review → deploy-prod.ps1, production branch production. Verify on the unique deploy URL first; the alias lags. A build-dist.ps1 step is referenced in older notes but is UNVERIFIED — confirm the script exists before relying on it.

3.5 Google Business Profile — move the listing, do not rebuild it

If the listing exists, its review history is the brand's single biggest asset — a new listing at 209 Ute starts at zero reviews. Star rating and review count: UNKNOWN-NEEDS-INPUT (read them off the profile in step 1). Use Google's address-change (move) flow on the existing profile — reviews, photos and listing age all travel with it. Never create a second Mimi's profile, and never mark the existing one "Permanently closed"; that is the one flag that kills it.

Sequence:

1. Verify the listing exists first. No file read tonight proves it does. Search Maps for "Mimi's Sweet Treats Delta", check whether it is claimed and by whom, and write down the rating and review count. UNVERIFIED. If no listing exists, create exactly one at 209 Ute on 1 Oct, video-verify, and accept that reviews start at zero.
2. Now through 30 Sept: mark it Temporarily closed. It reduces prominence while it is set, but it is true, it is reversible, and the alternative is a listing showing a shop that is not there. "Permanently closed" is the fatal one; "Temporarily closed" is not.
3. On or just before 1 Oct: change the address to 209 Ute Street, Delta, CO 81416, with the reason given as a move. Drop the map pin on the arcade door, not the Roadhouse entrance.
4. Re-verification: Google will re-verify, usually by video, and it usually wants visible signage reading Mimi's Sweet Treats, distinct from the Roadhouse's. Do the call with Naomi present for the code, and after the Mimi's sign is up at the arcade counter.
5. Reopen the listing on 1 Oct and rewrite the description to drop the closure sentence.

Ownership: Naomi is CEO and 50/50 owner, so the profile is managed from her Google account with Joe as manager, unless she agrees in writing to Joe's account. Managing it from the same account as Chef Joe's profile would be more convenient; convenience does not outrank a co-owner's control of her own listing.

Fields: - Name: Mimi's Sweet Treats — matches the sign and the LLC. Never "Mimi's at Roadhouse", never a keyword-stuffed variant. - Category: Ice cream shop (primary), Dessert shop (secondary). Deliberately distinct from Chef Joe (food truck) and Delta Roadhouse (bar / music venue) — that distinctness is what stops Google treating three businesses at one address as duplicates. - Attributes: Serves alcohol = No. This is the protective setting, not a mention — leaving it unset lets Google infer from the co-located licensed premises. After the move, check the live listing and confirm Google is not surfacing it as a visible public attribute on the profile; if it is displayed, unset it. No bar attributes, ever, whatever the licence covers on the premises. - Hours: empty until Naomi sets them. Never re-enter the Main Street hours. - Photos: the logo; the 209 Ute counter and signage once they exist. The current GBP menu photos still show 320 Main and need replacing. - Posts: one Update per week — the same post as Instagram, pasted. No automation. Do not post "Wednesday Family Fun Night" until Naomi confirms the programme continues at 209 Ute.

Description — 394 / 750:

Homemade ice cream, milkshakes and sweet treats in Delta, Colorado — family-owned and run by Naomi and Joseph Sutliff.

Closed while we move. Reopening Thursday, October 1 at 209 Ute Street, Delta, in the arcade at Delta Roadhouse — across the courtyard from Chef Joe at Roadhouse. New hours will be posted before we open.

Birthday parties, celebrations and large orders — call (970) 874-3163.

3.6 The remaining fixes

Not a fix, so you are not surprised by a grep hit: roadhouse.html:986 ("320 Main Street, Delta — where it all started") and gallery.html:296 ("Happy scoops at 320 Main Street") still print the old address, but both are past-tense and historical. They are consistent with the rule that Main Street is no longer framed as an open counter. Leave them.

Cadence from 1 Oct. The daily flavour-board automation is dead: the posting queue was empty on 21 Sept and the scheduled task is gone. Do not resurrect a daily promise — one operator who also cooks cannot keep it, and the plan files already lied once about this channel being healthy. The floor is one feed post per week (Instagram, mirrored to Facebook, pasted as the Google Update), shot at the counter on the same Sunday Joe shoots Chef Joe. Stories on days Joe is at the courtyard anyway. TikTok 0–1 per week, reusing the Reel. YouTube zero. Reopening week only: three posts — moving day, first scoop, and the courtyard post with Chef Joe. Then count monthly and set next month's plan at the lowest number actually shipped in the last four weeks, never higher. A floor that holds beats a ceiling that collapses.

3.7 Naomi's sign-off

Joe has say over marketing and social, and Naomi is aligned with him — but Mimi's Sweet Treats LLC is a separate 50/50 entity with Naomi as CEO, and Vivere Colorado LLC is not "behind" it. That distinction is binding in two directions:

• On any future umbrella brand (deferred, section 6). Mimi's may not be named in a To Live CO bio, on the To Live CO site, or in any "the people behind…" line until Naomi agrees in writing. Ship those surfaces without Mimi's until that lands.
• On Mimi's own surfaces. Joe executes; Naomi approves before anything is saved. Her explicit sign-offs: the bio text on each platform, the address change on the Google listing (and she is present for the re-verification code), the hours whenever she sets them, any new price or flavour before it is posted, whether Wednesday Family Fun Night continues at 209 Ute, and the brand art — she owns the mark, so the logo is not restyled.

Facebook admin and Google ownership follow the same logic: both accounts carry Naomi at full control, and the Google profile sits in her account with Joe as manager unless she writes otherwise. This is not ceremony. It is the one campus brand Joe does not own outright, and the reviews, the followers and the name are hers as much as his.

4. Catering and events

Under ruling R4 there is no catering brand. Delta Roadhouse is the owner/host that uses Chef Joe for catering during their events; Mimi's uses Chef Joe for its parties. So catering is a service line of Chef Joe — a page and a phone call — never an account, never a listing, never a second domain.

All three architects agreed on that shape. Where they differed, the choices are called out inline.

4.1 Where the funnel lives

Which URL /book/ sits on is decided in the domain section, not here. Today the page is live at chef-joes-roadhouse-trailer.pages.dev/book/. joesdeltaroadhouse.com is a redirect only, never the brand home. Two architects wrote chefjoeatroadhouse.com/book/ as if it were bound — it is not; that domain is available and unregistered as of 21 Sept. Print nothing with a domain on it until the domain is actually registered and bound.

Catering has no cadence of its own. It is a content pillar on the Chef Joe accounts, not a feed: one post per catered event after it happens, plus an EVENTS highlight. If no event happens, nothing posts and nothing looks abandoned, because nothing promised a feed. No catering post ever shows a bar, a glass, or a price.

Retire the internal lockup "Joe's Catering at Roadhouse" from partnership.json, pricing.json, share.json and the engine's menu.json _meta.brand. It is a name for a business that the ruling says does not exist, and it carries the wrong possessive spelling (R5). The same _meta.brand object also holds "trading_name": "Chef Joe's" and "courtyard_lockup": "Chef Joe's at Roadhouse" — both carry the possessive R5 bans. Retire all three strings in the same pass.

4.2 What must change on the /book/ page

The page today sells Chef Joe as an independent Western Slope caterer with a Mimi's dessert bar. That contradicts R4. Rebuild the top of the page as three doors, then keep the quote form behind the third door only.

I take the "router" framing from architects 1 and 2 over architect 0's "reframed storefront": a storefront still reads as hire this caterer, and the ruling says two of the three routes are the venue's booking, not Joe's.

The "Built by Vivere" string is identical at site/index.html:632; it comes off there in the same pass. Grep every Chef Joe and Mimi's deploy for /Vivere/ before publish.

Add as the first field of the form: "Where is the event?" → At Delta Roadhouse / At Mimi's / Another venue. The first two route to the partner pages instead of submitting. This stops a Roadhouse booking landing in Joe's KV where the Roadhouse never sees it.

Keep: the quote form and the commissary sentence. CHANGE the campus disclaimer — strike the sentence "All bar service is provided by Delta Roadhouse under Delta Roadhouse's liquor licence." (live at site/book/index.html:207). The disclaimer paragraph becomes, in full: "215 & 209 Ute Street, Delta, Colorado. Chef Joe at Roadhouse and Mimi's at Roadhouse are independent businesses operating at Delta Roadhouse." Do not soften it, do not move it to a tooltip — delete the sentence. The same footer block is shared with site/index.html; strike it there too. (R5: nothing on a Chef Joe surface may sell, name or imply alcohol — that sentence names bar service and the liquor licence, which §4.7 already orders removed.)

Router copy for the top of the page:

• Hosting at Delta Roadhouse? Book the room with Delta Roadhouse — they host, we cook. → link to their events page. (Their number is on their page. Not here.)
• A party at Mimi's? HOLD — UNKNOWN-NEEDS-INPUT. No Mimi's door, no "Ask Mimi's" card, no Mimi's mention of any kind ships on a Chef Joe surface until Naomi agrees in writing (§4.4). Until then /book/ has two doors: Delta Roadhouse, and a phone call.
• Somewhere else? Call (970) 462-2817.

Meta description for /book/ — 151 / 160:

Events at Delta Roadhouse are catered by Chef Joe. Book the room through Delta Roadhouse and ask for Chef Joe food. Anything else, call (970) 462-2817.

Page title — 42 / 60:

Events — Chef Joe at Roadhouse | Delta, CO

GBP "Caterer" service description on the single Chef Joe profile — 185 / 300 (GBP service-item cap, 300; not the 750-character GBP business description limit quoted elsewhere in this report):

Chef Joe cooks for events hosted at Delta Roadhouse. Book with Delta Roadhouse and ask for Chef Joe food. Cooked on site, served hot. Rates by quote. Anything else, call (970) 462-2817.

The Mimi's clause, any off-site or service-area clause, and any wording implying the venue sells the food as one bundled package are all HELD — see §4.3 (who invoices, UNKNOWN-NEEDS-INPUT), §4.4 (Naomi sign-off, UNKNOWN-NEEDS-INPUT) and §4.5 (whether Joe takes off-site work at all, UNKNOWN-NEEDS-INPUT). Do not paste any of them into GBP until they are ruled.

Strike list for the word bar on /book/ — exact strings, not a preference:

• <h3>Dessert Bar</h3> → <h3>Dessert Table</h3>
• <li>Sundae bar or plated</li> → <li>Sundae table or plated</li>
• <option>Dessert bar only</option> → <option>Dessert table only</option>

(site/book/index.html lines 115, 117, 157.) If the Mimi's hold above removes the dessert card, the first two go with it — but the form option is outside the card and comes off either way.

4.3 How a Roadhouse-hosted booking arrives, and who invoices

1. Guest wants an event at Delta Roadhouse.
2. They land on the Roadhouse's own private-events page (roadhouse-private-events.pages.dev today — it already says the food comes from Chef Joe). That page is the booking form, not /book/.
3. The enquiry posts to /api/event-inquiry and is stored in the ROADHOUSE_LEADS KV.
4. It probably notifies nobody — ASSUMPTION, verify before quoting it. There is no .dev.vars in _campus-roadhouse/private-events/, but Cloudflare dashboard secrets would not appear on disk either, so "RESEND_API_KEY, NOTIFY_FROM and NOTIFY_TO are unset" cannot be proved from the repo. The page ships its own health endpoint (functions/api/health.js:36 reports email: !!(RESEND_API_KEY && NOTIFY_FROM && NOTIFY_TO)) — hit /api/health once and cite the result. If it is false, set NOTIFY_TO to a Roadhouse staff inbox and Joe.
5. The Roadhouse confirms the room, then books Chef Joe for the food.

Fixes owed on that page (Vivere drafts, TW and Miles publish — it is their surface):

• NOTIFY_TO = a Roadhouse events inbox plus Joe. UNKNOWN-NEEDS-INPUT: what that Roadhouse inbox address is.
• NOTIFY_FROM needs a Roadhouse-domain sender and therefore their DNS. UNKNOWN-NEEDS-INPUT.
• sutliffjoe@gmail.com is currently shown as the public email on their page (index.html lines 800 and 802, English and the data-es Spanish string). It comes off — it is Joe's personal Gmail on a partner's public surface.
• "Built by Vivere Web" comes off too (same two lines, both languages — the Spanish data-es attribute repeats it as "Hecho por … Vivere Web"). R1: the word Vivere never appears on a consumer surface, and Vivere Web is the separate B2B agency — a credit link from a campus consumer page is exactly the cross-link R1 forbids. Replace with an unlinked credit or nothing.
• The footer links the dead chef-joes-roadhouse.pages.dev (index.html:797). Point it at the live Chef Joe host.
• "Chef Joe's" → "Chef Joe" on that site and in catalog.json (R5).

Who invoices the client at a Roadhouse-hosted event: UNKNOWN-NEEDS-INPUT. No source settles it. The two candidates are (a) the Roadhouse invoices the client for the whole event and pays Chef Joe as a supplier, or (b) the Roadhouse invoices the room and Chef Joe invoices the food separately. This must be settled in writing before the catering term sheet is signed, because it decides whose name is on the customer's receipt, who carries the deposit, and who eats a cancellation. Do not print a booking flow that implies either answer until Joe and the partners agree.

4.4 How a Mimi's party booking arrives

1. Guest books through Mimi's own parties page, by (970) 874-3163 or mimis.josephsutliff@gmail.com.
2. Naomi books the party. Chef Joe food is a line item on the Mimi's booking, not a separate contract.
3. Naomi passes Joe the headcount and the date.

One line may be added to Mimi's parties page — "Food by Chef Joe at Roadhouse by arrangement" — only after Naomi agrees. She is 50/50 owner of a separate LLC; her page is not Joe's to annotate unilaterally. Status: UNKNOWN-NEEDS-INPUT. The same sign-off gates every Mimi's mention on a Chef Joe surface (§4.2).

4.5 The third door, and whether it stays

Anything that is neither a Roadhouse event nor a Mimi's party — an off-site wedding, a corporate drop-off — goes to /book/ → /api/quote → ORDERS KV. No email is sent today (functions/api/quote.js stores to KV and sends nothing). Until a mail provider and a bookings inbox exist, Joe reads the KV after every service day and replies by phone from (970) 462-2817. That is a stopgap, not the system — an unnotified manual chore for a cook, so put a date on it: wire a notification to Joe the day credentials exist, and if it is still manual by then, it is a blocker, not a habit.

Whether Joe still takes independent off-site work at all is Joe's call — UNKNOWN-NEEDS-INPUT. R4 frames catering as Roadhouse-hosted and Mimi's-hosted. Until he rules otherwise, keep door three as a phone call, not a marketed offer: no service-area page, no "serving the Western Slope" line, no territory claims.

There is no bookings email address yet. book@ on the Chef Joe domain waits on the domain being registered and on SPF/DKIM/DMARC. Do not print an email address that does not receive mail.

4.6 Phone separation — each venue's number on its own page only

Binding (R6, and a judge must-fix that overrides architect 0, who wanted the Roadhouse number shown inside a block on /book/).

The rule is never mix them on one page. A Chef Joe page routes a Roadhouse booking by linking to the Roadhouse's page, where their number already lives. Printing their number on /book/ breaks A2P 10DLC separation and contaminates both businesses' NAP for local search.

(970) 209-8978 stays off every surface: one handoff calls it a booking line, Mimi's own files suggest it is Naomi's personal number, and the Chef Joe print scripts already ban it. UNKNOWN-NEEDS-INPUT until Joe or Naomi confirms — and it goes nowhere in the meantime.

4.7 The alcohol rule — what comes off the page and the term sheet

R5: nothing on a Chef Joe or Mimi's surface may sell, picture, name or imply alcohol. Delta Roadhouse holds the liquor licence; TW and Miles own it; it is theirs alone.

Off /book/:

• "Plan the space, bar and theme too" — struck.
• The campus-disclaimer sentence "All bar service is provided by Delta Roadhouse under Delta Roadhouse's liquor licence." (site/book/index.html:207, and the shared block on site/index.html) — struck. Replacement paragraph in §4.2.
• Any photo showing a bar, a tap, a bottle or a glass.
• Any mention of bar service, drink packages, or a hosted bar in an event description — even as the Roadhouse's, on a Chef Joe page. Their page says it; ours does not.
• The three bar strings in the strike list at the end of §4.2 — Dessert Bar, Sundae bar or plated, Dessert bar only — so the word does not appear at all.

Off the unsigned catering_215 term sheet, before signature:

• The "Bacardi milkshake" package line (menu.json → terms.catering_215.packages: vivere_price $7, added ingredients $4, menu price $13) — ASSUMPTION, Joe's call, not an R5 requirement. R5 governs Chef Joe and Mimi's consumer surfaces; an unsigned B2B term sheet is not one, and the sheet already records the lawful shape: "Alcohol-infused items are prepared by Vivere, then finished and served by Roadhouse tavern staff." What R5 does bind: no alcohol item may ever surface on a Chef Joe or Mimi's page, menu, post or listing. Whether to keep or drop the line in the deal is a Joe-and-attorney decision — UNKNOWN-NEEDS-INPUT. (Term sheet status on disk: "unsigned term sheet, seven slides, still in negotiation".)
• The supplier line must read Vivere Colorado LLC. That is correct and stays: it is B2B paper, not a consumer surface (R1). Every consumer-facing string on the same job says Chef Joe.
• Any alcohol offer that survives anywhere carries only the Roadhouse's marks, on the Roadhouse's own surfaces. The football coupon's free-beer offer never appears on a Joe-owned page.

Say "live music & arcade", never "tavern" (R5) — including when describing the venue in an event write-up.

4.8 Asks to TW and Miles (catering-related)

These are the catering items from the written ask list. They need answers on paper, not in conversation.

1. Consent to use "Roadhouse" in a Chef Joe handle and domain.
2. Their real Facebook Page URL (it is not /deltaroadhouse) — UNKNOWN.
3. Once the Chef Joe Facebook Page exists (it does not yet — /chefjoeatroadhouse is only LIKELY FREE, UNVERIFIED), add it as co-host on Roadhouse Facebook Events where Joe cooks. Roadhouse-hosted events are their events; Chef Joe is a co-host they add, never the creator.
4. Written OK to use the Roadhouse name and event photos in a Chef Joe catering post, and their tagging preference.
5. NOTIFY_TO inbox and NOTIFY_FROM DNS for the private-events form; sutliffjoe@gmail.com and the "Built by Vivere Web" credit off that page; footer link fixed.
6. Who invoices the client at a Roadhouse-hosted event (§4.3).
7. Confirmation that GBP entries stay distinct — no shared category/phone/address between the Roadhouse listing and the Chef Joe listing.
8. Any alcohol offer tied to an event carries only their marks, on their surfaces.

5. The courtyard page, and what we ask of Delta Roadhouse

5.1 Why this page exists at all

Three businesses share one courtyard and a customer only ever asks one question: is anything open right now? Today that question has no answer anywhere. The Chef Joe site knows its own hours, the Mimi's site knows its own, and the Roadhouse's events live on Eventbrite. One operator cannot keep three sites in sync by hand, so the answer has to live on one page fed by one file.

It cannot live on any of the three brand sites. Not the Chef Joe site (it would list Mimi's and the Roadhouse), not the Mimi's site (a separate LLC, and Naomi runs it), not the Roadhouse's (theirs, and we cannot publish to it). A neutral fourth page is the only one that can name all three without one appearing to own the others.

5.2 The URL

Decision — one line on why. Architect 3 proposed a fourth domain family, 215ute.com, for this page. Judges marked that MUSTFIX in two lenses: a one-page shared surface does not justify a fourth domain to renew, redirect and defend, and 215ute.com is UNCHECKED anyway. Build on the interim Pages URL now and decide the final home later — the page has to prove it gets updated before it earns a printed address, and the umbrella that would have hosted it is deferred.

Not offered to the Roadhouse as deltaroadhouse.com/courtyard. Architect 2 floated handing them the page to publish. Rejected: the point of the page is that it updates the same evening Joe changes a service day, and a page on their domain updates when they get to it. If TW and Miles want their own copy later, they get the static file — Joe's copy stays canonical.

5.3 What the page shows

One screen, phone-first, the answer above the fold and no scroll needed to get it.

Line 1 — the place, not the brand.

The courtyard at Delta Roadhouse · 215 Ute Street, Delta, Colorado

Today's date, computed client-side, so a stale cache is visible as stale.

Three rows, in this order:

No Roadhouse phone on this page. Architect 2 wanted all three numbers, each labelled. Judges marked the Roadhouse number MUSTFIX on two lenses and the graft is explicit: no coupon, no alcohol words, no Roadhouse phone on that page. Their number lives on Roadhouse surfaces only — we do not restate it here, because it appears nowhere in the repo and is UNVERIFIED. We link to their page and let it carry their number. This also keeps the A2P 10DLC separation clean.

One event line, below the rows: the next dated courtyard happening, from courtyard.json. First entry, stated as an event and nothing more:

Sun 27 Sept — open late for the game

Type only — no team names, no team logo, wordmark or colourway, no offer, no price, no alcohol word. The 21 Sept order-ahead sheet prints the matchup by name (SOURCED: _print/menu-onepager-2026-09-21/...); this page does not carry it, because those are a third party's club marks on a page Joe owns. The line is deleted from courtyard.json after 27 Sept.

Footer:

Chef Joe at Roadhouse (215 Ute Street) and Mimi's Sweet Treats (209 Ute Street from 1 October 2026, in the arcade at Delta Roadhouse) are independent businesses. Delta Roadhouse is a separate business and the host of this courtyard. Delta, Colorado.

Not on the page, ever: prices; menu items beyond the one-line descriptor per row; clock hours until Joe rules (see 5.6); the word Vivere; any alcohol word, image, offer or coupon.

5.4 The data file

Everything the page renders comes from one file, courtyard.json, edited by one person in one place. All three architects proposed this and every judge lens grafted it — it is the single most load-bearing decision in this section, because the alternative is one operator hand-editing three pages on a Sunday night after service.

courtyard.json
├─ businesses[]
│   ├─ name, descriptor, url, phone
│   └─ standing{}          weekday → open/closed (+ hours, once Joe rules)
├─ exceptions[]            date → override + a short reason string
└─ next_event{}            date, title  (one entry, hand-typed)

Rules on the file:

• Naomi's written OK gates the Mimi's row itself, not just the links to it. Mimi's Sweet Treats LLC is a separate entity and Naomi is CEO and 50/50 owner. Before the page ships with a Mimi's row, get her yes in writing on: the descriptor wording, the use of (970) 874-3163 on a page Joe owns, the link target, the Pacifico/red-gold treatment of her mark in 5.5, and the footer sentence naming her business. Append it to DECISIONS.md with the date. Until it lands, the page ships with the Chef Joe row and the Roadhouse name only.
• The Chef Joe standing block is generated from the server-side STANDING table (site/functions/api/_denver.js) — the one the order API actually reads: site/functions/api/order.js imports dayKey, todayStatus from ./_denver.js. The courtyard page can then never say OPEN while the order API refuses the order. It is explicitly not generated from site/assets/js/schedule.js: that is a client-side first-paint copy whose own comment records that the two drifted on 17 Sept, and it uses a different vocabulary (on / off / avail against the server's open / closed / arranged). Generating from the client copy would reproduce the drift rather than remove it — and rebuild that bug on a third surface.
• The Chef Joe url value is the live Pages URL, typed in full — https://chef-joes-roadhouse-trailer.pages.dev. Do not rely on the site's own canonical: its canonical, og:url, og:image and JSON-LD url all point at joesdeltaroadhouse.com, which is a Squarespace "Coming Soon" parking page, so an inherited link would carry the parking page into every share preview.
• Mimi's block is hand-edited and Naomi controls its contents. Her hours are not ours to compute.
• The Roadhouse block is a static string they approved in writing. Not scraped from their site, not inferred from Eventbrite — a string, with the date they approved it recorded beside it in the repo.
• Later, the Chef Joe site's week strip reads the same file, which retires a second copy of the hours. That is a week-2 follow-on, not a launch blocker.

5.5 The identity rule

The page presents the Roadhouse as the place, and never as our brand.

• The page is named for the address — "the courtyard at 215 Ute Street" — not for the Roadhouse. A Joe-owned URL carrying the partner's identity would need their written mark consent and would have to be unwound the day the trailer leaves. An address-named page needs neither.
• The Roadhouse is named as host in the first line. That is a factual statement of location, exactly as "at Roadhouse" is on the Chef Joe wordmark — location, never ownership.
• Three marks, three zones, never fused. Chef Joe in Anton on ink/ember; Mimi's in Pacifico on red/gold; Delta Roadhouse in their own lockup on navy/brass. Each in its own panel with its own type. No combined lockup, no "presented by", no pick emblem sitting beside the Chef Joe wordmark.
• The Roadhouse lockup appears only after written OK (ask 5.9-E). Until then the row is their name set in the page's neutral type.
• The page ground is neutral — ink with bone type — so no one brand's palette reads as the owner of the courtyard.
• No publisher line until the umbrella name clears its Colorado trade-name and USPTO checks (both UNKNOWN-NEEDS-INPUT — neither search could be completed on 21 Sept, and the foreign-equivalents question against Reg. 1,779,343 is an open attorney checkpoint). Printing the umbrella name as a publisher attribution is a use in commerce before clearance. Until it clears, the footer carries only the independent-businesses line in 5.3. The word Vivere appears on it in no case.

5.6 The wording and alcohol rules

Say "live music & arcade". Never "tavern". All three architects drafted a Roadhouse row at some point reading "live music, tavern & the arcade"; all three were marked MUSTFIX, on three separate judge lenses. The rule is simple and has no exception: the Roadhouse says tavern on their own surfaces; we say live music & arcade on ours. This page carries the Chef Joe and Mimi's names, so it is one of ours — and so is the order-ahead sheet, which breaks the rule today. _print/menu-onepager-2026-09-21/chef-joes-order-ahead-2026-09-21-PRESS.html prints, under Drinks, "Fountain soda, ice-cold draft and the full bar are poured in the tavern." and a row reading "Spiked Shake · Ask at the bar". Before the next run that block becomes: "Fountain soda · Milkshake 16 oz $9.75 · Bottled Water $2" — the draft/full-bar/tavern sentence and the Spiked Shake row come off entirely, and no replacement alcohol sentence goes on in their place (see the licence-attribution ruling below). No sheet already in a Delta business's hands is recalled; the correction lands on the reprint.

No alcohol offer appears on this page. Architect 3 proposed showing the current coupon, including the football coupon through 27 Sept. That coupon is a free-Lagerado offer — an alcohol promotion on a page that is not a licensee's. Marked MUSTFIX. Only Delta Roadhouse may publish it, on their surfaces, under their marks. The 27 Sept row on this page says the courtyard is open late for the game, and stops there.

The licence-attribution sentence is Joe's call — UNKNOWN-NEEDS-INPUT. Architect 2's footer included "All bar service is provided by Delta Roadhouse under Delta Roadhouse's liquor licence." A judge flagged the tension honestly: it is a correct legal attribution, and it is also the only alcohol sentence on a family-facing page. Default until Joe rules: leave it off, and carry only the independent-businesses line in 5.3. Nothing on the page mentions bar service, so nothing needs attributing.

noindex until every row has real hours. A page that tells Google "Chef Joe" and shows no hours, or wrong hours, competes with the profiles it is meant to support. The hours conflict is unresolved — the Chef Joe site says Sun 11:00–19:00 / Mon 14:00–20:30, the 21 Sept one-pager says Sunday 11am–7pm / Mon–Wed 12–5pm, and the printed coupon says Sundays 10:30am–7pm. Until Joe rules, the rows carry days and state only for the days the sources agree on — Sunday and Monday open — and Tuesday/Wednesday read "call to check" rather than open or closed, because the server STANDING table marks Tue/Wed closed while the 21 Sept one-pager sells Mon–Wed 12–5pm. The page stays noindex.

5.7 Page copy with hard limits

Two strings on this page have length targets. These are SERP truncation thresholds, not platform-enforced caps like a bio field — Google truncates on pixel width, not character count — but both strings sit well inside them either way. Everything else on the page is free-length body copy.

Page <title> — 56 / 60:

What's open today · the courtyard, 215 Ute Street, Delta

Meta description — 132 / 155:

Who is open today in the courtyard at 215 Ute Street, Delta, Colorado — Chef Joe at Roadhouse, Mimi's Sweet Treats, Delta Roadhouse.

The word is today, not "tonight", everywhere it appears: the interim project is courtyard-today.pages.dev, the Chef Joe footer slot reads "What's open today", and the Mimi's slot reads "What's open in the courtyard today". The only hours source Joe himself supplied puts the courtyard shut before evening on most trading days, so a page titled "tonight" would answer a question about a time when nothing is open — and "In the courtyard tonight" is the exact string the drifted schedule bug printed on a Thursday.

This section carries no social bios; the profile bios live in the Chef Joe, Mimi's and umbrella sections.

5.8 Where the page is linked from

("Campus strip" means a navigation strip of links. It is never called a bar on a Joe-owned surface.)

5.9 The written asks to TW and Miles

One email, one reply, in writing, before any further handle or domain containing "Roadhouse" is claimed. This is not a formality and it is not a contract negotiation — it is six sentences of confirmation that cost them nothing and protect both sides.

Why it must be in writing, and why now: the endorsement to use "Chef Joe at Roadhouse" is verbal. A verbal permission is fine to launch under and is not fine to spend against — not a wrap, not a print run, not a domain family, not a GBP name. Instagram @chefjoeatroadhouse already exists (created 21 Sept, Joe's, 0 posts, 0 followers, a personal account that is currently public — its display name "Joseph" and bio "chef Joe at Roadhouse!" were readable logged out on 21 Sept — and not connected to the scheduler). Set it to private today; it stays private and empty until the reply lands. That makes the email overdue rather than optional, and nothing further with "Roadhouse" in it is created before then.

Carried in the same email, since it is one reply either way:

• Name confirmation — "Chef Joe at Roadhouse", that spelling, no apostrophe-s.
• Their events inbox. The Roadhouse private-events form appears to have NOTIFY_TO unset, which would mean leads are landing nowhere — UNVERIFIED: that is a runtime environment-variable state and cannot be read from disk. Hit the project's own health endpoint (functions/api/health.js reports email: !!(RESEND_API_KEY && NOTIFY_FROM && NOTIFY_TO)) before this sentence goes into the email, and state it as fact only if the check confirms it. Either way: which inbox on their side, plus Joe — and sutliffjoe@gmail.com comes off their page.
• GBP distinctness. Ours will be a distinct entity, name, phone, category and website from theirs at the same street number. Their profile is not ours to police, but a heads-up costs nothing and a Google suspension deletes reviews.
• Clover "JOE'S MENU". It needs correcting before any ordering link goes on a profile. Who on their side can edit it.
• Alcohol offers carry only their marks. Going forward, any Roadhouse offer involving a drink is published by the Roadhouse under Roadhouse marks — no Chef Joe or Mimi's lockup on it.

The gate. No new handle, domain, Google Business Profile name, wrap or print run containing "Roadhouse" is claimed, registered or ordered until their reply is in writing and appended to DECISIONS.md with the date.

Three things already carry the word and are disclosed in the email rather than gated — they stand still rather than being unwound:

• the verbally endorsed trading name "Chef Joe at Roadhouse";
• the @chefjoeatroadhouse Instagram account, public today, set private and empty pending the reply;
• joesdeltaroadhouse.com, which the live Chef Joe site already publishes as its canonical, og:url, og:image and JSON-LD url.

Naming Delta Roadhouse as the host location on the courtyard page is a factual statement of address and is not gated. The courtyard page can be built in the meantime — it just ships with the Roadhouse row reduced to a name and a link until 5.9-E comes back.

6. Later — the umbrella brand

Deferred by Joe, 21 September. Vivere Colorado will launch on social at a later date under a different name, with To Live CO as the working candidate. Nothing in this section is on the Chef Joe launch path, and nothing here blocks it. It is kept because the availability checks, the name-neighbour findings and the trademark position were done on 21 September and will be stale if they have to be redone from scratch. Read it when that launch date is set.

Two things are worth doing now even though the launch is deferred, because both are cheap and reversible: reserving the handles so nobody else takes the string, and putting the trademark question to an attorney, since the answer takes longer than anything else here.

6.1 What it is

To Live CO is the public, consumer-facing expression of Vivere Colorado LLC (CO ID 20211734817, good standing, formed 10 Aug 2021). [CONFIRMED — Secretary of State, read 21 Sept 2026]

It exists for one reason: so that the word Vivere never has to appear on a consumer surface. Joe's ruling stands — Vivere appears only on B2B paper, contracts, invoices and a /legal page, because VIVERE Reg. 1,779,343 (restaurant services) is live, unowned by Joe, and was never cleared. [CONFIRMED — Joe's ruling R1]

To Live CO is an endorser, not a master brand. It signs the footer; it never signs the door. Concretely:

• It owns a name, a domain and reserved handles.
• It signs other people's work with one fixed line.
• It posts nothing, sells nothing, has no address, no phone, no hours, no menu, no sign, no Google Business Profile.
• It is the stamp future ventures and multi-brand events carry.

The role itself is settled: endorser, zero cadence. Nothing here is open.

Tagline: to live Colorado — the plain-English gloss already on disk at C:\Users\sutli\Desktop\Developer\Vivere Clients\Vivere Colorado Food Trailer\site\assets\css\site.css, line 3. [SOURCED] It is a tagline, not a name: it is set in sentence case, it is never a handle, and it never replaces "To Live CO" in a name field.

6.2 The endorsement line

The line is a fixed string. It is not rewritten per surface, not translated, not expanded, not turned into a sentence:

A To Live CO venture

Variants like "Brought to you by To Live CO", "To Live CO presents", "part of the To Live CO family" are not approved and should not be typed.

Where it goes / where it never goes

6.3 The naming grammar

Every venture, current and future, is named by the same formula:

[VENTURE NAME] + (optional) at [LOCATION] — with "A To Live CO venture" in back-matter.

To Live CO never enters the name field, the handle, or the wordmark.

This grammar is the written rule every future venture is checked against.

Worked examples

6.4 The future-venture test

Run any new idea through these five questions before a name is spoken publicly. Two worked cases below, deliberately chosen to break the "food at the Roadhouse" assumption.

1. Does it have its own name that stands alone without the umbrella?
2. Does the location slot apply — and if so, is that location ours to name?
3. Does it need its own phone? (If it will ever text a customer, yes — separate A2P 10DLC registration [R6].)
4. Does it need its own GBP? (Only if it has a door or serves customers at a verifiable address.)
5. Has the attorney checkpoint in 2.5 cleared, if anything is going to print?

Case A — a non-food venture. Say Joe starts a small screen-printing / merch operation in Delta.

• Name: Delta Press (illustrative placeholder, not a decision) — venture name stands alone. Location slot: empty, because it is not at the Roadhouse. No "at Roadhouse", no DR guitar-pick emblem (the partner's mark), no Roadhouse phone.
• Endorsement: A To Live CO venture on its site footer and its invoices. Same line, unchanged — that is the whole point of a fixed string.
• Handles: its own. It does not post from the umbrella and the umbrella does not post about it.
• Phone: its own number if it texts; never (970) 462-2817, which is Chef Joe's [R6].
• GBP: only if it has a door. If it runs out of Joe's garage, no listing.
• Type and colour: it may inherit Anton/Barlow and the campus palette, but it does not inherit Chef Joe's ember or the flame. [ASSUMPTION — a brand-art decision, not yet ruled]

Case B — a venture with no Roadhouse connection at all. Say a stall or pop-up at a Montrose or Grand Junction market.

• The at [LOCATION] slot is filled by its own location or dropped entirely. Nothing about the Roadhouse travels with it: not the name, not the pick emblem, not the address, not the partners' number, and nothing that could read as the Roadhouse's liquor-licensed venue operating off-site. [R5]
• The umbrella line still reads A To Live CO venture — it is location-independent, which is why it can carry Joe's work anywhere in the state without the word Vivere.
• If the venture is food and would be a second Chef Joe outlet, that is not a new venture; it is Chef Joe with a second location, and it goes under the existing Chef Joe brand, not a new name.

The test's failure mode: if a proposed venture only makes sense as "To Live CO does X", it has no name yet. Give it a name or do not launch it.

6.5 Name neighbours and the trademark position

This is an attorney checkpoint before anything prints — not a blocker on reserving a free handle or domain today. Reserving costs a few dollars and is reversible; printing 500 sheets is not.

Known neighbours [SOURCED — web search, 21 Sept 2026]:

No "To Live Colorado" was found anywhere. [SOURCED]

Open, and they stay open:

• USPTO clearance search could not be completed (search UI returned nothing). [UNKNOWN-NEEDS-INPUT]
• Colorado trade-name search could not be completed. [UNKNOWN-NEEDS-INPUT]
• Doctrine of foreign equivalents: "to live" is the literal English of "vivere". An attorney must weigh that against Reg. 1,779,343 directly — this is the single most important question to put in front of counsel, because the whole point of To Live CO is to get away from that registration. [SOURCED — the doctrine; the outcome is UNKNOWN-NEEDS-INPUT]

What that means operationally

6.6 Domains

Availability below is from RDAP checks run 21 Sept 2026 [CONFIRMED]. Owner identifications for the taken domains are from web search, not RDAP [SOURCED]. The Role and Note columns are recommendations, not findings.

The short form was considered as primary on the argument that "the domain IS the name". tolivecolorado.com wins — the handle string has to be tolivecolorado anyway (2.7), and matching the domain to the handle is worth more than four saved characters, especially with two live neighbours sitting on the short form.

Hosting: Cloudflare Pages project to-live-co, noindex until the wordmark exists and the domain is bound. Never link to vivereweb.com from it.

6.7 Handles — pick one string: tolivecolorado

The call: tolivecolorado on all four. It is free on Instagram, TikTok and YouTube and likely free on Facebook (UNVERIFIED, per the row above), and it is the string furthest from the live neighbours — toliveco is owned by a real operating brand that also holds toliveco.com, and holding that same string elsewhere is a liability, not an asset. Do not reserve @toliveco anywhere.

Display name everywhere: To Live CO.

Order of operations: register tolivecolorado.com first. Every link field below points at it, so filling those fields before the domain exists launches the accounts pointing at nothing.

A Page can normally be created and left unpublished, and that is the intended route here — it avoids showing Delta County an abandoned-looking empty Page. But neither the availability of /tolivecolorado nor whether Facebook will let an unpublished Page claim a username was verified on 21 Sept. [UNVERIFIED — confirm both in the Facebook UI before relying on this. If the username cannot be claimed while the Page is unpublished, claim nothing and leave the Page without a username rather than publishing an empty Page.]

Bios. None of these name Mimi's, none carry an address, none carry a phone. Each is in its own block so it can be copied straight out.

Instagram — 65 / 150

To live Colorado. Home of Chef Joe at Roadhouse. Delta, Colorado.

Facebook Page short description — 79 / 255

To Live CO. To live Colorado. Home of Chef Joe at Roadhouse in Delta, Colorado.

TikTok — 60 / 80

To live Colorado · Home of Chef Joe at Roadhouse · Delta, CO

YouTube channel description — 79 / 1000

To Live CO. To live Colorado. Home of Chef Joe at Roadhouse in Delta, Colorado.

Website meta description — 115 characters (no platform-enforced limit; ~155 is the Google display convention, not a cap)

To Live CO — to live Colorado. The Delta, Colorado umbrella for Chef Joe at Roadhouse and the ventures that follow.

The YouTube bio in the source material carried "215 Ute Street" — removed: the umbrella carries no address anywhere.

6.8 Minimal configuration for a parked account

A reserved account has to look quiet and owned, not dead. Dead is an account with no picture, no bio and a published Page with zero posts. Quiet and owned is five things:

Avatar brief (nothing can be reused, so this is a make-it job):

• TO LIVE set in Anton, with CO beneath or as a small mark, one colour — bone #E5D6BD on ink #0C1F39. Legible at small avatar sizes, around 26px. [ASSUMPTION — a design target, not a measured requirement]
• Do not recolour any existing Vivere Colorado art. [UNVERIFIED — the Vivere marks are Badge / Emblem / Wordmark; whether the Badge and Emblem carry the word VIVERE has not been re-checked for this section. Open each file before any reuse. Under R1, any mark carrying the word is unusable on a consumer surface.]
• Do not use the DR guitar-pick emblem — that is the partners' mark, and it is currently and wrongly serving as the Chef Joe site's favicon and PWA icons. [CONFIRMED — viewed 21 Sept]
• No flame. [ASSUMPTION — the flame is treated here as Chef Joe's; it is not ruled. The only confirmed Chef Joe lockup (1620×460 PNG at C:\Users\sutli\Desktop\Developer\videos\chefjoe-sunday-sep20\assets\chefjoe-lockup.png) is the DR pick plus Anton type and contains no flame.]
• Neutral ground on purpose: it must sit beside Chef Joe's navy/ember without fighting Mimi's red/gold.

Account settings, all four:

• Owner: Joe's login. 2FA on Joe's phone. Same recovery inbox as the Chef Joe accounts.
• Instagram: Professional → Business, "Manually approve tags" ON — nothing should ever land on this grid by accident.
• Facebook: created, username claimed, left unpublished, Joe as admin.
• Never connected to the scheduler (Blotato). There is nothing to schedule, and an unconnected account cannot be posted to by mistake. Every scheduler post must name its pageId explicitly. [UNVERIFIED — that the scheduler's default account is Vivere Web is not in the confirmed record; naming the pageId explicitly is the right practice either way.]
• Category on every platform: the most generic non-place option offered (e.g. "Brand" or "Organization"). Never a Local Business or any place category — those fields prompt for a street address, and rule 2 below forbids an address anywhere. Never a food or restaurant category, and never "Restaurants & Bars" [R5].

6.9 The hard rules

These are not style preferences. Breaking any one of them creates a real, named problem.

1. The umbrella posts nothing. Cadence is zero, permanently, with the single pinned holding-card in 2.8 as the only exception. If anyone proposes a To Live CO post, the answer is: post it from the brand it is about. This is not modesty — it is that Joe is one operator who also cooks, and a fifth feed is a fifth thing to abandon publicly. If it ever needs a voice at all, the ceiling is one post per venture launch.

2. No address. Anywhere. Not in a bio, not in a profile field, not in the Organization schema, not in a YouTube description. (The locality "Delta, Colorado" in the 2.7 bios is a place name, not a street address, and is allowed; a street address is not.) An umbrella carrying 215 Ute Street becomes a fourth identity at one address sharing an owner with the others — which is the shared-address pattern that risks a listing suspension. [UNVERIFIED — the suspension mechanics, and the claim that a suspension deletes reviews, are not in the confirmed record.]

3. No phone. Ever. Not Chef Joe's (970) 462-2817, not Mimi's (970) 874-3163, not the Roadhouse's, and absolutely not (970) 209-8978 — that number appears in one handoff as a booking line but Mimi's own files suggest it is Naomi's personal number. [UNKNOWN-NEEDS-INPUT] It goes on nothing, including this.

4. No Google Business Profile, now or later. To Live CO has no door, no sign and no hours. Google must never see it as a place.

5. Never claim to be "behind" Mimi's. Mimi's Sweet Treats LLC is a separate 50/50 company with Naomi as CEO. Vivere Colorado LLC is not behind it, does not own it, and saying so publicly is an ownership misstatement on a surface Joe controls. Every bio, page and schema field in this section ships without Mimi's. If Joe wants Mimi's presented as a To Live CO venture, that is Naomi's call and needs her written yes — and it would be a family-umbrella framing, not a parent-company one.

6. The word "Vivere" appears on no To Live CO consumer surface. Not in the footer, not in "a trading name of…", not in a copyright line. The LLC name lives on a /legal page, on B2B paper, on contracts and on invoices. Earlier drafts put "Vivere Colorado LLC" in the visible footer of the umbrella site; that is overruled here. Whether legalName: "Vivere Colorado LLC" may sit in the Organization JSON-LD is Joe's call — default OFF, since structured data on a public page is machine-readable and scrapable, which is close enough to a consumer surface to need a ruling rather than an assumption. [UNKNOWN-NEEDS-INPUT]

7. Schema is Organization, never LocalBusiness — no address field, no hours field, no telephone field. The absence is the point.

6.10 Separation from Vivere Web

Vivere Web (vivereweb.com, @vivereweb on Instagram and YouTube, Facebook page id 1141952239011602) is Joe's separate B2B web agency. It is out of scope for this entire playbook and is never touched. [CONFIRMED — R1]

The two are kept apart by five specific prohibitions:

One genuine overlap: Vivere Web may perfectly well build these sites, and the invoice for that work is B2B paper where both names are allowed to appear in full. That is a private document, not a public surface.

6.11 Open items for this section

7. Verification record

Everything in this document was checked rather than assumed. This section says what was checked, how, and what could not be. It exists so the next person does not repeat the work, and so anything unverified is visible rather than buried.

Evidence key

What was checked live on 21 September

What could not be checked

How the recommendations were produced

Six readers went through the Chef Joe site and its build documents, the twenty-one document research corpus from August, the Mimi's site and content pipeline, the print set and brand files, and the catering and partnership material. Three independent architectures were then designed from that evidence, each from a different starting principle: local search, operator capacity, and brand system. Three judges scored all three, one for discoverability, one for legal and partnership risk, one for sustainability. Each judge picked a different winner, which is why this document is a merge rather than a copy of any one of them.

Every section was then checked twice by adversarial reviewers, once against the facts and once against your rulings, and repaired where they found a problem. The reviewers were instructed to fail anything they could not verify.

Named limits of this document

• Hours are unresolved on purpose. Three sources disagree. Nothing here publishes a clock time until you rule.
• Bio character counts were counted twice, at writing and at review, against each platform's published limit.
• Nothing here has been posted, printed or claimed. Every account, purchase and listing in this document is yours to execute.