『The Cold Side』のカバーアート

The Cold Side

The Cold Side

著者： FermentIQ
無料で聴く

【Amazonプライム会員限定】今ならプレミアムプランが4か月 月額99円。

10月19日まで。※適用条件あり
An AI hosted podcast from FermentIQ covering real brewing topics from real breweries.2026 FermentIQ Inc. 博物学 科学 自然・生態学
エピソード
  • Water Is a Cost Line

    Water Is a Cost Line
    2026/10/16
    Water is a cost line: about $290 a year from a full point of water-to-beer ratio, water and sewer only, and excluding the energy to heat the water, which is very likely the larger line. Mac and Wren argue over when water stopped being free — you pay for it four times: to buy it, to treat it, to heat it, and to send it down the drain. Wren prices the part she can, on stated assumptions throughout (a 5:1 ratio she explicitly does not assert as an industry average, a combined water-and-sewer rate of $0.012 a gallon, 52 batches a year — $27.90 a batch, about $1,451 a year at that ratio). Mac wins the round: the ratio is not a dial, it is CIP cycles, keg washing, and floor cleaning, cutting it means cleaning less or cleaning better, and a single reading is a snapshot of a number that moves seasonally. Wren concedes both. Tie-in (verified against code 2026-10-16): water treatment is a recognised ingredient category in FermentIQ (water treatment, mineral, salts, acid), the additions sit on the batch at the strike step, and the batch cost calculation sums every batch ingredient's quantity times its cost per unit into the batch's ingredient total — so a costed salt is inside the batch cost, not beside it. Recipes also carry source and target water profiles. Utility metering was killed in verification and is not claimed. Ask BrewBuddy (real question, real account, whatever it says is what you hear): "What was the ingredient cost for the most recent batch, and what went into it?" — captured 2026-10-16 on org 11 (Playground Brewery, is_test=true), site context "FermentIQ Brewery" single-site via the site switcher, browser task with the saved bot login, attempt 1 of 3. CONFIRMATION: BrewBuddy returned the most recent batch's full ingredient breakdown — every ingredient named with quantity, cost per unit from the inventory records, and a line total, summed to an ingredient total and a per-barrel figure — and under "Strike water" it listed Calcium Chloride with its own quantity, unit cost, and line total inside that sum. The answer also states its costing basis honestly (current cost per unit in the inventory records, not necessarily what was paid for the lots). No customer names in the answer (nothing to anonymize). The tie-in is strengthened by the capture: the Hot Side beat's claim (salts as costed recipe inputs inside the batch cost) is exactly what the live record shows, and the post-INSERT beat answers the record directly. Dry Hops: meter the hose to the keg washer before you meter anything else — one hose, one honest count, for one week. And put the salts on the recipe so they show up in the batch cost — the day the treatment has a line in the cost, it stops being a hobby and starts being an input. Last Call: find your last water and sewer bill and divide it by the barrels you packaged that month. Cold Side is from FermentIQ — built by a brewer, fifteen years on the floor, no engineering background, who directed AI coding agents to build the ERP he couldn't buy. It runs the whole operation, grain to glass. The first thirty days are free and you can cancel anytime at ferment-iq.com. PRODUCTION NOTE (2026-10-16): Render initially blocked at the level gate — p10 (the Ask BrewBuddy question turn) at -1.69 dB and p11 (BrewBuddy turn, Amelia, 856 chars) at -2.62 dB vs the -16.60 reference, builder gain clamped at 6.0 dB. Delete + re-run performed; the raw takes are genuinely quiet and failed near-identically. Applied the manual ffmpeg gain repair Jacob approved for Ep10's p12 and Ep11's p10 (threshold unchanged): +1.69 dB on p10 and +2.62 dB on p11, peaks verified at -2.2 dB and -2.6 dB, no clipping. Rebuild: 14 chunks, level spread 0.53 dB (limit 1.50) — PASS. Final 12:06, 11.6 MB. Flagged in the run report for Jacob before publishing.
    続きを読む 一部表示
    12 分
  • Two Weeks, Not Two Months: Onboarding a Cellar Hand

    Two Weeks, Not Two Months: Onboarding a Cellar Hand
    2026/10/09

    Two weeks, not two months: about $2,900 a hire lost in the gap between week three and week eight. Mac and Wren argue over why a new cellar person takes two months before they can be left alone with a transfer — what "trained" even means ("can do it unsupervised and will stop when something is off"), why the confident untrained person is the expensive one, and why the thing Mac calls judgment is mostly a list he never wrote down. Mac concedes it: thirty people's worth of the list, all in his head. Tie-in (verified against code 2026-10-09): the onboarding checklist with due dates, per-employee training records (forklift, hazmat, first aid, food safety) with due dates and completion status, and every batch stage change logged as a written, timestamped sequence on the batch. SOP storage killed in verification — no customer-facing SOP feature exists in the brewery product, so the script claims nothing about one. Ask BrewBuddy (real question, real account, whatever it says is what you hear): "Are there any training records or certifications on file for the team at FermentIQ Brewery?" — captured 2026-10-09 on org 11 (Playground Brewery, is_test=true), site context "FermentIQ Brewery" single-site via the site switcher, browser task with the saved bot login, ask #2 of 3 (ask #1, "What onboarding tasks are open for the team right now?", deflected — no tool lists onboarding checklist tasks). The answer is a truthful deflection: no training records or certifications confirmed on file, no safety standards tracked on the capture org. No customer names in the answer (nothing to anonymize). Per the runbook deflection rule, the tie-in is not strengthened by the capture: the Hot Side beat claims only the code-verified mechanism, and the post-INSERT beat answers the empty record honestly ("On this site it lives where it lives at most breweries. In people's heads."). Dry Hops: have the new person write the procedure as they learn it — the gaps in their draft are the gaps in your training. And let them make the safe mistakes early and on purpose — everybody remembers the mistake they made; nobody remembers the mistake they watched you make. Last Call: write down the CIP sequence for one tank, start to finish, and hand it to somebody who has never done it. If they can follow it without asking you a question, you wrote a procedure. If they can't, you wrote a reminder — to yourself. Cold Side is from FermentIQ — built by a brewer, fifteen years on the floor, no engineering background, who directed AI coding agents to build the ERP he couldn't buy. It runs the whole operation, grain to glass. The first thirty days are free and you can cancel anytime at ferment-iq.com.
    続きを読む 一部表示
    11 分
  • Six Stops, One Truck: Building a Route That Holds

    Six Stops, One Truck: Building a Route That Holds
    2026/10/02
    Six stops, one truck: about $2,100 a year in recoverable driver hours, and only if the recovered time actually gets used. Mac and Wren argue over a real run sitting in the app — six accounts, $1,692 on the truck — on why a delivery day is built out of habit and the order the calls came in, why the truck costs an assumed $289 a day to roll (eight hours, $28 an hour fully loaded, $65 fuel), and why delivery is not a distance problem — it is a time-window problem. Mac wins the round: the paper-optimal route loses to the route that respects when accounts will actually take a delivery. First Runnings: the clipboard version of the real run. Dana at the Copper Mug called first Friday, so the Copper Mug is stop one — driver at eight-fifteen for a ten-to-noon window, forty-five minutes in the parking lot, engine off. Late everywhere downstream: Harbor and Rye at eleven-fifteen, after Priya — the only signer — left at eleven. Ferment and Fork at noon against an eight-to-ten window. Two stops missed, one redelivery later in the week. Two trucks for one week's beer, and the record says nothing. Hot Side: the arithmetic, assumptions throughout. Eight hours at an assumed $28/hr fully loaded plus an assumed $65 fuel: $289 a delivery day. Two days a week, fifty weeks: $28,900 a year to run the truck. Forty-five recovered minutes a day at $28/hr: about $2,100 a year in driver hours — and Wren says plainly what that number is not: not fuel, not truck wear, not revenue, unless the time gets used for another stop. Mac concedes the math outright, then wins: the optimizer's perfect loop puts the driver at Ferment and Fork at ten-thirty for a window that closed at ten, or at Harbor and Rye at one-thirty after Priya's gone. The route that ignores the windows is abandoned by stop three. Wren concedes fully. Then the real stop order, sequenced by the windows: Ferment and Fork first (eight-to-ten), Harbor and Rye for Priya before eleven, the Copper Mug ten-to-noon with Dana and the back door, the Hoppy Monk (side door after eleven, by two), Bottle Theory fifth (call twenty minutes ahead, Fifth Street dock), Cask and Craft last (flexible hours, hand-truck job down the stairs, truck at its lightest). Tie-in (verified against code 2026-10-02, corrected 2026-10-02): the route and the paperwork come off the same record — road-routed ETAs via OpenRouteService, driver signature capture, and vehicle inspection are live in the driver app. LLM stop-ordering (`POST /api/delivery/routes/optimize`) and BOL generation (`POST /api/driver/bills-of-lading/generate`) exist as backend endpoints only, with no UI calling them — not user-reachable, so not claimed as live features. Structured receiving-window modelling does not exist (free-text field only) — the windows stay a human process, and the script claims only that the software holds what you typed. Ask BrewBuddy (real question, real account, whatever it says is what you hear): "What's on the delivery run for tomorrow, and in what order?" — captured 2026-10-02 on org 11 (Playground Brewery, is_test=true), site context "FermentIQ Brewery" single-site via the site switcher, browser task with the saved bot login, attempt 3 of 3 (6 asks total, all consistent). The answer is a truthful deflection: no delivery routes created for tomorrow (2026-10-03), 0 pending deliveries on the capture org — not a technical failure. No customer names in the answer (nothing to anonymize). Per the runbook deflection rule, the tie-in is not strengthened by the capture: the Hot Side beat claims only the code-verified mechanism, and the post-INSERT beat answers the empty record honestly ("Empty is also an answer, as long as it's the true one"). Dry Hops: write the receiving window in the customer record the day you open the account — Dana's window, Priya's mornings, the back door, the side door — not the third time you get turned away. And hand the driver the windows and let him sequence the run once; buy him a beer and write down what he says. Last Call: take your biggest delivery day and write down the receiving window for every account on it. The gaps are your route problem. Every blank is forty-five minutes in a parking lot waiting to happen. Cold Side is from FermentIQ — built by a brewer, fifteen years on the floor, no engineering background, who directed AI coding agents to build the ERP he couldn't buy. It runs the whole operation, grain to glass. The first thirty days are free and you can cancel anytime at ferment-iq.com. PRODUCTION NOTE (rewrite 2026-10-02 ~06:45 PDT): this episode was rewritten around a real delivery route built in the app the same day (org 11; 6 fictional test accounts IDs 545–550 with real receiving-window constraints, 6 invoices INV-869–874, route "Delivery 10/2/2026" PLANNED, $1,692 total; no email addresses on any record per Jacob's rule #0). The v1 script is backed up at FermentIQ_Podcast_Ep10_Script_v1.md. The rewrite's render passed the level gate ...
    続きを読む 一部表示
    11 分
adbl_web_anon_alc_button_suppression_t1
まだレビューはありません