⚠ My own notes — just me and Naomi — never share, forward, or paraphrase to Tyler, TW, or Miles
My working notes — for me and Naomi, nobody else

The Negotiation, The Risk, The Money

Everything I can't say out loud in the room

Where I actually have leverage and where I don't, what's committed versus what's at risk, what I have to measure before location #2 opens, and the terms I need to secure before a dollar of buildout capital moves. Working through the negotiation and risk research myself, start to finish — every figure traced back to where it came from.

Read this first Full contents

For: me and Naomi — internal only
Written by: Joe · Date: August 13, 2026 · Draft v1

20
sections
50
findings, sourced
20
critical severity
Aug 17–23
the negotiation week

Contents

1. Read this first

ScopeWho's allowed to read this, why I wrote it, and the rule I'm holding myself to.

I'm writing this separately because a negotiation strategy, a partner's base rate, and my own cash position can't live in the same file as something T.W. Stites and Miles Van Hee might read. The shared report at `report/` says the plan, the numbers I'm comfortable putting in front of them, and the asks. This is everything underneath those asks — the leverage, the exposure, and the money.

Who may see this: me and Naomi. Nobody else, and not a screenshot, a forwarded section, or a paraphrase to Tyler, TW, or Miles. I'm talking about Tyler's own arrangement here in terms he hasn't seen (§5). If that needs to change, that's a call Naomi and I make together, not a default.

The rule I'm writing this under: state the value, never the leverage. Everywhere the shared report says what I'm bringing to the campus, this document says what happens if that thing never gets put on paper — and separately, what I'm genuinely exposed on and shouldn't pretend otherwise about, even to myself. The Roadhouse should hear confidence and specific asks from me. This is where the arithmetic behind that confidence actually lives, and it's not for their eyes.

How I built this: two full research passes over `15-roadhouse-agreement.md`, `19-master-plan.md`, `27-bottlenecks-redundancy.md`, `20-blindspots-v2.md`, and `10-blindspots.md` — 34 findings total, every figure traced back to a named source file, nothing invented. I'm flagging two data conflicts where they surface and not resolving them here — see §4 and §13.

How I need to use this before Aug 17–23: read §2 through §12 before I'm in the room. Read §13 and §14 before I agree to anything involving a number. Read §16 before anyone says a revenue projection out loud.

2. The asymmetry, stated once

ScopeWhat I actually bring to this, stated plainly — and an honest read on who needs whom more.

HighWhat I actually bring — say it plainly, once, and then stop apologising

My posture going in should not be supplicant. I'm not asking for a favour, and I bring five things into this deal that the Roadhouse can't generate on its own:

Seven days out of two. The Roadhouse publishes venue hours of Friday and Saturday, 11:00 AM to 9:00 PM+, and its live-music calendar runs a consistent Friday/Saturday cadence. I anchor Sunday through Thursday. That converts a two-day venue into a seven-day address without the Roadhouse adding a single labour hour of its own.

The arcade opens when Mimi's opens. Mimi's at Roadhouse sits inside the arcade building and replaces the arcade's existing snacks-and-ice-cream concession. Extending the arcade from two operating days to seven is value I'm delivering straight to the Roadhouse's own P&L. I need to name it as consideration in the negotiation — not let it sit there as a pleasant side effect nobody paid for.

A brand with local trust the Roadhouse has not had time to build. Mimi's is roughly two years established at 320 Main with a 4.9 rating, in a town of about 9,000 people. The Roadhouse opened June 2026 — roughly two months old as this was written. That asymmetry runs in my favour and it's the only one that does.

Capital into their real property. Courtyard lighting, windbreak, overhead cover, heaters and freeze-thaw-rated seating are improvements to the Roadhouse's asset, serving the trailer, Mimi's #2 and the Roadhouse's own patrons. I need to frame them that way — jointly fund them or trade them against occupancy terms.

An in-house caterer and a production agency. Vivere Catering fills the private-event lane out of our own kitchen. Separately, I'm applying web, photography, board systems, content and channel work to a shared campus. Both are real value — and I have to disclose the agency hat rather than quietly absorb it (§15).

Source: 19-master-plan.md

HighThe asymmetry, stated honestly — this is the part I can't put in the shared report

I'm bringing capital, brand and operating labour onto someone else's real estate, someone else's kitchen and someone else's licence. Every one of those rights is revocable by the Roadhouse unless I get it written down with teeth. The Roadhouse, by contrast, is exposed on exactly one axis — its liquor licence — but that axis is existential for them. That's why they'll demand control over pouring, and that demand is legitimate, not a power play.

Both sides have a genuine reason to want paper, and that's the frame I should open the meeting with. But I can't confuse a mutual interest in paper with symmetric leverage. The blunt sentence, straight from the research: I need the kitchen far more than the Roadhouse needs me.

Two facts compound it and I need to confirm both before I assume the seat at the table is reserved:

I need to ask both questions before the rent conversation, not after.

Source: 19-master-plan.md
3. Concentration

ScopeEvery revenue line my family owns now sits on one lot we don't control. I need to read this before anything else in the room.

CriticalConcentration: every revenue line the family owns now sits on one lot, and we don't control it

Let me stand back from the individual analyses and count what's at 215 Ute Street after this plan executes.

Before: location #1 owned its store and made its own product. The trailer was mobile — designed as a two-window unit explicitly targeting the Colorado festival and brewery circuit, with a ranked top-ten event list across Grand Junction, Palisade, Delta County, Montrose, Pueblo and Denver. There was one point of failure and we controlled it.

After: location #2 is a leased shell at 215 Ute. The trailer is parked in the courtyard at 215 Ute. Catering is produced in the commissary at 215 Ute. Production and wholesale relocate to 215 Ute. The liquor programme runs on a licence held at 215 Ute by someone else. And location #1 — the 4.9-star, family-owned, original unit — becomes a downstream customer of a building we don't control. There's still one point of failure. It's now controlled by two other men.

The direction of dependency has been inverted, and no single research document could see it because each one correctly analysed one unit. It lives between the documents.

The concrete failure: one counterparty event — a sale, a non-renewal, a lost food or liquor licence, capital redirected to their eight riverfront acres, or a default under a master lease I haven't read — takes down location #2, the trailer's commissary of record, the catering company, the wholesale plant, and the supply chain of location #1, in one move. Not sequentially. Simultaneously.

The question I need to ask myself out loud: if the Roadhouse relationship ended in month 18, what would I still own? Today the honest answer is a trailer, a brand, and whatever customer list I've managed to build. The buildout, the courtyard habit, the campus traffic and the arcade concession all accrue to the landlord.

Source: 20-blindspots-v2.md

HighThe plan quietly makes #2 the flagship and #1 the outlet — and #1 is the one you own, Naomi

Naomi — this part belongs to you and nobody else.

Under the brief, location #2 receives the expanded food menu, the liquor programme, the production plant and the wholesale line. Location #1 becomes "retail-led, supplied by the Roadhouse location."

The plan makes location #2 the flagship and location #1 the outlet. And the flagship sits in someone else's warehouse, under an unsigned lease, run by the two principals who are not the majority owner.

Whether that is intended is a decision. Right now it is a side effect.

The governance exposures sitting underneath it — none of them papered:

Naomi — the three-way founders' conversation with you, me and Tyler has to happen before the Roadhouse conversation, not after. Who owns what percentage of which unit, who contributes what, who decides what, and how someone exits. The unpapered deal between family and friends is more dangerous than the one with the landlord, precisely because none of us thinks it needs paper.

One correction I need to carry forward: "TW" is T.W. Stites, not Tyler Nordberg. The conflict-of-interest angle I was working from — the possibility that the person running Mimi's #2 sat on the landlord's side of the table — doesn't apply.

Source: 10-blindspots.md

HighThe only structural hedge I have left is keeping 320 Main able to make product — and it's nearly free

Two independent documents reach the same conclusion from different directions, and it's the single most valuable thing I found in the entire risk set.

Moving production from 320 Main to the Roadhouse increases capacity and simultaneously removes the only geographic redundancy I have. Both things are true. In the target end-state, one batch freezer at one address supplies Mimi's #1 retail, Mimi's #2 retail, and all wholesale. One machine, one address, three revenue lines — inside a building we don't control.

The fix costs me almost nothing: I should not dispose of 320 Main's production capability. I need to retain it through at least the first full year after the move, even at reduced scale, even if it's only the ability to run a batch in an emergency. As long as Mimi's #1 owns its recipes, its brand and its own premises, and as long as production can run there, losing the Roadhouse is survivable. Sell or scrap that capability and it isn't.

Three conditions need to gate the move, in order, before I do it:

  1. I confirm the licence class first. Wholesale/manufactured food is regulated differently in Colorado than a retail food establishment. Moving equipment into an unlicensed use is a self-inflicted outage that costs both the move and the season.
  2. The Roadhouse relationship has a multi-year term with real remedies. Moving production is what converts a partnership risk into an existential one. I need to do it from strength, not from optimism.
  3. 320 Main's supply is protected contractually — either a supply agreement with a term at least as long as the lease, or retained backup production. I can't let the original store become the dependent party with no fallback.

The same logic applies to the trailer's Friday–Saturday off-site lane. It's now the only diversification instrument I have left in the business. I can't let the courtyard agreement claim those days, and I can't let the catering agreement quietly consume them either — two documents independently found Fri–Sat is contested three ways.

Source: 27-bottlenecks-redundancy.md
4. The counterparty

ScopeA base rate on the Roadhouse itself — not a judgment on them, just the fact pattern I'm working from.

CriticalThe counterparty has no track record, and its own kitchen was unfinished on opening day

The Delta Roadhouse opened June 19, 2026 — roughly ten weeks before my September target. Everything below is sourced from the High Country Spotlight business profile, not inferred:

Put those three facts together. The commissary that gates the trailer's licence and is the catering business may not have existed as a licensed kitchen eight weeks ago. The building Mimi's #2 is moving into is the second of the two warehouses — a shell, not a demised space. And the landlord's stated posture is expansion, not stability: the courtyard, the warehouse and the kitchen that four of my revenue lines depend on are current-phase assets of a partnership already looking at the next phase.

This isn't a judgment about Miles Van Hee or T.W. Stites. It's a base rate. A venue this new has no seasonal history, no proven cost structure, no demonstrated ability to hold a schedule, and no track record of surviving its own first winter. I'm proposing to make it the sole foundation of five revenue lines before it's completed one full year of trading.

My detection lead time is currently near zero. I have no contractual right to know the Roadhouse is in financial or regulatory trouble until the door is locked.

Note to myself: `27-bottlenecks-redundancy.md` §3.1 states the venue is "14 months old at the target opening." Against a June 19 2026 opening and a September 2026 target that's wrong — it's about ten weeks. I need to not carry the 14-month figure forward into anything.

Source: 20-blindspots-v2.md
5. Public records to pull

ScopeOne afternoon of mine, under $50 in copy fees, before I sign anything — on both sides of the table.

CriticalI haven't checked whether the counterparty owns the building, or whether the entity I'm signing with is in good standing

Across eighteen research documents I found zero hits for assessor, county records, deed of trust, mortgage, or master lease. I haven't run a public-record check on the Delta Roadhouse, its owners, or 215 Ute Street. The records are public, free, and I can get them in one afternoon for under $50 in copy fees — Delta County Assessor (560 Dodge Street Suite 100, (970) 874-2120), Delta County Clerk & Recorder (501 Palmer Street Suite 211), and the Colorado Secretary of State business entity search.

Three exposures I hadn't named until now:

1. If the Roadhouse leases 215 Ute rather than owning it, everything I sign is a sublease — subordinate to a master lease I've never seen, on terms I can't negotiate. A default by the Roadhouse under that master lease terminates my sublease automatically. I'd lose the building, the commissary, the courtyard and the liquor arrangement simultaneously and without notice, with no privity with the actual owner and no standing to cure.

2. If there's a recorded deed of trust, a lender's foreclosure extinguishes a junior lease unless there's a Subordination, Non-Disturbance and Attornment agreement signed by that lender. I can find out this week whether one is even necessary, and from whom.

3. If Delta Roadhouse LLC is delinquent, non-compliant, or administratively dissolved, I'd be contracting with an entity whose capacity to contract is impaired — and the liquor licence the entire boozy-shake programme depends on sits on that same entity.

And I need to run the same check on my own side. My own records show Vivere Colorado LLC as NONCOMPLIANT as of 2026-07-16. That gates every trade name, licence and contract signature downstream. I can't ask a counterparty to prove good standing while my own signing entity is out of compliance.

I need to ask Miles and T.W. directly: do you own 215 Ute Street or lease it, and is there a mortgage on it? Their answers should match the records. A mismatch would be the single most valuable thing I could learn before signing.

Source: 20-blindspots-v2.md

CriticalBefore I agree to any terms: who signs, and which entity owns what

Nothing below can get drafted until this is settled, and it gates a large share of the program. This goes at the top of my meeting sheet, above every commercial term.

On my side: which entity signs each agreement? Is Mimi's Sweet Treats an LLC? Is the trailer entity separate from the agency and from Vivere Catering? If I sign four agreements as one entity I co-mingle the trailer's liquor-adjacent risk with the agency's balance sheet — and the question my attorney queue asks more sharply is: should alcohol-adjacent food service sit in the same LLC that owns the agency's copyrighted source code? I need to answer that before signature, not after a claim.

On the Roadhouse's side:

The question that changes the shape of the room: is "TW" Tyler Nordberg or a separate person? Tyler co-runs Mimi's at Roadhouse and the trailer with me. If there's ownership overlap between the licensee and the tenant in either direction, that's precisely the fact pattern the Colorado tied-house restriction (CRS 44-3-414) addresses, and I need it answered before any liquor structure is designed. It also changes who's actually sitting across the table from whom.

Internal-only, and it doesn't leave this document: Mimi's is a 50/50 ownership with no operating agreement and no tiebreaker. Naomi — no Mimi's-side commitment I make in a meeting binds until you've signed it. I can't agree terms on your behalf, and I can't let the room believe I can.

Source: 15-roadhouse-agreement.md
6. The 320 Main lease

ScopeThe document I already own and have never opened. One hour of my time, zero cost, could end this whole plan by itself.

CriticalThe one document I already own and have never opened could end the plan by itself

Across all eighteen research documents, the 320 Main Street lease gets referenced exactly once, in passing, as "the lease history." I've never actually treated it as a document to be read. Every term in it is unknown to me.

Commercial retail leases routinely carry provisions this plan walks straight into:

The failure mode, stated plainly: I sign at 215 Ute, open location #2, and the landlord at 320 Main sends a default notice citing a radius clause I forgot about. The remedy in most such leases is termination and acceleration. I'd lose location #1 in order to open location #2.

I need to find it and read it today. One hour, zero cost. If a radius restriction exists, I call a Colorado commercial real estate attorney before the Aug 17–23 meeting — waivers are usually available for consideration, but I have to ask before I sign the other side, not after. I also need to put the expiry date on the same timeline as everything else: if 320 Main's lease expires inside 24 months, that's a negotiating fact I need before committing capital 0.69 miles away.

Source: 20-blindspots-v2.md
7. The commissary unblock

ScopeDelta County's requirement is a signed agreement from a licensed commissary — it doesn't say which one. This is the one real leverage move I have before I'm in the room.

CriticalThe one move that changes the balance: I need to ask Delta County about 320 Main before I negotiate

Every document in both research waves I pulled together treats the commissary as a Roadhouse dependency, because the brief says I have access to the Roadhouse commissary. But Delta County's requirement is a signed agreement from a licensed commissary — it doesn't say which one. Mimi's Sweet Treats at 320 Main Street is an operating, licensed retail food establishment, owned by Naomi, roughly two years established.

If Delta County will accept 320 Main as the trailer's commissary, three things happen at once:

The counter-arguments, honestly: 320 Main is an ice cream shop, and the county may judge its warewashing, dry/cold storage and prep capacity inadequate to support a burger trailer. My own plan also relocates production and wholesale away from 320 Main, so its capacity is shrinking, not growing. And a commissary has to be usable at the hours the trailer actually preps.

But it costs one phone call to find out. I need to call Delta County Environmental Health, (970) 874-2165, and ask both questions in the same call: can 320 Main Street serve as commissary for our mobile unit, and can a kitchen inside a liquor-licensed premises serve as a commissary at all? (Denver's guide warns some liquor-licensed facilities aren't accepted as commissaries — not binding in Delta County, which is exactly why I need to ask rather than assume.)

Best structure if both work: name 320 Main primary and the Roadhouse secondary. Redundancy on the one node that can stop the business — and, not incidentally, the only genuine leverage move I have available before the room.

Source: 19-master-plan.md

CriticalHandshake risk #1 — the commissary. Existential, and it fails before I even get to fail.

Ranked first because a handshake here doesn't produce a weak position, it produces no business at all.

Colorado requires a mobile retail food establishment to operate from a licensed commissary unless fully self-contained, with a signed commissary agreement and a use log kept at the unit during operation. The signed agreement has to be in the plan review packet at the time of application.

What happens if it's only a handshake: the packet can't be submitted. This blocks the submission, not merely the approval — the 14-working-day statutory response clock under CRS 25-4-1605(4) never even starts. There's no version of this where goodwill substitutes for the document, because the reader of the document is a plan reviewer, not a partner.

Catering fails the same way, through its own instrument (the county may require two).

And then the tail risk, which is worse. My own food licence would name that kitchen. If the Roadhouse's food or liquor licence is suspended, my commissary vanishes and my licence is unsupported — and switching commissaries means new plans and probable new plan review. My research calls this clause "the deal," and that's the correct weighting.

Mitigations, in order: I need to ask for the agreement as a standalone one-page attestation decoupled from rent terms; in the same week I need to ask Delta County whether 320 Main can serve as commissary instead; and I need to draft the existential clause with counsel — what happens to my licences if the Roadhouse's licence goes down.

Source: 19-master-plan.md
8. Terms to secure

ScopeNine clauses across the four remaining shared rights. I need to ask for these in the same meeting as rent, not after.

HighThe space and lease boundary I need to lock down

I need to get this straight first: this is a demised space inside the arcade building, not the standalone building I'd been picturing. That changes the lease from a building to a space, and it puts shared restrooms, shared utilities and a shared licensed-premises boundary into play.

I need a lease, not a licence to occupy. A lease conveys exclusive possession and creates a leasehold estate. A licence to occupy is merely a privilege to use the property, creates no property estate, is typically revocable at will, and is usually not assignable. I can't put buildout capital and a permanent second location on a revocable permission. There's a second reason I need to care about, maybe even more than the first: Colorado liquor licensing turns on the applicant's possession or right to possession of the licensed premises, so a revocable licence is weak evidentiary ground for anything touching the liquor structure.

Boundary and condition — what I need to pin down:

Use clause — I need to widen it deliberately. It has to cover ice cream, expanded food, liquor-based treats later, and wholesale/manufacturing production, because I'm planning to relocate production from 320 Main into this space. A narrow "ice cream shop" use clause quietly blocks two of my four revenue lines.

Source: 15-roadhouse-agreement.md

CriticalHandshake risk #3 — the demised space. Where my capital goes to die.

What happens if this is only a handshake, or a licence to occupy: my buildout capital, a fixed public address, a Google Business Profile, fabricated signage, printed menu boards — and, per my plan, the wholesale and manufacturing relocation out of 320 Main — all sit on a permission that is typically revocable at will and usually not assignable, creating no property estate.

Three consequences stack on top of each other:

Secondary but real: if I agree to a narrow "ice cream shop" use clause informally, it blocks both the liquor-based treats line and the wholesale production line — and I won't notice until it's too late to renegotiate cheaply.

Source: 15-roadhouse-agreement.md

HighRent structure — the benchmark I'm negotiating against

Restaurant occupancy-cost norms give me a defensible band to negotiate inside: a healthy target is roughly 5–8% of gross sales, high-traffic locations may run 9–15%, and restaurants "generally cannot operate profitably with rents above 8 to 10 percent of gross sales" (Paytronix; The Cauble Group). In a percentage lease the natural breakpoint equals annual base rent divided by the percentage rate — the worked example I'm using is $60,000 base at 6%, meaning percentage rent begins after $1,000,000 in sales (Northmarq; Tango).

I need to push for a hybrid: a modest base plus a percentage over a natural breakpoint. It aligns the Roadhouse's interest with my success and protects me through the ramp. If percentage rent is on the table, I need four things nailed down or it becomes a trap:

  1. The definition of "gross sales." Does it exclude sales tax, employee meals, comps, refunds, third-party delivery commissions, and gift-card sales until redeemed?
  2. Whether liquor revenue counts toward my gross sales at all. The Roadhouse is likely the licensee of record and may be ringing those sales on its own POS. If the Roadhouse takes the liquor margin and charges percentage rent on it, I pay twice. This is a real double-count risk and I need it closed in writing — see §10.
  3. Reporting and audit rights — what gets reported, how often, and the Roadhouse's audit right with a threshold, so audit cost shifts only if an understatement exceeds something like 2–3%.
  4. A cap on total occupancy cost as a percentage of sales, so a good year doesn't become unaffordable.

I also need to negotiate rent abatement during buildout and a ramp for the first months of operation, plus how rent resets on renewal (fixed bump, CPI, or market).

Courtyard rent is a separate number and deserves a different logic. The trailer operates on the five days the campus is publicly dark and has to generate all of its own traffic — it's not capturing Roadhouse spillover. That argues for a nominal or percentage-only courtyard fee rather than a flat market rate, for shared Sun–Thu marketing cost, and for the Roadhouse opening restrooms and lot lighting on trailer nights as part of the consideration.

I don't have a rent figure, a square footage or a revenue projection for Mimi's at Roadhouse right now. I'm not going to model this with invented numbers, and I'm not agreeing to a number in the room — lease terms land the week of Aug 17–23.

Source: 15-roadhouse-agreement.md

HighExclusivity, in both directions

What I'm asking for: no competing dessert, ice cream, frozen treat or bakery vendor anywhere on the campus — including in the courtyard, at Roadhouse-hosted events, and among third-party vendors the Roadhouse invites. I also need to settle whether the Roadhouse itself can serve dessert in the restaurant.

This isn't theoretical. The arcade already advertises "snacks and ice cream," and Mimi's replaces that existing concession. That's the single strongest exclusivity argument I have: I'm not asking to be protected from a hypothetical competitor, I'm taking over a line the Roadhouse currently runs itself. Getting it in writing is what converts "I absorbed your concession" into a protected position instead of a favour that can be reversed the moment someone offers them a better split.

Courtyard exclusivity Sun–Thu: no competing food vendor in the courtyard on trailer nights, defined by cuisine category once the concept is locked.

The mirror they'll ask for: that the trailer not compete with the Roadhouse's core BBQ menu. Two rules govern how I concede it:

I need to verify first: is there already an incumbent food truck with an arrangement on the campus? An exclusivity clause is worth what the existing arrangements allow, and a promise that can't be honoured is worse than no promise.

Source: 15-roadhouse-agreement.md

MediumSignage and public identity

Signage on this campus isn't cosmetic — it's a platform requirement with a review-history consequence attached. Google permits a second profile at a shared address only for a distinct business with a different name and clearly visible signage differences. No sign means suspension risk, and a hard suspension takes the reviews with it. Mimi's 4.9 rating can't transfer between profiles. Four profiles at one address, two sharing a name root, one owner — that's the textbook hard-suspension pattern.

I need to secure in writing:

Source: 15-roadhouse-agreement.md

HighHours independence from arcade and venue hours

The Sun–Thu strategy is settled and deliberate: I'm the anchor on those days and I have to generate my own draw, not inherit Roadhouse traffic. What's not settled is whether the campus is physically open on those nights, and that's a negotiation term, not a given.

I need to secure:

Source: 19-master-plan.md

HighHandshake risk #4 — the courtyard. "Mobile" is less mobile than it sounds.

What happens if it's only a handshake: the trailer has nowhere to park five nights a week, and I don't have an answer for displacement when the Roadhouse books its own event.

Here's what I still need answered before I sign anything:

And here's the thing that makes this heavier than it looks: a fixed-site trailer is far less mobile than the word implies once a Google pin, measured coordinates, printed panels advertising hours, and a wrap all exist. A fixed-address trailer advertises hours, not "find us." Moving it isn't a Tuesday decision for me.

What I need: a siting licence is the right form here — but a term licence with defined notice, not one revocable at will, and with a term matched to the premises term where possible.

Source: 15-roadhouse-agreement.md

CriticalCommissary access guarantees

This is a regulatory filing document, not a handshake courtesy. Colorado's retail food rules require mobile retail food establishments to operate from a licensed commissary unless fully self-contained, and require both a commissary agreement and a commissary use log available at the mobile unit at all times during operation. A health inspector may ask to see it. It has to be signed, dated, and specific enough to satisfy a plan reviewer — and in hand at the time of application, not after.

I need to ask for it as a standalone one-page attestation, decoupled from the lease. The county-drafted form isn't a negotiation; there's no reason it should wait on rent terms. Then I need to secure, in the fuller instrument:

Separately, I need the kitchen documentation released: floor, plumbing, electrical and site plans, hood type and dimensions, fire suppression status, PWSID number, water and sewer type. I can't file the catering plan review packet without them — and a refusal to release them is itself a negotiating signal worth reading.

Source: 15-roadhouse-agreement.md

LowSmoker use — the fifth shared resource

The smoker is the smallest of the five shared resources and the easiest to leave unwritten, which is exactly why I want to name it here. The "Roadhouse Smoke Burger" uses the Roadhouse's smoker — so a menu item and the partner's brand name both sit on an asset I don't own and currently have no written right to touch.

Terms I need: access days and hours; capacity allocation and who wins a conflict; who fires and tends it; fuel and its cost; cleaning and maintenance responsibility; whether my product may occupy it during Roadhouse service; and what happens if it fails, is replaced, or is taken out of service. Plus the written sign-off on the item name, with a defined wind-down if the relationship ends.

My own pragmatic note to myself: the master plan already recommends cutting the Smoke Burger from the v1 trailer menu — it's limited to roughly 30 a day, and smoke-then-sear is a two-stage process needing prep capacity the trailer may not have. Cutting it for v1 also removes a partner dependency from the launch. It's far easier for me to negotiate smoker access calmly as a Phase 2 addition than to have a printed menu panel hostage to it. The print lead time is the only externally controlled item on that path — a menu change isn't a same-day fix for me.

Source: 19-master-plan.md

LowHandshake risk #5 — the smoker. Smallest exposure, cheapest fix.

What happens if it's only a handshake: the least damaging of the five — but it's not zero, because the dependency currently sits inside a named menu item that also borrows the partner's brand.

If access is withdrawn, the smoker is out of service, or capacity is claimed by Roadhouse production on a Friday, the Roadhouse Smoke Burger can't be served. On a printed ACM/Dibond panel that's not a same-day fix for me — print turnaround is the only externally controlled item on the menu-panel path, and I have to check a hard proof against a signed price sheet before any reprint releases.

My fix is sequencing, not paper. I'll cut the Smoke Burger from the v1 trailer menu, as the master plan already recommends on independent operational grounds. That removes a partner dependency from the launch entirely and lets me negotiate smoker access calmly, in Track B, as a Phase 2 addition.

I still need to get the written sign-off on the name before the item ever appears anywhere, even if I defer the item itself.

Source: 19-master-plan.md

CriticalThe liquor structure

"Under the umbrella of the Roadhouse's licence" is a business description, not a legal structure — and from what I've found, it's not a structure Colorado law recognises. CRS 44-3-301(3)(a)(I) exposes both parties. A liquor licence doesn't travel with a brand or an owner's goodwill; it attaches to a licensee and a defined licensed premises.

My first move is a records request, not a negotiation. I need to get the approved licensed-premises diagram on file with the City of Delta for liquor licence No. 03-25524 (Delta Roadhouse LLC, TAVERN, "209 & 215 Ute Street," issued 2026-06-12). If the arcade space and the courtyard are already inside the approved diagram, the problem shrinks enormously. If they're not, extending service into them is a modification of the licensed premises under Colorado Liquor Rule 47-302 — which reaches changes to usage as well as physical layout — requiring prior written consent of both the local and the state licensing authorities. That's a filed DR 8442 on a regulator's hearing calendar, with 30-day holds and 2–3 month norms, and it's the licensee's application, on their calendar, not mine.

I need to settle in writing, regardless of which structure counsel picks:

I need to say the uncomfortable thing first, before anyone signs: under any shared-licence structure the licence is theirs, and their entire Friday–Saturday revenue engine is collateral for one mistake at an ice cream window. Saying it before they do is worth more than conceding it after.

Source: 19-master-plan.md

CriticalHandshake risk #2 — the liquor licence. The one that can end the partnership, not just the product line.

What happens if it's only a handshake: I'm operating a product line under a structure Colorado law doesn't recognise, with both parties exposed under CRS 44-3-301(3)(a)(I) for exercising licence privileges that aren't theirs. That's not a contract gap; it's a licensing exposure that attaches to the Roadhouse's licence — which is their entire Friday–Saturday revenue engine.

Three specific failure modes a handshake leaves open:

A handshake also leaves me with no rent relief when the licence goes down for reasons that have nothing to do with me.

My cheapest mitigation is sequencing, not drafting: launch dry. Open Mimi's at Roadhouse retail-only, with no alcohol, and treat liquor as an explicit Phase 2 once the premises modification is granted. Reg. 47-302 approval sits on someone else's calendar and I can't compress it by wanting to; the ice cream and expanded food lines don't depend on it. Liquor is the upside, not the launch premise.

Source: 15-roadhouse-agreement.md

HighTerm, exit, assignment and successor protection

The Roadhouse opened June 2026. That's not a criticism of the operators; it's a statement about risk concentration. If the Roadhouse closes, Mimi's at Roadhouse loses its landlord, its commissary, its liquor licence, and essentially all of its foot traffic — because on this campus the campus is the trade area. 215 Ute Street is a destination, not a Main Street storefront with passing trade.

Terms I need to have in place:

Cross-default is a decision I need to make deliberately, not a default setting. If the premises lease ends, do the commissary and courtyard rights end too? Naomi — I'm pretty sure we want them decoupled, so a lease dispute doesn't simultaneously kill catering.

Source: 15-roadhouse-agreement.md
9. Deal structure

ScopeOne master agreement is the wrong shape for this. Two tracks, four to five standalone instruments — that's the fit.

HighDeal-structure options — and the one that fits my situation

Option A — one master agreement covering all five shared resources. I'm rejecting it. Negotiating the building, commissary, courtyard, liquor licence and smoker as a single instrument guarantees the slowest item sets the pace for the fastest. Liquor is months on a regulator's calendar. The commissary form is a county-drafted one-page attestation. There's no reason the attestation should wait on rent terms — and if it does, the plan review clock never starts.

Option B — two tracks, four to five standalone instruments. This is the fit for me.

Instrument choice inside the tracks:

Why B fits here specifically: it protects the only dates I can actually reach, it keeps my regulatory standing independent everywhere the law permits, it puts the highest-legal-risk item on a deliberate calendar rather than a launch calendar, and — the point that matters most to me internally — it means a stalled rent negotiation can't hold the trailer's licence hostage.

Source: 19-master-plan.md
10. The double-count trap

ScopeIf the Roadhouse takes the liquor margin and charges percentage rent on it, I pay twice. I need to close it in the definition of gross sales.

This is small enough to bury inside the rent conversation and expensive enough that I want it as its own line item.

The mechanism: the Roadhouse is likely the licensee of record for any alcohol Mimi's serves, and may be ringing those sales on its own POS (§8, liquor structure). Separately, the rent structure I'm looking at is a hybrid base-plus-percentage lease, with percentage rent calculated against my "gross sales" (§8, rent structure).

If I don't get those two facts reconciled in the lease's own definition of gross sales, here's what happens: the Roadhouse takes the full liquor margin — as the licensee, that's defensible — and then the same liquor revenue gets counted toward my gross sales for percentage-rent purposes, because nobody excluded it. I end up paying rent on revenue I never touched.

The fix is one sentence in the lease, agreed before signature: the definition of "gross sales" for percentage-rent purposes explicitly excludes any alcohol revenue for which I'm not the entity of record on the POS transaction. Whoever drafts the lease should treat this as a required exclusion, not an optional one — I can't count on the landlord's template to include it unless I ask.

11. Non-concessions and walk-aways

ScopeSixteen things I'm not conceding, and which walk-aways are from one piece of this versus from the whole campus.

HighWhat I shouldn't concede

Sixteen items. Every one of them is cheap for me to hold now and expensive to recover later.

  1. A licence to occupy for the demised space. My buildout capital and a wholesale relocation can't sit on a revocable permission.
  2. Percentage rent on liquor revenue I don't receive. See §10.
  3. "Anything competitive" as the non-compete definition. I need a named list of dishes and categories — and I'm not signing a concept-level non-compete while the trailer menu is still labelled v1 (flexing).
  4. Uncapped indemnity, or any indemnity that covers the Roadhouse's own negligence. I need to cap the exposure, exclude consequential damages except where insurance responds, and define who controls the defence.
  5. Short-notice commissary termination. I need at least 90 days, nothing inside the booked catering horizon, and an end date aligned to the Dec 31 calendar-year licence renewal.
  6. Termination-for-convenience notice shorter than the catering booking horizon. Catering sells months ahead; my reputation is what defaults.
  7. The trailer's Friday–Saturday freedom. That lane is my diversification, my festival strategy and my off-site revenue. I need to confirm the Roadhouse can't demand it.
  8. Publishing anything co-branded before the consent letter is signed — and nothing whatsoever about alcohol before the premises modification is approved, under any commercial pressure. The deciding regulator can see the marketing.
  9. A personal guaranty without a burn-down.
  10. Describing myself as a licensee anywhere, in marketing or otherwise. I'm not one.
  11. Vivere Catering operating as an extension of the Roadhouse's food licence. I need to own the licence, borrow only the kitchen.
  12. Gifting the courtyard improvements. Lighting, windbreak, cover, heaters and seating are improvements to their real property. I need to jointly fund them or trade them against occupancy terms — not pay for their asset and call it goodwill.
  13. Total occupancy cost pushing past the roughly 8–10%-of-gross-sales band without a ramp, and no rent abatement during buildout.
  14. A rent number agreed in the room. Lease terms land the week of Aug 17–23; nothing financial is final until they do.
  15. Signing all agreements as a single entity.
  16. Operating without a licence to save a date. Not a concession, a hard floor — it risks my licence, the Roadhouse's licence, and Mimi's clean reputation in a town of 9,000. It's not an option worth discussing, including with myself.
Source: 15-roadhouse-agreement.md

CriticalMy walk-away conditions — and which ones mean walking away from a component, not the campus

Most "walk-aways" here aren't really walking away. Separating them out is what keeps a bad term on one resource from turning into a reason for me to concede on all five.

I walk from the alcohol line — not the deal — if:

I walk from the courtyard site if:

The trailer generates its own draw on those nights anyway — that's my stated strategy, not a consolation. If I can't secure the site, the festival and off-site lane plus a different fixed site are live alternatives, not a catastrophe.

I walk from the buildout — not the relationship — if:

Under any of those conditions: I don't spend buildout capital, and I don't move wholesale production out of 320 Main. Moving production before the Roadhouse facility is licensed and the tenancy is secured strands both locations.

On the commissary, I substitute rather than walk:

I walk from the campus entirely if:

Source: 19-master-plan.md
12. Paid-pilot risk

ScopeSuccess is the failure mode here. Three clauses fix it, and none of them exist yet.

HighI may be running a paid pilot for my landlord — and success is the failure mode

This is the unsparing version, and it's not an accusation about Miles Van Hee or T.W. Stites. It's a description of what the current paperwork permits.

What they own: the building, the second building, the kitchen, the liquor licence, the courtyard, the arcade, and eight more acres along the Gunnison River with development already under consideration.

What they've already demonstrated: the arcade page advertises snacks and ice cream today, and a third-party food truck covered their food service through opening. They've already run the experiment of a food unit on their lot.

What I'm proposing to give them: five additional operating days, a family draw midweek, a food programme they don't have to run, an in-house caterer for their event centre, a marketing engine, an established 4.9-star local brand, and a proven courtyard concept — on their property, under their licence, out of their kitchen.

What I currently have in return: no signed agreement of any kind, no term, no renewal option, no right of first refusal, no exclusivity, and no non-compete in either direction.

At the end of twelve months they'll know precisely which items sell, in what volume, on which nights, at what margin — because it'll have happened on their lot, through their kitchen, in front of them. The cheapest move available to them at that point is to decline to renew and run it themselves. Nothing in the current arrangement stops that.

And here's the inversion I need to sit with: success is also the failure mode. If the courtyard fills Sun–Thu, the rational response of a landlord with no term commitment is to reprice the courtyard or take the concept in-house. The better this works, the more exposed I am.

Three clauses fix it. All standard, all cheap, all currently absent — I need to ask for them in the same meeting as rent, not after: a term with a renewal option at a pre-agreed formula (not "to be negotiated in good faith," which isn't a right); exclusivity as the campus dessert and prepared-food operator, which is also what makes the arcade concession worth building; and a mutual non-compete / non-circumvent covering the concepts I'm bringing.

If they won't grant a term, that refusal is worth more to me than the rent number is. It tells me what the relationship actually is, while I can still act on it.

Source: 20-blindspots-v2.md
13. Cannibalisation instrumentation

ScopeLocation #2 is additive May–September and cannibalistic November–March — and it opens right into the cannibalistic half of its own year. I have to measure this now or I lose the ability to ever know.

CriticalThe honest read: additive May–September, cannibalistic November–March — and I'm opening #2 into the cannibalistic half of its own year

Nobody had done this arithmetic, so I did.

320 Main does roughly 6,630 orders a year — about 18 a day — at $15.99 per order, in a town of 9,421, with repeat customers visiting two to three times a month. The two sites are 0.69 miles apart. In a market that small the customer count is close to fixed. The only question I actually need answered is whether location #2 adds occasions or relocates them.

Where #2 is genuinely additive:

Where it is purely cannibalistic: Sunday through Thursday. On those five days the campus is dark — six documents now confirm Fri–Sat-only published hours, with all 15 scheduled events between Aug 14 and Oct 9 2026 falling on a Friday or Saturday and zero Sun–Thu programming. There is no event crowd and no arcade draw unless the Roadhouse commits to opening. A second Mimi's counter 0.69 miles away is then competing for the same ~18 daily orders that already exist.

The conclusion I hadn't drawn until now: location #2 is plausibly additive from roughly May to September, and structurally cannibalistic from November to March — and it's scheduled to open in September, into the cannibalistic half of its own year.

That's the opposite of the sequencing I'd choose, now that I've done this arithmetic. It compounds the winter problem with a mechanism I hadn't named before: in winter the new unit isn't merely ramping slowly, it's actively taking sales from the unit that has to fund it — at a time when 320 Main runs about $221.55/day against a full-year daily average of $345.78 (late-autumn trade is roughly 64% of the annual daily average, and December–February are unmeasured with no reason to expect them higher).

I need to seriously model opening #2 in spring 2027 instead. It puts the new unit's first six months in the additive half of the year, moves the winter burn out of the ramp entirely, and gives the warehouse conversion a schedule that isn't a fiction.

Data conflict I still need to settle: the brief carries 9,421 population; the research files carry 8,909. One is wrong. I need to pick a source and use it everywhere.

Source: 20-blindspots-v2.md

CriticalExactly what I need to measure before #2 opens, or the answer is unknowable forever

This is the irreversible item. Once the campus opens I can never again measure what 320 Main did without it. Every instrument below has to exist before opening day — retrofitting any of them produces a number nobody can trust.

  1. I need to freeze the trailing 12-month Clover baseline this week — by week, not by month. Export it, date it, and store it somewhere that isn't a working file.
  2. I need to capture transaction counts separately from revenue. Revenue alone can't distinguish a footfall shock from a mix shift or a price change — counts and revenue tracked separately can.
  3. I need to separate revenue by unit at the POS level before opening — a separate Clover merchant ID, or at absolute minimum separate revenue classes. The existing dashboard aggregates one unit; with three it'll blend them into a single number and hide exactly the thing I need to see. Merchant underwriting has lead time and I still haven't confirmed whether a second application has even been started.
  4. I need to track covers by day of week, split weeknight vs event night, from day one at both units. It's the only way to distinguish "the concept failed" from "the campus was closed." Un-captured September baselines are gone forever.
  5. I need to build a customer identifier that works across both units. Clover's native loyalty doesn't cross locations. Without a shared identifier I can measure totals but I can never measure who moved — and "same customers, different door" versus "new customers" is the entire cannibalisation question.
  6. I need to baseline review count and rating per profile before the second Google Business Profile goes live.
  7. I need to record the Main Street construction start date as a known confound — see the next item.
  8. I need to write the day-30 and day-90 targets and the kill criteria before the numbers start arriving. A threshold set after the fact is a rationalisation, not a control. Naomi — you set the values, nobody else.

Without items 1 through 5, the first hard question anyone asks — is this a concept problem or a campus problem? — becomes permanently unanswerable, and the decision to close or defend a unit gets made emotionally, late, and expensively.

Source: 20-blindspots-v2.md

HighMy measurement will lie to me — Main Street is getting torn up and zero of eighteen documents mention it

My measurement plan is correct and it's going to be confounded, in a way that produces exactly the wrong decision.

The City of Delta is running the Revitalizing Main Street Project — a reconstruction of the 13-block corridor through historic downtown Delta, covering street, drainage, hardscape, pedestrian access and landscaping. As of early 2026 design was substantially complete and the City was awaiting federal obligation of construction funds, with authorisation delayed.

320 Main Street is inside that corridor. The October 2025 lender document already refers to the project approvingly, as a future improvement.

The concrete consequence: when construction starts, 320 Main's parking, access and foot traffic take a material hit for a construction season. If that lands in 2027 while I'm measuring cannibalisation, I'll read a construction-driven decline at location #1 as proof that location #2 stole its customers — and either close a healthy unit or defend a failing one, on evidence that means neither.

The fix is one free phone call. I need to call City of Delta Community Development, 360 Main Street, (970) 874-7566, and ask for the current construction schedule for the 300 block. Then write the start date into the measurement plan as a declared confound before it happens — because a confound named in advance is an adjustment, and a confound discovered afterwards is an argument.

Source: 20-blindspots-v2.md
14. Cash and capital

ScopeI can't currently assess my own cash position. That's the finding — no reserve figure, no committed capital, no lease cost, and a revenue line that may be double what's real.

CriticalWhat's committed, what's at risk, and what I genuinely can't know until the lease lands

Cash cannot be assessed. That's the finding. I don't have a reserve figure, a committed capital figure, a lease cost, a buildout bid, or a wage budget anywhere in the research I've got on disk. Cash may well be the real binding constraint on this whole programme, and right now I have no way to test it.

COMMITTED — the good news, and it's genuinely good

The trailer is owned and in hand. Mimi's #1 is debt-free — that's the single best fact in this whole financial picture. Recorded equipment value is $38,394; total equity is recorded at $119,380.07 as of the November 2025 workspace file.

HighAT RISK — my money going into someone else's building

The Roadhouse buildout is a blank in every budget I've got, and it's not a paint-and-signage number. Mimi's #2 is going into the second of two vacant warehouse buildings that lacked running water and sufficient electrical service eight months ago. A warehouse shell doesn't have floor drains, a grease interceptor, hot water at required temperature and volume, a three-compartment sink and dedicated hand sink, a Type I hood with suppression, washable wall and ceiling finishes, coved sealed flooring, food-grade HVAC and make-up air, ADA customer restrooms, or the electrical service to run batch freezers. This isn't a tenant improvement; it's a shell-to-food-plant conversion — plausibly a City of Delta building permit with a change of occupancy classification, a county plan review, a separate state review for the wholesale operation, and licensed trades working to their availability rather than mine.

I CAN'T KNOW ANY OF THIS UNTIL AUG 17–23: rent, the occupancy terms for all four rights (premises, commissary, courtyard, liquor), whether there's a tenant improvement allowance, and — decisively for the cost of delay — whether rent commences on signature, on opening, or on licensing. If rent commencement is tied to opening rather than signing, the cost of a staggered launch is close to zero. That's a specific term I need to negotiate for, and I haven't asked yet.

MISSING FROM EVERY BUDGET I'VE GOT, both confirmed by the documents themselves:

Three hard rules for myself while the numbers are unknown:

  1. Not one dollar of buildout spent on 215 Ute Street before a signed document exists. Not a handshake, not a term sheet — signed.
  2. I need to write a one-page sources-and-uses. Where each dollar comes from, where it goes. If the columns don't balance, the scope is wrong.
  3. I need a scoped, written contractor bid before the Aug 17–23 meeting. I can't ask for a TI allowance credibly without a number. Then I need to negotiate amortisation and reimbursement of unamortised improvements on early termination — the single most valuable clause available to a tenant improving someone else's shell.
Source: 20-blindspots-v2.md

CriticalThe revenue number I've sized this whole thing off may be roughly twice the real one

The revenue discrepancy I've been circling for nine months has a name, and the named line is the problem.

The lender package I prepared 2025-10-24 for an $85,000 loan request states:

LineAmount
Total Revenue 2025$251,812.10
Clover Sales (Credit/Debit)$110,382.30 (44%)
Sales (Cash/Other)$129,461.37 (51%)
Billable Expense Income$10,099.18
Services$1,894.00
Sales of Product Income-$24.75

The Clover export for Oct 25 2024 – Oct 24 2025 records total net sales of $106,104.57. The Clover workspace summary for Jan 1 – Nov 21 2025 records cash at 26.5% of payments — $36,088.91.

I asserted $129,461 of "Cash/Other" revenue in a year where the point-of-sale system recorded $36,089 of cash. That's a gap of roughly $93,000 between the cash revenue I claimed and the cash actually recorded.

There are three explanations and they lead to very different places:

(a) It's catering, wholesale and event revenue invoiced outside the POS. Legitimate — the business genuinely has non-retail channels. Then I need to rename the account and produce the invoice detail. "Cash/Other" isn't a revenue category, it's a bucket.

(b) It's owner contributions, loan proceeds, or inter-account transfers posted to an income account in QuickBooks. Then 2025 revenue is roughly $110–120K, the 34.8% margin I've been claiming isn't real, and there's no distributable profit to fund an expansion. Every plan I've got is sized against a top line roughly twice the real one.

(c) It's unrecorded cash sales. A matter for the CPA, not for this document and never for a landlord.

A second discrepancy compounds it: I've got two average tickets in circulation, differing by a factor of two. The lender document states $15.99 average ticket across 6,630 orders; the Clover workspace states 14,432 transactions at $7.79. 6,630 × $15.99 = $106,032, which matches the Clover export almost exactly — so $15.99 is per order and $7.79 is per transaction record. Both are in circulation and picking the wrong one doubles or halves every model I build on it.

What I need to do: have whoever keeps the books run the QuickBooks account detail behind "Sales (Cash/Other)" — one report, one afternoon, open since November 2025. Rename the account to whatever it actually is and re-issue the breakdown. Footnote on every financial page whether net income is stated before or after owner compensation. And if the BSide Capital application is still live, the lender is entitled to know the plan changed: Ouray is dead, the trailer's business model is different, and the use of funds has moved.

Standing rule for myself: no external document leaves this programme carrying a revenue figure until I close this out. Not the lender, not the landlord, not the report.

Source: 20-blindspots-v2.md

CriticalThree simultaneous negative-cash-flow periods, landing in the weakest quarter, against a reserve figure I still don't have

This is the mechanism by which profitable small businesses actually die: not a bad idea, but a timing mismatch between when capital is consumed and when it is generated.

Here's what I'm stacking up:

Naomi — the reserve figure is on us, you and me. No substitute is acceptable and I'm not offering one here. What I can say without inventing anything is the method: a reserve isn't a target balance, it's a number of days of survival at zero revenue, sized against the longest plausible interruption this specific business faces — a health-department closure and re-inspection, a liquor suspension (published enforcement outcomes run 5 to 20 days), a production-equipment failure, commissary loss and re-permitting, a total trailer loss, and a bad winter — 13 weeks, on the calendar. That last row is the one that sizes the reserve.

For calibration only: JPMorgan Chase Institute analysed over 470 million transactions across 597,000 small businesses and found the median small business holds 27 cash buffer days; the median business in a low-wage industry such as Restaurants or Retail holds 19; the bottom quartile holds 13 or fewer. The median restaurant is 19 days from zero. That's the industry Vivere is entering three times at once.

Three rules I don't need the number to start on:

  1. Compute buffer days weekly — cash on hand ÷ average daily cash outflow. I need to set the floor now, in daylight, along with what happens when I hit it: freeze discretionary spend, pause the liquor and production phases, re-sequence.
  2. Arrange credit while I don't need it. Mimi's is debt-free — that's exactly the balance sheet that gets approved, and it won't stay that way once three ventures are consuming capital.
  3. Separate the reserve from operating cash, in a different account. Reserves visible in the operating balance get spent on opportunities.

And build a 6-month weekly cash projection, not a P&L — Sept 1 through Feb 28, opening balance, weekly in, weekly out, closing balance. If any week goes negative, that week is the real launch constraint.

Source: 10-blindspots.md

High"Debt-free" and a live $85,000 loan file can't both be true until I get an answer in writing

I've been describing Mimi's as debt-free. But the November 2025 workspace file has a section headed FUNDING REQUEST$85,000, BSide Capital, use of funds: equipment, facility, working capital — backed by an entire folder of two-year projections, a lender email summary, an audit report and an expense categorisation, plus a personal financial statement and a personal tax return.

I haven't recorded anywhere whether that loan was funded, declined, or withdrawn, or whether a personal guaranty is outstanding. A February 2026 document reportedly concluded that business loans "were not viable" — is that the outcome of this application, or a separate conclusion? It changes every capital option beneath it, so I need to nail this down.

The trailer raises the same class of question. I've been saying it's owned and in hand — good, that removes the largest single line. But: how did I pay for it, through which entity, and is it encumbered? If it's financed, the lienholder has a say in where it's parked and what insurance it carries.

And I've got at least five trailer revenue figures in circulation, one of them at a financial institution — see §16. None of them describes a fixed courtyard operation Sun–Thu with its own savoury concept, free for events Fri–Sat. All of them are obsolete for that reason.

I need to write a one-page retired-numbers register: every figure, with a verdict — KEEP / REBASE / DELETE — and a one-line reason. Both source PDFs will keep getting forwarded for years, and the register is the only thing that can travel with them.

Source: 10-blindspots.md

HighI haven't stated a financial objective, and I haven't written the do-nothing counterfactual

The payroll summary for 2025-01-01 to 2025-10-30 records:

LineAmount
Joe Sutliff (Contractor)$29,740
Naomi Sutliff (Contractor)$23,400
Seven W-2 employees, combined~$22,545
Total payroll cost$75,685.10

The same file set records that we work 60+ hours a week each, with a stated target of $20/hour each. Annualising the ten-month owner figure gives roughly $63,800/year combined; against 120 combined hours a week over 52 weeks that's approximately $10.20/hour each.

The finding isn't the hourly rate. It's that across eighteen documents and roughly 1.1 million characters of analysis, I've never once written down what this expansion is for, in numbers. No target owner income. No payback period. No target enterprise value. I'm launching four business units with no stated financial goal.

The uncomfortable consequence, which is exactly why I need to write it down: if the objective is to move the two of us from roughly $10/hour to our stated $20/hour target, there are cheaper paths than launching four business units on someone else's property. A price increase across a menu that hasn't moved in two years, or converting the existing 5–10 events a month into a properly priced catering line out of the existing kitchen, would each get partway there with a fraction of the capital, the risk and the counterparty exposure.

I've never made that comparison, and it's the one a good advisor would insist on before anything is signed.

Two sentences I need on one page, before the Aug 17–23 meeting:

  1. "This expansion succeeds if, by [date], it produces [$X] of owner distributions and [$Y] of enterprise value." Naomi — you set the numbers. Nobody else.
  2. "Over the same period, the two units we already have produce [$Z] if we spend the same effort on price, catering and wholesale from the existing kitchen."

If the counterfactual wins, that's not a failure of the analysis — that's the analysis working.

Source: 20-blindspots-v2.md
15. Disclosures

ScopeFour things that are cheap for me to disclose now and corrosive to get caught on later.

MediumThe disclosures I owe before the room — better volunteered than discovered

Four items that are cheap to disclose now and corrosive to get caught on later. Each one builds credit I'll need for the harder terms.

1. I wear three hats. I'm simultaneously running the web and marketing agency, the food trailer brand, and the catering company. If the agency does — or is ever asked to do — marketing work for the Delta Roadhouse itself, I'm on both sides of the table. I need a plain-language paragraph in the agreement stating which hat I'm wearing in this relationship and whether agency services for the Roadhouse are included, separately contracted, or excluded.

2. I may already cater at a competitor of their event centre. The investor deck claims a Longhorns & Lace partnership (40 weddings per peak season) — I still haven't verified that, and I need to. If it's real, TW and Miles need to hear it from me. This compounds with a structural fact stated bluntly in the research: using the Roadhouse's kitchen to service its competitors will be visible, because the food leaves through their door, and it puts the commissary agreement at risk. The right shape is a written off-site lane plus a referral economic on outside work, negotiated openly — not an arrangement they discover from a wedding photo.

3. The October 2–4 collision. Cedaredge Applefest (30,000+ attendees) lands on the same weekend as a Delta Panthers home game and the Roadhouse's own Stray Grass and Mountain Jam shows. Applefest wins on arithmetic and the trailer won't be on campus. I need to tell TW and Miles weeks ahead, not the week of. Small item, large credibility return.

4. The September 1 date. If I promised it externally — to TW and Miles, to a vendor, publicly — then reframing to October has a real credibility cost, and getting ahead of it proactively is worth more than the date was. If it was only ever an internal target, moving it costs nothing. I need to establish which it is before the meeting, because it determines whether the first item on the agenda is a correction or simply a plan.

Source: 19-master-plan.md
16. The three retired revenue models

ScopeNone of them goes into the room, into the shared report, or into a rent conversation, in any form.

CriticalNo numbers into the room — how I negotiate rent without a model

This is the single easiest way I could lose credibility in this negotiation, and it would be entirely self-inflicted.

Three conflicting trailer financial models exist, and two of them sit in my own files: $75,000 base build versus $40,208 total startup; Year 1 $52,000 versus roughly $160,000 implied. Separately, the February 2026 five-year projections are dead with Ouray — roughly $775K of the ~$1.1M Year 1 total came from Ouray — and I need to rebuild them from zero, not adjust them. And the November 2025 touring model's event-revenue table is built on a premise (a touring truck) that's been formally retired, so it can't carry into anything.

There are at least five trailer revenue figures in circulation:

The lowest is a factor of 3–10 below the others, and it's the one an outside institution has on file. All of them are obsolete for the same reason: none describes a fixed courtyard operation Sun–Thu with its own savoury concept, free for events Fri–Sat.

I need to retire four "reusable" constants in the same pass, because they look neutral and will get misapplied: the $387,763 Colorado food-truck median revenue (a statewide survey of full-time operators working the Front Range circuit — no relationship to a courtyard in Delta); "typical day $1,000–$2,000" (at a $15–18 ticket that's 55–130 covers per service, against a store that averages about 18 orders a day); the 5% event-capture rule (valid only for the Fri–Sat off-site lane — precisely the days the trailer is not in the courtyard); and the ~$28K/yr fixed overhead figure (built for a touring unit — a parked unit deletes fuel, towing and event fees and adds courtyard fee, shore power, trash, restrooms, winterisation and snow removal).

None of these are going into the room, into the shared report, or into a rent conversation. Letting TW and Miles find two of them would cost more credibility than a slipped date ever would — and a rent number anchored to a projection I later disown is very hard to renegotiate downward.

Before the rent conversation: I need to mark one model authoritative and the other superseded, in a single dated file (see the retired-numbers register in §14). Until that exists, my correct answer to "what do you expect to do in sales?" is that the model is being rebuilt and the number will be shared when it's real. That's also the honest answer, which is why it holds up.

And the structural point that makes this survivable: a hybrid base-plus-percentage rent over a natural breakpoint lets me agree a rent without publishing a revenue forecast at all. I'd be negotiating a rate and a breakpoint formula, not a projection. That's the reason to push for the hybrid structure quite apart from its cash-flow benefits — it's the structure that doesn't require me to have a number I don't yet have.

Source: 19-master-plan.md
17. Operational single points of failure

ScopePeople, equipment, licences and suppliers — four more single points of failure I haven't covered in the negotiation sections, plus the one dependency that runs the other way, toward me.

CriticalPeople: the three of us are the entire redundancy plan, and it's already over-subscribed on paper

The binding constraint on this campus isn't cash, equipment or demand. It's labour-hours from Tyler and me, and it binds before everything else.

Tyler and I are both named as operators of two ventures each. I'm also carrying all marketing, all web, all reporting, the POS and tooling, the partner-facing documents, and a separate agency business on top of that. Naomi is a third principal but she's fully committed to 320 Main, which is open seven days a week — she is not spare capacity.

Here's a normal Friday in the current plan, with nobody sick:

Five simultaneous demands, three principals, one of whom can't leave Main Street. That doesn't require bad luck.

The failure impact isn't symmetrical:

At least one of the three of us being unavailable for a stretch over any 12-month window isn't a risk — it's a scheduled event with an unknown date.

The redundancy plan is one hour of work and I haven't done it: the second-name exercise. For every cell in the coverage grid, I need to name the person who covers it and the person who covers them. Any cell with one name is a launch risk.

Then four cheap follow-ons I still need to knock out: certify at least two, preferably three, Certified Food Protection Managers; get two holders for every credential — keys and codes, POS admin, bank and merchant accounts, domain and hosting, socials, the insurance broker, the county EH contact; state a fallback for the marketing function, even a low one; and Naomi — I need us to write down who decides if you're unreachable: who signs, who spends, up to what limit.

The earliest warning signal is free to read: consecutive days worked, by named person. Past 12 consecutive days, we're running on borrowed time rather than capacity. The second signal is tasks migrating into the 10 PM–1 AM window.

And I need to plan for churn, not retention: the BLS JOLTS accommodation-and-food-services quits rate was 4.3% in March 2026 — the highest of any tracked industry and close to double the private-sector average. A staffing plan with no turnover assumption fails in month four.

Source: 27-bottlenecks-redundancy.md

CriticalLicences: four permissions, none of which I hold, all revocable by one counterparty

I'm bringing capital, brand and labour onto someone else's real estate, someone else's kitchen, someone else's courtyard, and someone else's liquor licence. Four of the five shared resources are revocable by one party, and none of them is on paper yet — see §7–9 for the negotiated fix. This is the operational summary of why it matters as a single-point-of-failure question, not just a contract question.

The commissary is the most dangerous of the four, because it's not merely where I prep — it's what makes the trailer legal. If the Roadhouse kitchen isn't today a licensed Colorado retail food establishment in a class that can serve as commissary for a third-party mobile unit, I can't sign the agreement, I can't submit the plan review packet, and September is over for the trailer — regardless of anything else. (Note: the research files carry two different EH numbers — (970) 874-2165 and (970) 874-2168 with eh@deltacountyco.gov. I need to try both.)

The liquor licence has no redundancy, only compliance and separation. "Under the umbrella" is not a structure Colorado law recognises. The live exposure is the under-21 prong, which has no intoxication element — in a venue whose primary customer is a child, that's the realistic failure. Enforcement outcomes in published summaries run from 5 days served to 20 days with part held in abeyance; a revocation isn't restorable on any useful timescale. And if the suspension shuts the building, the commissary and the premises go with it.

Three questions I still haven't asked, all yes/no:

  1. Is the Roadhouse a Responsible Vendor Program designated licensee? If yes, every Mimi's employee who touches a liquor-based treat inherits a mandatory training clock — a large, currently unbudgeted staffing consequence.
  2. Who employs the person who serves a liquor-based treat — Mimi's, the Roadhouse, or dual-badged? That determines who trains them, who supervises them, whose insurance covers them, and whose licence dies if they over-serve.
  3. Where does the licensed premises boundary physically run, and is it marked? A guest carrying a drink into an unlicensed courtyard is a violation.

The contractual redundancy I need for all four rights is the same short list: notice-and-remedy on any regulatory action touching either party's food or liquor licence, offered symmetrically; notice periods that exceed the longest booking horizon plus a wind-down right; successor and assignment language so a sale isn't a termination; confirmation of the entity chart before signing; and the right to name a backup commissary without breaching exclusivity. Identifying that backup costs one afternoon and converts an existential dependency into an expensive inconvenience.

Source: 27-bottlenecks-redundancy.md

HighEquipment: one machine, one address, three revenue lines, and I don't know who fixes it

Production equipment. In the target end-state — production at the Roadhouse — the batch freezer and the hardening freezer that supports it are a single point of failure for Mimi's #1 retail, Mimi's #2 retail, and all wholesale simultaneously. Nothing in my research on disk records what equipment Mimi's actually runs: no make, no model, no capacity. And the number that matters most, I don't have: who is the nearest qualified service technician, what is their response time, and what is the parts lead time?

Freezer capacity — I've never measured it, at either site. Wholesale capacity is capped by the smallest freezer in the chain and I don't know which freezer that is. A tape measure and a thermometer turns four unknowns into numbers in an afternoon: usable cubic feet and actual holding temperature, per unit, per site. Processors are advised to hold at roughly −13°F to −22°F with minimal variation; temperature cycling is worse than storage at a constant high temperature, and the damage shows up months later as customers saying "icy," "grainy," "not like it used to be."

The trailer. One owned unit. A mechanical, refrigeration, generator, fire or theft event takes 100% of Vivere Colorado's revenue, and a total loss takes months plus a new plan review — a replacement unit is a new application, not a swap.

The cheap mitigations, none of which I've put in place yet:

Source: 27-bottlenecks-redundancy.md

HighSuppliers: I haven't named a single one anywhere in the research

No supplier appears by name anywhere in my research. Not the dairy or cream supplier, not the primary broadline distributor, not the bun bakery, not the beef supplier, not the CO₂ or propane vendor. The business runs on relationships that exist only in one or two people's heads — a supplier risk and a key-person risk at the same time.

The dairy supplier is the one that matters most: it stops the ice cream business, and the ice cream business is the brand.

Five things I need to do, in order of how cheap they are:

  1. List them and rank them by "what stops if this stops." One page. It doesn't exist yet and it should.
  2. Open a second account, dormant, for every single-source item. Opening an account under pressure takes days I won't have; opening one in advance takes an afternoon.
  3. Test the backup before I need it, and record the result. The specific hazard in ice cream is substitution risk — a different cream, a different stabiliser, a different base performs differently. A backup I've never run is a hope, not a plan.
  4. Establish the actual delivery days and cutoff times. Delta isn't on a daily-delivery grid for every distributor.
  5. Interrogate the menu for single-source exposure. The brioche sesame bun, the specific beef blend, the gochujang, the cashews — each is a menu decision with a supply-chain consequence.

The same discipline belongs in the wholesale agreements: supply-interruption language, minimum-order and lead-time terms, a price-adjustment mechanism tied to input costs, and no volume commitment that exceeds what the redundancy plan supports.

Source: 27-bottlenecks-redundancy.md

MediumThe one running the other way: Mimi's is the arcade's on-switch

Every other dependency in this programme runs from me toward the Roadhouse. This one runs the other way, and it's the one where I am the single point of failure for the partner.

The brief states it plainly: "The arcade opens when Mimi's opens. Mimi's presence extends the arcade's operating days from two to seven." That's the value I deliver and it's central to my negotiating position (§2).

The exposure it creates: if Mimi's at Roadhouse can't open on a given day — a sick call, a staffing gap, a supply failure — the arcade doesn't open either, and the Roadhouse's customers are the ones who find a locked door. Every staffing failure on my end becomes a Roadhouse customer-service failure, and it lands hardest in exactly the weeks when the labour constraint is tightest — opening month.

Four fixes, all free:

  1. I shouldn't promise seven days until the coverage grid has two names in every Mimi's #2 cell. Promise five, deliver five, expand to seven.
  2. Define the arcade commitment as stated hours, not "whenever Mimi's is open."
  3. Agree explicitly what happens when Mimi's can't open — can Roadhouse staff open the arcade independently, and is there a key or alarm arrangement?
  4. Write the exclusivity down alongside it. Mimi's replaces the arcade's existing snacks-and-ice-cream offering — the right and the duty belong in the same paragraph.
Source: 27-bottlenecks-redundancy.md
18. Failure modes nobody has named

ScopeFive things I noticed that don't show up in any single research file, because each one lives in the gap between two of them.

HighThe labour constraint eats the marketing that fixes my demand constraint

This is the feedback loop most likely to bite me slow and confusing rather than loud and visible — and I've never named it as a loop until now.

The campus has two different constraints on different days, and I almost missed planning for that:

Now watch the loop close:

  1. Labour is my binding constraint, and it binds structurally every Friday and Saturday.
  2. The first thing I let go is my own marketing output, because it's the most deferrable thing I own.
  3. But my marketing pipeline is the Sun–Thu demand engine. On a dark campus the trailer isn't capturing traffic — it's originating it.
  4. Weeknight covers fall. My instinct is to respond by adding capacity — more hours, more menu, more staff.
  5. That's spending into a demand constraint. It turns a marketing problem into a labour and cash problem, which tightens the labour constraint further, which starves marketing further.

Two instruments break the loop, both free:

I need to watch posting cadence as a labour indicator, not a marketing one. When content stops, the constraint has bound — days before it shows up in revenue.

I need to give the marketing function a floor, in writing. Blocked hours that operations may not raid.

And I need to write the decision trigger now, while it's cheap: "weeknight covers flat for three consecutive weeks → cut to Thu–Sun. Do not add hours, menu, or staff." Four good nights beat five thin ones.

One free partner-facing signal worth me reading weekly: the Roadhouse's own published events page. Any Sun–Thu programming appearing there is the strongest possible confirmation that the seven-day campus strategy is real. Its continued absence is the strongest possible signal that it isn't.

Source: 27-bottlenecks-redundancy.md

HighThe trailer stops being mobile — and a movable asset becomes a leasehold improvement on land I don't own

Nobody's named this one yet, and it's the quiet way the concentration risk becomes permanent.

I chose the trailer over a truck for two reasons that were both arguments about optionality: a dead tow vehicle can be swapped where a dead truck engine kills the business, and a trailer holds resale value. It's designed as a two-window mobile unit targeting the Colorado festival and brewery circuit.

Now I need to think through what a permanently-sited courtyard operation does to it. If the unit gets hard-plumbed into courtyard shore power, a potable connection and a greywater or grease dump — and if Delta County classifies a permanently-sited unit as a fixed establishment rather than a mobile one, a question that's still open — then it stops being mobile in practice and in law.

I'll have spent a movable, saleable, financeable asset to create a leasehold improvement on land I don't own. And I'll have done it to the one thing on the balance sheet that could physically be driven away from a failed relationship.

I need to preserve mobility as a deliberate engineering constraint, not an afterthought:

There's also a fixed-site upside worth stating: a trailer that doesn't tow doesn't break down on the way to work. The point isn't to avoid the courtyard — it's to avoid becoming unable to leave it.

Source: 20-blindspots-v2.md

HighThe labour constraint manufactures the food-safety incident, and the 4.9 doesn't come back

A short chain, and one of the links is the constraint I keep finding everywhere else in this document.

The mechanism: a business short of labour pressures sick staff to work. A sick food handler is the most common cause of a customer illness complaint. A foodborne illness cluster lands on Mimi's 4.9/5 across two locations, Vivere Colorado's brand-new zero-history reputation, Vivere Catering's entire value proposition, and the Delta Roadhouse's licence — at the same time, because they share a lot, a kitchen, and in the customer's mind a single address. In a town this size, reputational events don't stay in their lane.

Operationally the damage is days. Reputationally it's 12–24 months, and the 4.9 may never come back. The compliance file puts it exactly right: the liquor licence is replaceable; the 4.9 is not. This is the highest-severity uninsurable risk on the campus.

The single highest-yield mitigation is a piece of paper I need to write before the pressure exists: a written employee health policy with exclusion and restriction rules, signed by every employee — Colorado's rules require reporting of specified illnesses including Norovirus, E. coli O157:H7, Hepatitis A, Shigella and Salmonella. I need to write it before the labour pressure exists, and the principals — starting with me — have to be the ones who visibly go home sick first. A policy the owners break isn't a policy.

The supporting controls, in order of value: CFPM coverage at every establishment, with a certified backup; temperature logging at every hand-off; allergen control across two very different production types in one commissary (ice cream's dairy/nuts/egg and savoury's wheat/sesame/cashews sharing a room is a real cross-contamination problem, not a formality); monthly mock inspections against the county checklist; and a pre-agreed incident-communication protocol across all three brands and the Roadhouse, agreed with TW and Miles before anything happens.

And one rule that saves the brand more often than any of the above: when in doubt on ice cream, dump it. Safe to sell isn't the same as fit to sell under a 4.9-star brand. The product is cheaper than the review.

Source: 27-bottlenecks-redundancy.md

HighPrice rejection read as a marketing failure — I haven't checked whether Delta will pay for this menu

I searched all eighteen documents for price point, willingness to pay, and median income. Zero hits. The menu has an equipment analysis, an allergen analysis, a sourcing analysis and a food-safety analysis. It contains no price. Not one document anywhere has a single competitor price check.

The v1 menu is smash burgers on brioche sesame-seed buns with caramelised onions; triple-cooked tallow fries; a half-pound smoked-then-seared burger with garlic aioli and Pecorino Romano; a gochujang chicken cashew salad.

That's a Front Range menu. Tallow, Pecorino Romano, brioche, a half-pound smoked patty and a three-stage fry process are a cost structure, and cost structures set prices.

Against that: Mimi's own pricing runs mostly $6.00–$9.75 per item at an average order of $15.99, and the business describes itself as "$15–25 per family." Delta's median household income is approximately $45,250 with a poverty rate around 20.5% (Data USA, 2024 ACS-derived).

So the trailer would be asking one person to spend roughly what an entire family currently spends at Mimi's — on a campus that's dark, on a Tuesday, in a town where one household in five is below the poverty line.

It may still work — Delta gets US-50 traffic, Grand Mesa and Black Canyon tourism, and there's genuinely no competing product locally. But I haven't checked.

The failure mode isn't that the menu is too expensive. It's that price rejection is indistinguishable from weak marketing at the covers level, and my instinct when covers are weak is to spend more on marketing — which burns cash and principal hours against a problem marketing can't solve.

Three things I need to do before the menu is locked (which plan review requires anyway):

  1. Price-check every burger sold within fifteen miles — both Delta Dairy Queens, the Roadhouse's own BBQ menu, the Montrose operators.
  2. Set a target price per item and a target tickets-per-night, then multiply, and compare against a realistic dark-weeknight courtyard.
  3. Consider a deliberate two-tier menu: a lower-priced single smash burger a Delta family of four can afford on a Tuesday, and the Smoke Burger as the scarcity item.

I need to take the price question to Naomi. She has priced for this town for two years and is the only person in the programme with that data in her head.

Source: 20-blindspots-v2.md

MediumAn SSN is sitting inside a deployable repository with git auto-deploy enabled — I need to fix this first, ahead of everything else in this document

This one isn't strategic. It's a five-minute fix that's permanent if I get it wrong, and it belongs in the internal build because naming the files publicly is itself part of the exposure. Given the severity, I'm treating this as the single most time-urgent item in the entire document — everything else here can wait for Aug 17–23; this can't.

In about ten minutes of looking through the project tree, I found: a personal Form 1040 package containing a Social Security number and home address, a personal financial statement, a full lender package, and seven named employees' individual gross and net pay. A further ten confidential documents sit in the catering agreements folder.

The same repository has a documented history of exactly this class of accident: `git add -A` sweeping up `.env` despite `.gitignore`, and Cloudflare Pages git auto-deploy enabled on the repo, bypassing the build script — which is the script that performs the leak check.

The precise gap: the build script's leak guard checks ten known-sensitive filenames. It doesn't know about the tax return. What's actually protecting me today is that the build excludes `.pdf` by extension — that's one edited line away from not being true, and the git auto-deploy path skips the build entirely.

Four things I need to do:

  1. Move the marketing/financial folder and the catering agreements folder out of the repository tree entirely, to a location that isn't inside any deployable project. That's the whole fix.
  2. Verify today whether the Pages git integration still auto-deploys.
  3. Store or redact the SSN-bearing copy appropriately.
  4. Never put per-employee compensation in a partner-facing document, regardless of the business logic for including it.

And the related discipline for this report: the landlord must not see the margin, the equity figure, the growth targets, the loan appetite, or the fact that a business valuation and franchise prospectus exist. A landlord who learns my margin prices rent against it; a landlord who learns I commissioned a valuation draws conclusions about my intentions. That's exactly why I'm keeping this build separate from the shared one — and why nothing in this document goes anywhere near the other.

Source: 20-blindspots-v2.md
19. Future expansion — a second truck, different cuisine

ScopeMy own note, added 2026-08-13: a wood-fired pizza truck as the diversification move §3 and §17 argue for — not a bigger bet on the same lot.

§3 and §17 both land on the same conclusion from different directions: the trailer is currently 100% of Vivere Colorado's revenue, and it's about to be permanently sited on a lot the family doesn't control. A second mobile unit, in a different cuisine, is the actual fix for that concentration — not an unrelated growth idea bolted on afterward. I'm capturing it here so it doesn't get lost, and sequencing it honestly against everything else in this document.

Why wood-fired pizza specifically fits

It doesn't compete with anything already being negotiated. The burger trailer already needs a non-compete carve-out against the Roadhouse's own BBQ menu (§8, exclusivity). Pizza sits outside both the burger and BBQ categories — no exclusivity fight required to add it, on this campus or anywhere else.

Margin structure is friendlier. Dough, cheese and toppings scale cheaply per pie against a $15–25/pie price point; a live wood-fired oven is also the marketing.

It's the strongest fit for the event circuit the trailer's own research already mapped — Cedaredge Applefest, Mountain Harvest Festival, the Palisade wine/brewery corridor (§4 in the shared report's launch campaigns). Pizza is a better-proven pairing at those venues than a second burger operator would be, and it doesn't cannibalise the existing trailer's Fri–Sat event slots — it extends the total number of events I can work in one weekend.

It's a real Vivere Catering upgrade, not just a second truck — a live oven at a wedding is a distinct, higher-price-point line item, genuine differentiation from Longhorns & Lace rather than a repeat of the same package.

HighSequence it honestly — after staffing depth exists, not instead of it

§17 already establishes that the current three-venture plan is labour-constrained on exactly three people with no redundancy. A fourth mobile unit added on top of that, before I've even done the coverage-grid exercise in §17, repeats the same mistake at a larger scale — this is exactly the loop described in §18's labour-eats-marketing item, one more unit heavier.

The clean version: I need to budget this as a 2027-or-later addition, run by a dedicated hire from day one, not by my hours, Tyler's, or Naomi's. That makes it additive to the labour pool instead of a fourth draw on the same three of us, and it gives Naomi a real, separate P&L to justify hiring against — which also answers part of §14's do-nothing-counterfactual question with a concrete alternative use of capital.

Equipment note for later costing: mobile wood-fired ovens are a simpler build than the smash-burger rig — oven, small prep table, small reach-in, no fryer, no hood/UL-300 fight in the same form. Still needs commissary access for dough prep and cold storage, and the fire-code profile is different (open-flame venting, not grease-laden vapor suppression) — a separate call I need to make to Delta County Fire when the time comes, not an extension of the current permitting fight.

Branding note: either a second concept under the Vivere Colorado umbrella, or its own name in the spirit of "The Sidecar at Mimi's" (§8, signage) — something that reads as wood-fire/itinerant rather than reusing the burger trailer's identity, so two trucks read as a small stable rather than one brand stretched thin.

20. What I do next

ScopeThe actual worklist, tiered by whether anything external is holding it up. Built from a live audit of every property, not from memory.

This is the section I'll actually work off. Everything above is analysis; this is the queue.

I audited all five properties against what's genuinely deployed — the trailer site, the Mimi's-at-Roadhouse page, the menu-board system, the social channels, and the brand assets — rather than trusting my own notes. A few things came back worse than I assumed, and they're in the first tier.

How to read the tiers: This week is startable today with no dependency on anyone else. Blocked on others names the specific person or agency I'm waiting on — those are the calls and asks, not excuses. Build queue is my own build work that's real but not urgent this week. Deferred is postponed on purpose, written down so it doesn't quietly creep back into the September scope.

Every build, clickable

These are the actual deployed properties, so I can open any of them while I'm working through the list below. Each URL was verified on August 14, 2026 — real content, not a soft-404. Green is genuinely live, amber is staging or name-blocked.

STAGING

Mimi's at Roadhouse

master.mimis-sweet-treats.pages.dev/roadhouse

Location #2's own page. Staging only — production /roadhouse is still a 404, and it holds 5 TBD chips until the date, hours and menu land.

Open the build →
STAGING · NAME TBD

Vivere Colorado (trailer)

vivere-colorado.pages.dev

Working order-ahead flow, live menu, 3 API endpoints against a bound KV namespace. Deliberately noindexed until the name is locked.

Open the build →
STAGING

Trailer — catering page

vivere-colorado.pages.dev/catering

The second real page on the trailer site. Quote form works; no prices set yet.

Open the build →
LIVE

Menu boards — wall preview

mimis-menu-boards.pages.dev/wall-preview.html

The two-screen board system running the counter at 320 Main. This is the pattern I clone for the Roadhouse counter.

Open the build →
LIVE

Menu boards — Screen A

mimis-menu-boards.pages.dev/boards/MASTER-menu.html

The master menu board itself, full-screen, with the scrolling ticker.

Open the build →
LIVE · PRODUCTION

Mimi's Sweet Treats

mimissweettreats.com

The established brand this whole expansion builds outward from — 320 Main Street.

Open the build →
SHARED REPORT

Delta Expansion 2026 (partner-facing)

delta-expansion-plan.pages.dev

What TW, Miles, Naomi and Tyler actually read. Campaigns and storyboards live in its Part VIII.

Open the build →

THIS WEEK

Startable today — nothing external is holding these up8
Get the payroll/SSN folder out of the auto-deploying repoMe

§18 of my internal report flags a live SSN, tax-return and per-employee-pay exposure sitting inside a repo tree that has Cloudflare Pages git auto-deploy enabled — one edited line from publishing. I need to move that folder outside the repo, confirm auto-deploy status on that project, and verify nothing sensitive is left in history. This is ahead of everything else in the program; it is not lease-week prep, it is a today problem.

Fix the live Mimi's middleware key and the public admin pagesMe

Taking the disclosure out of the shared report did not fix the actual hole. functions/api/_middleware.js on the production Mimi's site still falls back to a hardcoded default bearer key when DASHBOARD_KEY is unset, and flavor-admin, owner-dashboard and connect-bank are still shipping to the public build where anyone who guesses the URL can reach them. I need to remove the fallback, set the env var properly, and keep those three pages out of the public build.

Put every untracked property into gitMe

Four live or near-live things have zero version history and exist only on this machine: the whole Vivere Colorado trailer site (which is live with three working API endpoints and a bound KV namespace), roadhouse.html, the entire mimis-menu-boards project that drives the screens at 320 Main, and both new logo asset sets. I need to init/commit each one properly — and remember the repo root here is my whole home directory, so no blanket git add -A.

Lock the trailer's nameMe

This is the one decision on the critical path that nobody outside is holding up — it is mine to make. "Vivere Colorado" is already my web agency's LLC, with its own blue/teal logo, invoices and service agreements, and the trailer has been carrying the same name since March. Until I settle it I cannot register a domain, claim the social handles, name the Google Business Profile, export an avatar, or print anything physical. Everything in the brand and channel queue sits behind this.

Close the two real holes on the live trailer siteMe

The trailer site has no 404.html, so Cloudflare serves the homepage at HTTP 200 for every unmatched path — every typo and dead link reports success, and that is also why robots.txt, sitemap.xml and favicon.ico all appear to "exist." It also has no privacy notice anywhere, while /api/order is writing customer names and phone numbers into KV today. Neither of those needs the final name. I should commit a _headers file at the same time so the live security headers are actually reproducible from source.

Answer the blocking questions only I can answerMe

Before the lease week I need to clear the items sitting on me: whether the trailer's Type I hood and UL-300 suppression system are installed and currently tagged (a missing tag pushes the earliest legal opening to October or later), whether anyone on the team holds a Certified Food Protection Manager certificate (Delta County will not accept a plan-review packet without it), whether any plan-review packet has already been submitted for the trailer, catering or Mimi's at Roadhouse, and whether the 320 Main lease carries a radius or exclusive-use clause that makes opening a mile away an event of default.

Close the Facebook cross-posting footgun and fix the stale pipeline docsMe

Blotato's Facebook connection still defaults its pageId to Vivere Web, not Mimi's — any post that does not explicitly override it publishes to the agency page. I need an explicit pageId assertion in the posting helper before the next scheduled run. While I am in there, PRODUCTION-GUIDE.md still lists the old Facebook ID, references the banned Instagram account, and says Instagram is on hold, all of which contradict the live workspace. Also worth correcting the TikTok handle everywhere: it is @mimis.sweettreats320.

Site visit with a tape measure and a cameraMe

Two things get harder or impossible if I wait. I need counter-wall and panel-mounting measurements at both the Roadhouse counter and the courtyard trailer position — screen count at the Roadhouse changes the board architecture, not just the layout — and I need the one-shot captures that are unrecoverable after Sept 1: the trailer before it gets wrapped and the Roadhouse space before it fills. There is also not a single Roadhouse photo anywhere, which is why the location page hero is still a gradient.

BLOCKED ON OTHERS

Cannot start until someone else answers or signs9
Get the licensed-premises diagram and the trailer's zoning answer from the CityCity of Delta

Two calls to the same building. The City Clerk at (970) 874-7566 has the approved licensed-premises diagram on file for Delta Roadhouse's tavern license 03-25524, which covers 209 and 215 Ute Street — I need to see whether it already includes the arcade building and the courtyard, because that single document decides whether alcohol needs a full premises modification. Community Development needs to tell me what permit or zoning classification a semi-permanent trailer requires and whether 215 Ute is inside city limits; Title 17 is silent on mobile vendors and silence is not permission.

Waiting on: City of Delta Clerk and Community Development
Confirm the commissary and plan-review path with Delta CountyDelta County

Delta County Environmental Health at (970) 874-2165 / 874-2168 has to confirm the Roadhouse kitchen qualifies as a licensed commissary, tell me whether one commissary agreement can cover both the trailer and Vivere Catering or whether they want two, and answer whether a single-operator courtyard launch fits their special-event framework. Without a signed, valid commissary agreement they cannot issue either license, and the special-event path is the only route whose timeline could actually close before September 1.

Waiting on: Delta County Environmental Health
Call CDPHE about the wholesale registration gap and the dairy-plant questionCDPHE

Two wholesale deliveries are already documented — CQP on Jul 29 and Red Shed on Jul 30, shipped as unlabelled tubs with paper handling sheets — and I do not know whether any wholesale registration exists. Product from an unregistered manufacturer is not an approved source, and the buyer takes the violation, so this is a present-day exposure that costs accounts, not a future risk. I need the Manufactured Food Program on the registration status before the next delivery, and Milk/Dairy on whether our scratch-built base makes us a dairy plant needing in-house pasteurization.

Waiting on: CDPHE Manufactured Food Program and Milk/Dairy Program
Settle the four shared rights in the Aug 17-23 lease weekTW+Miles

Lease agreements and real numbers are due the week of Aug 17-23. I need actual terms for all of it in one document: the demised space in the arcade building, commissary access, courtyard siting, the liquor arrangement, and use of the smoker — plus signage rights on the corridor and the building, exclusivity as the campus food and dessert operator in both directions, a real renewal formula, and a written commitment to the Sunday-Thursday campus being open with restrooms and lot lighting. That last one is the piece that makes every other item moot if it does not happen. Until these land the report keeps carrying placeholder boilerplate and no invented figures.

Waiting on: T.W. Stites and Miles Van Hee
Get written permission for every use of the Roadhouse name and marksTW+Miles

Nothing that uses the Roadhouse name, marks, photography, calendar or customers should publish until this is in writing — that includes the location page, the Google Business Profile at 215 Ute, and the "Roadhouse Smoke Burger," which puts their brand name on our product. I also need their answer on whether alcohol can be displayed on a Mimi's-at-Roadhouse board at all and during which hours, since that is the licensee's call and not something I can infer.

Waiting on: T.W. Stites and Miles Van Hee
Get the Mimi's at Roadhouse opening date and hoursTW+Miles

The location page is built and sitting on staging with five visible TBD chips — opening date, hours, the expanded food menu, and the 21+ details. The page correctly refuses to invent them, and I am not pushing a location page to production when its two most-searched facts are amber placeholders. The date and hours depend on the campus commitment and on how Mimi's hours sit relative to arcade hours, so this comes back with the lease terms.

Waiting on: T.W. Stites and Miles Van Hee, plus the arcade hours question
Get Naomi's signed menu, prices, and written brand sign-offNaomi

I need the trailer's v1 menu locked and signed with prices — not "flexing" — because the health-department packet cannot go in against an unfinalized menu and no menu board can ship without a signed price list. Separately I need Naomi's agreement in writing to the brand extension, to Mimi's at Roadhouse becoming the flagship, to the production move, and to her name being associated with alcohol. It is her name and I cannot implement any of it on my own, and with the LLC 50/50 and no operating agreement there is no tiebreaker if we disagree. Nothing on record says whether she even wants the brand selling alcohol — I should ask before spending money on legal work.

Waiting on: Naomi
Get an attorney on the entity structure and the alcohol structureAttorney

"Under the Roadhouse umbrella" is not a structure Colorado recognizes, and CRS 44-3-301(3)(a)(I) cuts both ways — it would expose their license as well as us. I need counsel to pick a real structure from the four that exist and to sort out which entity is which: Mimi's Sweet Treats, the trailer, Vivere Catering, Mimi's at Roadhouse, and the agency, who signs each Roadhouse agreement, and whether Vivere Colorado LLC is back in good standing with the Secretary of State. Also need TW's identity confirmed for the tied-house cross-ownership check.

Waiting on: Colorado liquor and business counsel
Price liquor liability coverage before anyone pours anythingInsurance broker

Standard general liability categorically excludes liquor claims and umbrellas frequently carry their own exclusion, so Mimi's current policy almost certainly covers none of this. I need a broker to quote a standalone policy or a CG 24 08 endorsement, and I need to know whether the Roadhouse's own carrier will even permit our staff to serve — if they say no, the entire boozy-treat line disappears regardless of licensing.

Waiting on: Commercial insurance broker and the Roadhouse's carrier

BUILD QUEUE

My own build work — real, but not this week4
Build the Roadhouse menu boards off the existing 320 Main systemMe

The board system at 320 Main is live and solid, and the spec is explicit that I reuse it rather than design a new one. Eight of the eleven rotation boards already work on dark ground for a tavern room; V2-avalanche, B3-flavors and B5-story are the light ones to exclude or reskin. I also need to generalize B11-neon's existing hours gate into day/evening/closed programs, and fork B12-marquee into a curated "Tonight at the Roadhouse" board. Structurally buildable now, content gated on the signed price list — and I should confirm the building's wifi before I rely on clock-driven day-parting.

Waiting on: Signed price list from Naomi for content; screen count and wifi at the Roadhouse
Produce the print, signage and social asset set for both brandsMe

There is no vector source anywhere for either brand — everything tops out at 1600px raster, which will not survive a trailer wrap, counter signage, or printed menu panels. The Mimi's at Roadhouse set is not blocked by anything: established brand, locked colors, four sound PNGs, so I can vectorize it and build the print, signage and social kit now. The trailer set has to wait on the name for anything physical, though I can still fix the emblem — it has no light-ground version and is currently invisible against the cream body on line 1103 of the report — and cut a favicon and square avatars off the working mark.

Waiting on: Trailer name for anything printed; nothing for the Mimi's set
Stand up the trailer's channels and content pipelineMe

There are zero social accounts for the trailer, for Mimi's at Roadhouse, or for Vivere Catering — only Mimi's existing three platforms and my agency accounts. Once the name is locked I need the Facebook page, an Instagram Business account linked to it, TikTok, both Blotato connections, the Google Business Profile (service-area for the trailer, storefront for Mimi's at Roadhouse), and a forked brand.py plus the card and video scripts. Mimi's at Roadhouse needs no new accounts at all — it rides the existing stack and just needs calendar entries, a location tag, a Story highlight and a sixth content pillar.

Waiting on: Trailer name; Blotato plan headroom unverified
Put access control on the internal report once real numbers landMe

delta-expansion-internal.pages.dev is noindex but has no access control, and I accepted that risk while everything in it is placeholder. The moment real lease and financial figures replace the placeholders — which is the Aug 17-23 week — those numbers are sitting on an open URL. Cloudflare Access email-OTP is about five minutes of work. I am writing this down so it does not quietly become permanent.

Waiting on: Real lease and financial figures arriving

DEFERRED

Deliberately postponed, so it does not creep back in2
Alcohol moves to phase 2 — plan a dry soft openMe

A premises modification runs on DR 8442, local approval before state, against 30-day posting holds and two-to-three-month norms, and no bridge exists — special event permits are nonprofit-only, the entertainment-district bill lost 32-31 in April, resort-complex needs a 50-room hotel, and a mobile trailer can never hold a Colorado retail liquor license. I am treating alcohol by September 1 as not achievable and opening dry. The 21+ section stays on the page as "coming soon" and no board displays alcohol until the licensee says it can.

Waiting on: Premises modification timeline; deliberately postponed
Wholesale and manufacturing relocation slips to Q4 2026 / Q1 2027Me

Early September is a no for moving production. Our base is built from scratch, which under 21 CFR 135.110 still yields an unpasteurized mix, and that puts us on the high-burden side — possibly a licensed dairy plant and an in-house batch pasteurizer. Retail at the Roadhouse supplied from 320 Main is fine and decoupling the two costs almost nothing while removing a large risk from September. The one cheap thing I should still do during buildout is lay out the Roadhouse utilities — drains, hot water, power — to accept a batch pasteurizer even if one never goes in, because retrofitting later costs many times more.

Waiting on: CDPHE dairy-plant classification; deliberately postponed to Q4 2026 / Q1 2027
Property / assetStatusWhere it stands
Vivere Colorado trailer site (vivere-colorado.pages.dev)PreviewTwo real pages (index + catering) plus three working API endpoints and a bound KV namespace, live and matching local byte-for-byte. Deliberately noindexed until the name is settled. Missing 404, robots, sitemap, canonical, og:image, favicon and any privacy notice; not in git.
Mimi's at Roadhouse location page (roadhouse.html)Staging348 lines, complete and on-brand, live at master.mimis-sweet-treats.pages.dev/roadhouse and 404 on production. Five visible TBD chips (date, hours, food menu, 21+ details). Staging is serving a build one revision old and the three roadhouse logo assets 404 there. Untracked in git.
Mimi's Sweet Treats production siteLive13 pages live. Footer credit fix and the Roadhouse nav wiring are on staging only, not promoted. Carries the unfixed middleware hardcoded-key fallback and three admin pages in the public build. Roadhouse is not in the sitemap.
Mimi's menu boards — 320 Main (mimis-menu-boards.pages.dev)LiveScreen A master menu plus an 11-board Screen B rotation across 7 surface packs. All 24 audit findings resolved and deployed. USB fallback drives are stale versus live, and the whole project is untracked in git.
Mimi's at Roadhouse menu boardsUnstartedEmpty folder. A case-insensitive search for "roadhouse" across the entire board system returns zero hits. Spec exists and says reuse the dark surface packs; day-part switching code and the Tonight at the Roadhouse board are unwritten.
Trailer menu panels (print)UnstartedPrint is the primary recommendation over a TV — consumer panels run 250-300 nits against the roughly 2,500 needed outdoors. No artboards, no bleed or trim setup, no CMYK. Print vendor lead time against Sept 1 is unverified.
Mimi's at Roadhouse logo setDraftFour clean RGBA PNGs with correct brand inks. The white reverse works fine on dark ground — it just reads as a wash if previewed on white. Still carries 230 gold pixels so it is a two-color reverse, not a true one-color. No vector, no favicon, no square avatar.
Trailer logo setDraftReal flame-badge marks with a genuine light/dark wordmark pair, sitting in the report assets folder in a duplicated nested path. The two emblem files are pixel-identical, so there is no light-ground emblem — and it is currently placed on the cream report body where its wordmark disappears. Not used by the trailer site at all, which renders the name as CSS text.
Shared partner report (delta-expansion-plan.pages.dev)Live27 sections. Two boundary-breach passes done and verified clean, including a live security disclosure that had to come out. Grep the leverage terms before every redeploy, and read the whole file — grep alone missed the second pass.
Internal report (delta-expansion-internal.pages.dev)Live19 sections in my own first-person voice, on its own Cloudflare project so there is no traversal route from the shared report. Noindex but no access control, accepted while the figures are placeholders. Regenerate via _docs/build-report-internal.py.
Trailer social accounts and BlotatoNoneZero accounts for the trailer, Mimi's at Roadhouse or Vivere Catering. Both Media Channels folders are empty shells with no channels.json entry, no forked scripts and no video projects. Blotato's Facebook connection still defaults to the agency page.
Mimi's social channelsLiveFacebook page, Instagram @_mimis_est2024 and TikTok @mimis.sweettreats320 all connected and operational — and per the plan this is the vehicle for Mimi's at Roadhouse too, so that unit needs content, not setup.