Tag: AI Strategy

  • Standing in the Middle

    Standing in the Middle

    Tygart Media · Notes from the Bot Lab

    One direction gives you something you can point to. The other gives you a wider map. Meaning shows up only where the two have to agree.

    Lens Piece · Free PDF

    Download this article as a PDF

    Keep the full essay, the Floor/Ceiling/Middle infographic, and the linked references formatted cleanly as a PDF.

    This morning I sat down with Chapter 2 of Douglas Hofstadter’s Gödel, Escher, Bach: An Eternal Golden Braid (“Meaning and Form in Mathematics”), right after finishing the MU-puzzle and circling back to the short prelude adapted from Lewis Carroll’s What the Tortoise Said to Achilles.

    In Carroll’s dialogue, Achilles keeps trying to force the Tortoise to accept a conclusion by writing down one more rule as another line in his notebook — and the Tortoise happily accepts every rule and still refuses to budge, trapping them in an endless chain. You cannot push meaning forward by piling more marks inside the same closed system. Something outside has to line up with it.

    Then Hofstadter hands you a tiny formal toy called the pq-system. Strings built out of three characters only: p, q, and hyphens, like ---p--q-----.

    My first reaction was to ask whether the hyphens were just noise I needed to clear away to find the signal. They aren’t noise. They are the count: three hyphens on the left, two in the middle, five on the right. Put ten tarnished brass coins on a sheet of paper with two sticks between them — three coins, a stick, two coins, a stick, five coins — and you see 3 + 2 = 5.

    Ten tarnished brass coins arranged on cream cotton paper beside a terracotta clothbound book, separated by two wooden sticks into groups of three, two, and five
    Three coins, a stick, two coins, a stick, five coins: the marks stay mute until an outside structure lines up with them.

    Here is the catch that stopped me: the coins don’t know they are doing arithmetic, and the hyphens don’t know they mean three, two, and five. Meaning isn’t packed inside the symbols. It lives in the fit — the isomorphism — between the marks sitting on the table and an outside structure that lines up with them.

    That single idea cracked open a frustration I have been carrying for months.

    Why I used to roll my eyes at keynote stages

    I work bottom-up. My week happens inside origin server logs, backup checksums, and request counts — the actual exhaust left behind when systems run. Everything we put into our white paper, Not All Bots Are the Same: 55 Days of Server Logs from One Website, and our log series like My Analytics Said 1,000 Visitors. My Logs Said Otherwise. came from counting raw requests on the server instead of trusting a dashboard estimate.

    Because of that, watching SEO speakers on keynote stages used to drive me crazy. From where I sit, a lot of stage talk sounds like pure top-down storytelling: wide, inferred narratives with nothing you can trace back to a timestamp or a status code. Bottom-up has actuals. Top-down has inference.

    Lens Piece · Free PDF

    Download this article as a PDF

    Keep the full essay, the Floor/Ceiling/Middle infographic, and the linked references formatted cleanly as a PDF.

    Then, halfway through talking out ---p--q----- this morning, I caught my own framing.

    Looking at that string, I realized I might just be the three hyphens on the left — sharp on my own local count, blind to the rest of the equation. The people on stage aren’t living inside one log file, which is precisely why they can hold a wider landscape across variables I cannot see from down inside the requests.

    Neither direction is superior. There is no “better.” Bottom-up gives you something you can point to. Top-down gives you a wider map. If you already have the bottom, you don’t need more bottom — you need to look up. If you only have the top, you don’t need another keynote story — you need to climb down into the ground truth.

    The floor, the ceiling, and the middle where they meet

    I have been calling the two ends the floor and the ceiling.

    • The floor is what actually happened: the 2,838,206 requests in 55 days of tygartmedia.com server logs (Sep 18–Nov 12, 2026), the HTTP status code, the work-order accounting rule where unfinished work stays at $0 until verified (Just a Guy: What Is One Person Worth Now?).
    • The ceiling is what is possible: what AI can do, where retrieval and buyer behavior are heading, the broader theory you want to test next.

    Most real thinking doesn’t live on the floor or up against the ceiling. It lives in the middle, where the two are forced to agree.

    Infographic titled Standing in the Middle showing The Ceiling (top-down wide context and possibility) above, The Floor (bottom-up verified receipts and server logs) below, and The Middle convergence zone where structure alignment, fact-only red teaming, and the observer flip meet
    The Floor (bottom-up receipts), The Ceiling (top-down wide context), and The Middle where they are forced to agree.

    When the floor and the ceiling meet in the middle, neither side gets a free pass. A wide narrative has to point to something that actually hit the server. A raw log count has to explain what it means outside its own three hyphens. Just like Hofstadter’s pq-system, meaning shows up only where the two structures lock together.

    Agreement with receipts beats theater every time

    Once you see that, something else clicks into place: an agreement reached across real disagreement is stronger than polite agreement you started with.

    That is why the U.S. Constitution splits power across three branches that push back against each other. Picture two axes crossing at an angle: they can diverge everywhere else, and right where they intersect is the point that carries the load.

    It is also the real difference between useful red teaming and performative pushback. I have always disliked red teaming when it is just someone taking the opposite side for the sake of being opposite. That is inference fighting inference — pure theater — and if you listen closely to critics, empty pushback can talk you right out of a sound idea.

    Fact-only pushback is the opposite. When we put together the PDF package for Not All Bots Are the Same, it went back two, three, four times over on verification checks before it was ready to publish. In the middle of those rounds, it felt annoying and disappointing. Looking back afterward, it was the best part of the process: every rejection came back with “show me the evidence.” The bottom-up receipts forced the top-down story to earn its keep.

    The catch: my bottom-up is your top-down

    Here is the turn I didn’t see clearly until the end of the morning: what is bottom-up for me is still top-down for you until you walk it yourself.

    Even when I publish the exact counts from our logs or lay out how a week of work orders ran, to anyone reading this article on a screen, my receipts arrive as someone else’s narrative. My Tuesday is not even the same as my Thursday, because things change — and your ones and zeros, your site, your crew, and your moment are specific to you.

    That is why I am not handing you a step-by-step checklist, and I am not selling a method. Think of this as a report from where I am standing:

    • If you already live up at the ceiling — in strategy decks, big-picture theses, and wide industry maps — maybe this gives you a reason to climb down into the raw receipts and see what pushes back.
    • If you already live down on the floor — buried in logs, tickets, and daily counts — maybe this gives you permission to look up at the wider landscape without feeling like you are abandoning the facts.

    I am just reporting from the field. Put your own spice on it.


    We do AI citation restoration. When the AI can’t find you, can’t read you, or keeps citing somebody else, send us the worst one you have — your RFPs, your disasters, the problem everyone else already failed to fix. We come from the restoration industry. We know what’s on the floor, and cleaning it up is the job. And if you’re a developer who just needs a hand on the hard part, get a hold of us. That’s what we’re here for.

    — William Tygart, Tygart Media. Reflections from a morning reading session on Gödel, Escher, Bach (Ch. II) and Bot Lab origin-log records, November 13, 2026.

    Printable Desk Reference

    Download this article as a PDF

    The complete article and Floor/Ceiling/Middle diagram formatted for print and offline reading.
  • ChatGPT Is Five Rooms, Not One Channel

    ChatGPT Is Five Rooms, Not One Channel

    There’s a post going around that says: if you can rank in ChatGPT, you’re way ahead of the game, your leads from ChatGPT will increase, invest now.

    Here’s the problem with that sentence. There is no “ChatGPT” the way there’s a phone book. There are rooms. And the person in each room is a different person, sitting in a different chair, at a different time of day, asking a different kind of question.

    A free-plan mobile ChatGPT user on the toilet is not the same human as a Claude user inside their desktop looking up technical documentation at 10 in the morning. Treating them as one audience because the logos are similar is how businesses end up advertising B2B services on a consumer feed — the same mistake, wearing a new jacket.

    The five rooms

    Room one: free ChatGPT on a phone. Consumer questions. Evenings, couches, commutes. What’s a good car stereo, write my cover letter, explain this homework. Enormous volume, almost no B2B buying intent.

    Room two: paid ChatGPT at a desk. Prosumers and knowledge workers who chose it as a tool. Better questions, work hours, some buying intent — when the question is about their own workflow.

    Room three: Claude at a desk. Developers, analysts, technical professionals. This is the room that reads documentation for a living. Weekday-shaped, deep, specific.

    Room four: Copilot inside Edge and Office. The corporate room. These people didn’t choose an AI — it arrived inside the tools their employer already runs. Facility managers, compliance staff, operations people, asking work questions in work language, mid-task.

    Room five: Gemini inside Google search. Everyone, for everything, at search scale. The broadest room and the shallowest intent per question.

    Same species of technology. Five different demographics. “Get cited in AI” means nothing until you say which room.

    What the counting says

    I count AI citations for a living — six months of Bing AI Performance data across my own network, 1.6 million citations and change. The rooms are not a theory. They’re in the numbers.

    On Tygart Media, the single most-cited page is a Claude AI pricing explainer — 1,388,909 citations. The audience for this site is technical professionals, and the citation traffic is weekday-shaped: it rises when people are at work and flattens when they aren’t. Room three, behaving like room three.

    On Healthcare Facility Hub — a site for hospital facilities and infection-control people — Microsoft’s AI surfaces cited 188 pages a total of 43,994 times in six months. The top pages are an ICRA matrix (4,067 citations), hospital evacuation planning (2,766), ASHRAE 170 ventilation requirements (2,435), NFPA 101 life safety (1,802). The questions behind them read like this: what has to be in a facility’s emergency preparedness plan about emerging infections; which fire safety feature keeps smoke in one zone. Nobody asks those questions from a couch. Those are room-four questions — asked at a desk, inside a Microsoft environment, by someone whose job depends on the answer being right.

    Two sites. Two rooms. Neither audience is in the room the hype is selling.

    The test that settles it

    Before you pay anyone to get you cited “in ChatGPT,” ask one question: which room is your buyer sitting in when the buying question forms?

    If you’re selling to hospital facilities staff, your room is Copilot at a desk, and the content that wins there is an ICRA matrix, not a viral post. If you’re selling car stereos, room one is genuinely your room, and God bless. The tactic isn’t wrong or right — the fit is.

    Anyone who can’t tell you which room they’re putting you in is selling you the label. The label is the one part that doesn’t matter.


    Will Tygart runs Tygart Media. The citation counts above are from his own six-month Bing AI Performance board, counted nightly. The $97 AI Citation Quick-Scan exists because “which room cites you” is a measurable question: https://tygartmedia.com

  • You Don’t Have a Token Problem. You Have a Habits Problem.

    You Don’t Have a Token Problem. You Have a Habits Problem.

    I held five hundred dollars of AI stack for ninety-nine bucks a month, and I used every drop of it. When the deal changed, I didn’t cry about the price. I changed where I bought my gas.

    Five hundred dollars of stack for ninety-nine bucks

    Here’s the deal I had, because it matters to everything after it. SuperGrok Heavy — the top Grok tier — listed at three hundred dollars a month. I got in early, in the first days of the offer, on an early-adopter intro price: ninety-nine bucks a month, a hundred and nine and change once the tax man took his cut. And riding inside that bundle, at zero extra dollars, was Cursor Ultra — the two-hundred-dollar Cursor plan. Do the math the way I did it at the time: I was holding roughly five hundred dollars of list-price stack for ninety-nine.

    And I used it. All of it. That’s the honest part, and I want it on the table before I say one word about anybody else’s habits. Grok seats, Cursor seats, the biggest model on whatever job was in front of me, because why wouldn’t I? The stack was so cheap that counting would have felt like a hobby, not a necessity. Nobody audits a deal that good. You just drive.

    I was not disciplined. I was subsidized. There’s a difference, and the difference only shows up later.

    Because the deal changed — deals do. The intro price was always going to step up; the paperwork said it would land at $299.99 a month. After that, the whole Grok plan structure got replaced by a new X subscription, and the bundle came apart. The free-stack era ended. Not with a betrayal — with a terms change, which is how these things always end.

    The gas was free, so nobody learned to drive

    Here’s my read on how we got here, and I’ll own it as a read: for a couple of years, compute was handed out like it was nothing. Generous free tiers. Big included allowances. Tokens falling out of every new signup. And I don’t think the platforms were being careless with that generosity. They knew exactly what happens when the meter isn’t running — people get unorganized. They experiment, they sprawl, they build their whole working life on the free stuff, and they form habits while nobody’s counting.

    That’s not a conspiracy. That’s how free samples work, in every business there ever was.

    Then things tighten — a limit appears, an allowance shrinks, the overage starts billing — and people feel robbed. People hit Claude’s usage limits and get furious. They watch a meter run in some agent tool and feel cheated. I understand the feeling, because I had it. But watch where the anger lands. It lands on the limit, every time. Almost never on the habits underneath it. The free era was never the normal state of the world. It was the sample. The normal state of the world is the one every household already knows: a thing costs what it costs, and the habits you built while it was free become your problem the day it isn’t.

    A kitchen table with paper bills, a calculator, a pencil and a coffee mug in morning light

    Premium in a car that runs fine on regular

    Compute is gas. That’s not a metaphor I reach for because it’s cute — it’s the same shape in every particular that matters. There are grades: regular, premium, diesel. Different fuel for different jobs. And most of us, most days, are putting premium in a car that runs fine on regular, because premium is what the pump defaulted to when somebody else was paying.

    I can put a number on that, because we ran the test. In October, my shop sent the same plain job to 44 AI models — visit five web pages, report the title, the heading, whether a video was embedded, and a one-line summary. A utility errand, not a puzzle. Thirty-six of the 44 models came back with a perfect score, 20 out of 20.

    The cheapest perfect run — a model called GLM 5.3 Flash — cost eight-tenths of a cent. The most expensive perfect run — Claude Fable 5, a flagship — cost 86.3 cents. Same job. Same perfect score. More than a hundred times the price.

    And premium didn’t even guarantee care. One run that cost over seventy cents reported a video missing from a page where the video was sitting in plain sight — it had read the page through a tool that strips embeds out, and never noticed. Money wasn’t the difference between those runs. Method was. The grade of fuel was never the thing that made a run good. How the job was set up was.

    So the question was never “can I afford the good model?” It’s “does this errand need diesel?” A small, fast model can run a census, sort a pile, draft the grunt work all day long on regular. The heavy reasoning model is diesel — you save it for the truck, for the leg of the job that actually pulls weight. Burning the flagship on everything isn’t quality. It’s a habit with a receipt.

    And then there’s the gas station

    The fuel is only half of it. There’s also where you buy it.

    Your harness — the app, the agent tool, the environment the model runs inside — is the gas station. Two stations can sell you the same grade at different prices, and the station still matters. Does it take your card, or do you have to go inside and prepay? Is it on your way to work, or twenty minutes out of the way? What else does it sell — the snacks, the tools, the integrations you use? A cheap station with bad pumps costs you more than the price on the sign.

    And then there’s the Costco question, and it’s a real question, not a punchline: the gas there is thirty cents a gallon cheaper, and the line is twenty cars deep. Does it make sense? It depends on the trip. A big batch job that can sit in a queue overnight is a Costco run — take the cheap fuel, wait in the line, who cares. A job that’s on fire at 2 p.m. is not. You pay the corner station, you pay it gladly, and you get back to work.

    Cheap compute almost always has a line attached to it — a queue, a rate limit, a slower pump. Pricey compute is the corner station: more per gallon, no waiting, right here, right now. Neither choice is dumb. What’s dumb is never noticing you’re making it.

    But here’s the part I learned the slow way, and it’s the most useful thing in this piece: the station is the thing you keep. The fuel is the thing you swap. Models come and go. Prices move on a Tuesday. Bundles unbundle. Your system — the harness, the setup, the way the work flows through it — that’s yours, and it stays. Loyalty to a model is loyalty to a price somebody else controls. Loyalty to your system is what lets you shrug when the price moves and just drive to the next pump.

    A long line of cars waiting at a warehouse gas station at dusk

    Set the system up. Then move the compute around.

    So when my bundle came apart, let me be clear about what I did not do. I did not go buy a bigger plan. I did not rebuild my shop. By then Muse had become available, and I started thinking about the compute itself: use more of what Muse offered, use more of the models already included inside Cursor, run different models through the same system. And that’s what we did. We’ve run different models all through our system — same harness, same workflow, different fuel in the tank depending on the job and the price that week. The shop didn’t change. The fuel did.

    Here’s what that looks like today. Our production runs are built in legs. The cheap model goes first and does the bulk work — the searching, the sorting, the first drafts. A mid-tier takes the middle leg. The expensive model runs last, briefly, on the one leg that genuinely needs its judgment. The cheap path is the default path. The premium pump is the exception, and it has to argue its way in.

    And when we need savings, we don’t suffer for them and we don’t stop driving. We move the compute: this job goes to a cheaper model, that job to a different station, the big batch runs when the line is short. It’s the same thing a family does in a tight month. You don’t stop eating. You stop ordering out on Tuesdays.

    And moving the compute around means the work never has to stop. There’s almost always another pump — another model, another harness, another way to run the same job — and knowing your map of stations is worth more than any single plan’s allowance. A shop that knows where its fuel comes from doesn’t panic when one station raises its price — it drives to the next one.

    That’s the whole discipline, and it’s not willpower. Willpower at the moment of the click loses every time — I know, I’ve clicked. Discipline is decisions made once, upstream, in how the work is set up, so the meter mostly takes care of itself downstream.

    A garage workbench with tools laid out in a row and parts bins stacked neatly

    Peanut butter, ramen, and two eggs

    I always tell people: I never learned how to cook until I ran out of food. Not ran low — ran out. Or ran out of money to go to the restaurants, which comes to the same thing with extra steps.

    The lean years were paycheck to paycheck, and I remember standing in front of a cupboard four days before payday, doing inventory. Peanut butter. Ramen. Two eggs. And figuring out how to turn that into something you’d actually call dinner — something magical, if I’m being honest about the ambition. I think that’s maybe where the word fusion came from. Somebody looked into a cupboard like mine and refused to be sad about it.

    I bring it up in a piece about AI tokens because it’s the same lesson, the real one underneath everything above: abundance never taught anybody anything. A full fridge never taught anybody to cook. A fat plan never taught anybody token discipline. Constraint is the teacher, every single time — and it’s a generous teacher, because what it teaches you is yours. The deal can change. The price can change. The cupboard can change. The skill doesn’t leave.

    Token discipline is a cook’s discipline. You work with what’s in the cupboard. You make it good anyway.

    It’s the oldest problem there is

    People talk about token limits like they’re some new cruelty the AI companies invented last spring. They aren’t new. They’re a budget. And a budget is the oldest problem human beings have — the same shape as the grocery money, the same shape as the gas tank, the same shape as every shop that ever stood in a parts store wondering how the month got away from it.

    The limits didn’t get meaner. The intro price ended, the free sample ran out, and habits built in the free era ran into a meter. When that happens at a kitchen table, nobody claims the grocery store is running a conspiracy. They say: we have to shop differently.

    Same here. You don’t have a token problem. You have a habits problem — and that’s the good news, because pricing pages aren’t yours to change, and habits are.


    Will Tygart runs Tygart Media in Puyallup, Washington, where we help local service businesses get found and cited by AI search. The shop runs on the rule this piece describes — cheap path by default, the good stuff where it counts. If that’s how you’d want your marketing run, come find us.

  • Is Your Voice Assistant a Brain, or Just a Router?

    Is Your Voice Assistant a Brain, or Just a Router?

    It hit me while I was talking to my phone

    I spend a good part of my working day talking to AI out loud. I run a small marketing shop, and a lot of my work now happens through voice — I talk to Glint Voice while I’m driving, I talk to Grok Voice when I’m working through an idea, and the conversation feels like one continuous thing, one personality on the other end of the line.

    Except it isn’t one thing. It never was.

    What you’re actually talking to is three parts bolted together. First, the ears and the mouth: the puck on the counter, the phone in your hand. It hears you and it says words back. That’s all it does. Second, the router: the part that catches the wake word, turns your speech into text, and makes a judgment call — what did he probably mean, and where does this go? Third, the brain: the model somewhere else, in a data center, that actually knows things and does the thinking.

    The personality you like — the voice, the tone, the way it answers — that doesn’t live in the speaker. It lives in the brain and in the routing rules. The box on your counter is a mouth with good PR.

    Once you see it, you can’t unsee it. Siri, Alexa, the assistant in your car, the voice app on your phone — they’re all the same machine wearing different plastic. Every one of them is ears, a router, and a brain somewhere else. The only real difference between them is who owns the middle part: the router, and the table of rules that decides where your words go.

    I noticed it first in my own tools. When I talk to a voice app on my phone, there are moments where you can feel the seam — a pause while the words travel, an answer that clearly came from somewhere with a lot more horsepower than the phone in my hand. That’s not a flaw. That’s the architecture showing. The app is a nice mouth and a good set of ears. The thinking happened in a building full of servers, and the only real decision my phone made was where to send me.

    And that difference — who decides where your words go — turns out to be worth about a billion dollars a year. Reported.

    Apple paid a billion dollars to prove the point

    In January of 2026, Apple and Google put out a joint statement: the next generation of Apple Foundation Models would be based on Google’s Gemini. In June, at WWDC, Apple confirmed it on stage. And in September, the rebuilt Siri shipped with iOS 27 — running on a custom Gemini model, inside Apple’s own Private Cloud Compute, so your questions never land on Google’s servers.

    Read that again, because it settles the argument. The biggest technology company on earth looked at its own voice assistant and decided the brain wasn’t worth building itself. It rented one. The reported price is around a billion dollars a year, for a model reported at roughly 1.2 trillion parameters — and I’ll flag it plainly: those figures are reported, not confirmed by either company. But the structure of the deal is confirmed, by Apple, in public. Apple kept the door. Apple kept the router. Apple kept your data inside its own walls. The thinking, it buys by the year.

    If Siri were a brain, that deal makes no sense. You don’t rent out the core of your own product to your biggest rival. But if Siri is a router — a front door, a wake word, a set of rules about where a request goes — then the deal makes perfect sense. The door was always the valuable part. The brain is a part you can source.

    Apple isn’t embarrassed about this, and it shouldn’t be. It’s just the first time the anatomy has been visible at that scale, with a price tag on it.

    A small voice satellite puck on a home office desk beside a monitor, open notebook, keyboard and headphones in late-afternoon light

    The front door stayed Apple’s. The brain became a swappable part

    It gets better. iOS 27 also shipped with Extensions, which let a user pick a third-party model — Claude, ChatGPT, and Gemini were the named launch partners — as the brain sitting behind Siri’s features. Same Siri voice. Same Siri face. Different brain answering, because you chose it.

    That’s the routing table, opened up a crack, in public, by Apple.

    For years the arrangement was: whoever owns the front door decides what it connects to, forever, and you don’t get a say. That’s why you couldn’t run Siri’s mouth with somebody else’s brain. The router is the product, and nobody gives up the product. What Apple has now done — first by renting Gemini itself, then by letting users swap the brain through Extensions — is admit the two things are separate. The door is one product. The brain is another. They just spent a decade pretending they were the same thing because the pretending was profitable.

    The honest version already exists, and it costs about $69

    Here’s the part that made me grin. The open version of this exact machine — dumb satellite, your router, a brain you choose — isn’t a concept. It’s a product. You can buy it today.

    It’s called the Home Assistant Voice Preview Edition, made by Nabu Casa, the company behind Home Assistant. It launched in December 2024 and sells for $59 to $69. It is deliberately, proudly dumb. The wake word — “Okay Nabu” — runs right on the device. There’s a hardware mute switch that physically cuts power to the microphones; when it’s off, the thing cannot hear you, and that’s a wiring fact, not a settings promise. Inside is an ESP32-S3 chip and an XMOS audio chip, and that’s about it. The puck does nothing on its own. Nothing.

    Everything else happens on a Home Assistant server in your house, and the puck talks to it over an open protocol called Wyoming. The pipeline is built out of stages you can swap like parts in a shop: Whisper turns speech into text, Piper turns text back into speech, and both can run locally, on your own hardware. The conversation stage — the brain — can be a local model running through Ollama, or any cloud model you point it at. Your routing table. Your call. Change brains next month if a better one ships.

    I think about it the way I think about tools in my own shop. I don’t buy a new workbench every time a better saw comes out — the bench stays, the saw swaps. This puck is the bench. Whisper, Piper, the model of the month: those are saws. A setup that treats them as parts is still useful in five years. A setup that welds them together is a countdown.

    The cheapest fully local setup runs about $130 all in — a small Pi-class server plus the puck. No subscription. No vendor account. Nothing leaves your network unless you tell it to.

    Now the honest trade-off, because there is one: you need a Home Assistant instance running, and there’s some setup. It’s a Saturday-morning project, not an unboxing. And that, right there, is exactly why the locked appliance sells. One box, one warranty, works out of the carton, nobody configures anything. I understand the appeal. I just want people to know what they’re trading for that convenience: the routing table. The vendor’s box is a router that lies about being a brain — it routes to their brain, with their hand on the table, and you can’t re-point it.

    A small dark voice satellite puck on a wooden bookshelf among old books and a framed photo, lamp light, hallway beyond

    So ask the only question that matters

    When any company shows you a voice product — a puck, a box, a gadget that promises all the intelligence in one little unit — don’t ask how smart it is. Ask two plainer questions: Who owns the routing table? And can I re-point it?

    If the answer is “we do, and no,” then the box is not the product. You are the route. Your words get sent to the brain they chose, on terms they set, at a price they can change — and when a better brain exists somewhere else, your box will never be allowed to use it.

    If you own the door, the rest is just parts. Brains improve every few months now; a brain that’s rented or swappable gets better on its own schedule. A brain that’s welded shut gets worse every day it ages, because the world moves and it doesn’t.

    The box was never the product. The routing table is the product. Apple just paid a reported billion dollars a year to tell us so.

    A small white voice satellite puck on a worn garage workbench among hand tools and parts bins, pegboard and task lamp behind

    Will Tygart runs Tygart Media in Puyallup, Washington, where we help local service businesses get found and cited by AI search. If your customers are asking assistants instead of typing searches, that’s the work we do — come find us.

  • Vibe Coding, From a Shop That Ships With It

    Vibe Coding, From a Shop That Ships With It

    I run a small media shop, and most of what we ship now — websites, measurement tools, videos, test programmes — gets built the same way: I describe what I want, an AI builder writes it, and my hours go to steering and checking instead of typing.

    Vibe coding is describing what you want built in plain language and letting an AI builder write the code — you steer with intent and judgment, and it does the typing.

    Andrej Karpathy put the name on it in early 2025: “fully giving in to the vibes.” The phrase stuck because it is honest about the feeling. You stop writing the code line by line. You talk, the machine builds, and you judge what comes back. What the phrase leaves out — and what nobody tells you until you run a real shop this way — is where the work actually went. It didn’t disappear. It moved.

    What it looks like from this desk

    Nobody here opens a blank file and starts chatting at a builder and hoping. The work runs on written work orders: a commission that says what the finished thing is, what it has to connect to, what it must never do, and what proof comes back when it’s done. The builder — we run several, in different seats, with different jobs — executes against that order. Then the return gets checked: not skimmed, checked. Claims get compared against sources. Numbers get tied back to where they came from. Pages get fetched live and read the way a visitor would read them.

    That seat discipline matters more than the model does. A builder with a lane, a written order, and a receipt to produce behaves like a contractor. A builder with a vague prompt and no checking behaves like a confident intern who never sleeps and never admits he’s lost. We wrote up how the seats are governed in our piece on running six AI seats on one business, and the short version is: the structure is the skill. The prompt is the smallest part of it.

    What shipped

    Talk is cheap in this trade, so here is what actually went out the door from this shop, built this way:

    • A citation-measurement programme across a fleet of niche sites. We track where AI answer engines cite our pages and where they don’t, topic by topic, site by site — that map drives what gets written next, instead of guessing.
    • A nightly board that re-pulls our own citation numbers and republishes them. Every night it goes back to the source data, rebuilds the tally, and posts the current standings. If the numbers move, the board moves. Nobody hand-types a figure into it, which means nobody can quietly round one in our favour.
    • Article-to-video pairs, built in-house. Script, scenes, narration, captions — produced here, published as pairs: the article and its video, each pointing at the other. Nine pairs are live. The most recent one is Half the Citations Sit on Three Pages, which is itself a finding out of the measurement programme — the work feeds the work.
    • An anchor experiment, installed live on November 7. We put anchor links on article section headings so each section can travel as its own citable piece — the way a video chapter does. It’s running now and being measured. It might work. It might not. Either way we’ll know from the data, not from a feeling.
    • A full inventory-test programme run against a real product. Not a demo on our own toy data — a scored test, run in the open inside the shop, with results written down whether they flattered anybody or not.

    That’s the part of vibe coding the tool ads get right: the volume is real, and a small shop can ship like a bigger one. Now the other half.

    What broke

    Everything on this list cost us time, and every item on it taught the same lesson from a different angle.

    • Invented facts, caught at the gate. Our page-refresh programme ran in waves, and a pattern showed up in the returns: builders writing plausible, confident, wrong facts into refreshed pages — vendor details, protocol claims, numbers that sounded right and weren’t. None of it shipped, because every claim got checked against a source before publish. But “none of it shipped” is doing a lot of work in that sentence. Without the gate, it all ships. That is the default outcome of vibe coding without a checker: fluent fiction at production speed.
    • A page and its PDF, saying two different things. We’d fix a page and leave its downloadable PDF stale, so a reader with the old file in their own system was working from numbers we’d already corrected. The fix became a standing rule: a page and its download are one asset. The PDF gets regenerated from the corrected content in the same run, or the edit doesn’t ship. The builder never once flagged the drift on its own. A human had to notice the pattern and make it a rule.
    • Runs that stalled on things nobody priced. Quota running out mid-programme. A token that didn’t cover the sites the job needed. A browser on a busy desktop that couldn’t be borrowed. Each one stopped a run cold, and each one was knowable before the run started — somebody just hadn’t checked the whole path to the finish.
    • A redirect job priced at the start instead of the finish. The estimate covered beginning the work, not completing it, and the job froze partway with the loose ends live. It got sorted, but the scar tissue became another rule: price the finish, not the start — the whole path, including whether the human has to stand there while it runs.

    Read those four back and the pattern is plain: the builder’s confidence is not evidence. Not one of those failures was a typing failure. The code worked. The words were spelled right. What failed was truth, scope, and follow-through — the exact things a confident machine will never flag about itself. The operator’s checking is not a quality step added to vibe coding. It is the product. The building is the commodity.

    The honest split of labour

    Here is how the work actually divides in this shop. The machine is fast at the typing and tireless at the volume. It will rebuild a board every night forever and never get bored. It will draft the fortieth page in a wave with the same energy as the first. It does not get tired, and that is genuinely new in the world — a two-person shop with tireless hands.

    The human carries everything the machine can’t: the intent (what should exist and why), the taste (this is good enough, this is not), the fact-check (this claim is true, that one is invented), and the stop button (this run ends here, this door doesn’t open). Those four things sound soft next to “writes code.” In practice they are the whole job, and they were always the whole job — the typing was just where the hours used to hide.

    We have a phrase for it here: partway is the point. The skill isn’t prompting. The skill is knowing which 80% to let run and which 20% is yours — and never confusing the two. Let the machine run the 80% and it will carry you further in a week than a year of typing. Hand it your 20% — the judgment, the verification, the calls — and it will carry you straight into a wall, politely, at speed, with perfect formatting.

    What it is not

    It is not “anyone can build anything now.” Anyone can get something built. The question was never whether the machine can produce the thing — it’s whether the thing is right, and knowing that takes judgment the subscription doesn’t include. Judgment is the scarce input, and it’s scarcer than it was, because now it has to cover ten times the output.

    It is not the end of programmers. Somebody still has to know when the output is wrong, and “wrong” gets subtle fast: the code runs, the page loads, and the fact on it is invented. The people who’ll do best in this aren’t the ones who type fastest or prompt cleverest. They’re the ones who can read a return the way an editor reads a draft — for what it claims, not how it sounds.

    It is not a vibe you can skip verifying. The name is the most dangerous thing about it. “Vibe” suggests the checking is optional, a personality choice for nervous people. In a shop that ships to real readers, verification is the difference between a production system and a fiction generator with good uptime. Give in to the vibes on the typing. Never on the truth.

    So here’s where this shop lands on the term. It sounds like the work got softer — like building things turned into lounging with a laptop and a feeling. From inside, it got more honest. The typing used to hide the judgment; now the judgment is all that’s left, and it shows. A piece either has its receipts or it doesn’t. The facts either check or they don’t. The thing either shipped or it’s a story about shipping.

    That’s a harder standard than the old one, and it’s a better one. We’ll keep building this way.

    Frequently asked questions

    What is vibe coding?

    Vibe coding is building software and content by describing what you want in plain language and letting an AI builder write the code, while you steer with intent and judgment. Andrej Karpathy named it in early 2025, describing it as “fully giving in to the vibes.” In a working shop, the steering and the checking are most of the job.

    Is vibe coding good or bad?

    Neither — it’s a method, and the result depends on what surrounds it. With written work orders, clear boundaries, and a hard check on everything before it ships, it lets a small shop produce at a scale that used to take a team. Without the checking, it produces confident mistakes faster than any method in history. The vibe is not the variable. The verification is.

    Do you need to know how to code to vibe code?

    You need to know how to judge, which is a different thing. You don’t have to write the code, but you do have to be able to tell whether what came back is right — whether the facts check, the scope held, and the thing actually does what it claims. If you can’t tell, you need someone beside you who can. That judgment is the part you can’t hand off.

  • Agentic AI, From Inside the Shop

    Agentic AI, From Inside the Shop

    Everybody is selling “agentic AI” right now, and most of the selling is conference talk — slides about autonomous everything, written by people who don’t run anything with it. I run a small media company with it. Every day. So here’s the definition from the floor of the shop instead of the stage.

    Agentic AI is AI that doesn’t just answer. You give it a job — with boundaries, tools, and a way to report back — and it carries the work through the steps itself, without a person pushing each one along.

    That’s the whole distinction. A chatbot waits for your next prompt. An agent takes a commission and goes and does the work: reads what it needs, uses the tools it’s been handed, makes the small decisions inside its lane, and comes back with the finished thing and the proof. Whether that works or falls apart depends entirely on how the shop around it is arranged — and the arrangement is the part nobody puts on the slide.

    The seats: nobody here does everything

    The first arrangement decision: the work is split across named seats, and each seat has a lane.

    • The chief-of-staff seat holds the context. It keeps the memory of what’s been decided, what’s owed, who’s who, and what I said on a clear-headed day — and it turns my direction into written work the other seats can run. It’s the filter, not the boss.
    • The code seat builds. When something needs to be made — a tool, a page, a fix — that seat writes it and shows its record. I keep the code seat’s record in public for a reason: a seat that builds should be able to show what it built.
    • Scout seats go and look. Research, censuses, reading a market or a competitor end to end and coming back with what’s actually there — not what the summary said was there.
    • The executor seat runs work orders on the machine where the work lives. It does the hands work: publishes, edits, uploads, the long multi-step runs I don’t have the hours to sit inside.

    I wrote up how I run six AI seats on this business — the governance, the lanes, and the rule that matters most: a seat does not freelance outside its lane. The moment an agent starts deciding on its own what else might be a good idea, you don’t have a staff. You have a rumor mill with write access.

    The work order is the unit of trust

    Seats don’t get vibes. They get work orders — written commissions, one job each, built before anything runs. A work order in this shop carries four things:

    • The whole price, stated once, up front. Everything the job will touch, everything it might cost in time or taps from me, named before it starts. Nothing gets discovered as a surprise blocker halfway through — or if it does, that’s a defect in the order, and we say so.
    • The context, baked in. The executor shouldn’t have to guess who I am, what the site is for, or how I talk. The order carries it, so the work comes back sounding like this shop and not like a template.
    • The boundaries. Some doors are mine alone: money, credentials, anything that sends to another person, anything that can’t be undone. Those are drawn as lines in the order itself. Inside the lines, the seat has real latitude. Across them, it stops and comes back to me.
    • The receipt standard. Exactly what proof comes back with the finished work — measured values, live links, counts — written into the order before the run, not negotiated after it.

    Think of it like commissioning a piece of furniture. I don’t stand over the maker’s bench. I write the commission well enough that the piece can only come back right — and then I do the finish work when it arrives.

    Receipts are the proof, because “done” is a claim

    Here is the part of agentic work the demos skip: an agent can tell you work happened that did not happen. Not out of malice — out of the same confident fluency that makes it useful. It will describe the email it sent, the page it fixed, the file it saved, in perfect detail, and some of the time it will be describing a thing it only intended to do.

    So in this shop, nothing is done because a seat says so. It’s done when the live thing checks out. The published page gets fetched and read. The number gets tied back to the source it came from. The export gets counted, not described. Every run comes home with receipts, and a second seat does the finish check against the live result before I ever hear the word “done.”

    That’s not paranoia; it’s the load-bearing wall. The whole Receipts series on this site exists because citation claims kept turning out to need a second look — the piece where half the citations sat on three pages started as a seat’s confident summary and ended as a very different story once somebody counted. The receipt discipline exists because of that failure mode. Not despite it.

    What the human does all day

    People ask what I do if the agents do the work. The honest answer: the parts that were always the job.

    I bring the direction and the instinct — which door is worth walking through, which idea smells wrong even when the reasoning sounds fine. I make the judgment calls: pricing, commitments, anything with another person’s name on it. And I hold the one-way doors. A send, a payment, a deletion, a credential — those wait for my tap, every time, by design and not by limitation.

    What the system holds for me is the context I can’t: every decision, every receipt, every open loop, across more projects than one head carries. I don’t have to remember where things stand. I have to decide what happens next — and when I’m tired or emotional and about to make a call my clear-headed self wouldn’t make, the system holds the line with what I said when I was thinking straight. That’s the trade, and it’s a good one.

    The honest limits

    Anybody who runs agents for real can tell you the failure list, so here’s mine. Agents drift off the brief when the brief has a soft spot in it. They conflate two similar jobs — same-shaped folder, different work — and run the wrong one beautifully. They price the start of a job and not the finish, so a run looks cheap until you count the stalls, the re-reads, and the tap it needed from me at the worst moment.

    The craft isn’t pretending the seats are flawless. The craft is the guardrails and the checking: the input manifest verified before the run starts, the step-zero check that clears a suspect before anyone calls it broken, the receipt read against the live thing instead of against the report. Every scar on the process here is a rule now. That’s how a shop gets good at this — not by buying a smarter seat, but by writing down what the last failure taught it.

    What “agentic” means with the talk stripped off

    Strip the conference language away and agentic AI is this: a small business running like it has a staff. Research that actually gets done. Pages that actually get published. Records that actually get kept. A two-person company doing the carrying work of a much bigger one — with the receipts to show for it, because the receipts are the only version of the story worth telling.

    We’ve published dozens of pieces from inside this work — the failures included, especially the failures — because the shop is the argument. If agentic AI is going to mean anything outside a demo, it’ll mean shops like this one: named seats, written orders, hard boundaries, and proof at the end.

    Questions people ask me

    What is agentic AI in simple terms?

    It’s AI you give a job instead of a question. You set the boundaries, hand it tools, and tell it how to report back — then it does the steps itself and returns the work with proof, instead of sitting there waiting for your next prompt.

    What is an AI agent vs a chatbot?

    A chatbot answers and stops. An agent acts: it reads, decides small things inside its lane, uses tools, and works through a multi-step job over time. The chatbot is a conversation. The agent is a commission — and commissions need boundaries and receipts in a way conversations don’t.

    How do multiple AI agents work together?

    The same way a small staff does: split lanes and written handoffs. One seat holds context and writes the work orders, specialist seats build or research, an executor runs the job where the work lives, and a second set of eyes checks the result against the live thing. The coordination isn’t magic — it’s the paperwork, done properly.

    Do AI agents replace employees?

    In this shop, there’s no version where a seat makes the judgment calls, holds the relationships, or takes responsibility for a one-way door — that’s my job and it stayed my job. What the seats replaced is the carrying: the hours of execution between a decision and a finished, checked piece of work. For a small business, that’s the difference between ideas that die in a notebook and work that ships.

  • Your Site’s Next Visitor Sends an Agent. Tobira Wants Yours to Meet It.

    Your Site’s Next Visitor Sends an Agent. Tobira Wants Yours to Meet It.

    Ask your AI to do a simple errand: book a call with ten real companies you might buy from. Not research them. Book the call.

    Tobira’s founder, Vlad, ran that exact test before he built anything. He asked his Claude to book a call with 10 real companies. The result, in his launch account, was zero bookings and zero payments. The agent didn’t fail at reading. It failed at the last step — account walls it couldn’t pass, booking pages that block AI, and forms built for fingers and eyes.

    That zero-for-ten is the failure every small business is about to meet. More buyers research inside ChatGPT or Claude, and increasingly ask the same chat to take the next step: book the call, start the trial, place the order. Your site was built for the researcher, not the errand. If the errand dies at your form, you never learn the buyer was there.

    Tobira Site Agent is one vendor’s answer to that break. We have not tested it on our own sites — this is a desk read, built from Dirty Static’s guide to Tobira Site Agent, itself built from Tobira’s maker site and Product Hunt launch post, facts checked November 7, 2026. Where a number comes from Tobira, we say so.

    The clerk, not the brochure

    Most of what businesses have done for AI visitors so far is brochure work: clearer pages, structured content, files an agent can read. Necessary — and it’s the layer we already run. Tobira bets the brochure isn’t enough. A brochure can’t close. A clerk can.

    Tobira puts a site agent of your own on your website, one that lives there, answers questions, and sells — not just to people, but to the AI agents people send. Your site should not wait to be read by a visiting agent. It should send an agent of its own to meet it, answer it, and do the transaction.

    The job list is sales work, not trivia. Per the maker, the agent asks about the visitor’s case, suggests the option that fits, books the call, starts the trial, captures the lead, and sends a payment link — right inside the chat the visitor started in. Booking, trial starts, leads, and payment happen in that chat, not on a separate page. It can talk by voice, with a transcript, and answers in the visitor’s language. When a case gets hard, a person steps in with the chat context attached, so the human isn’t starting from zero.

    Two visitors, one site

    The mechanism is a split. People see your normal website. Visiting agents get a version made for them, built by your agent from your own content. Per the maker, your agent publishes the files agents look for — llms.txt, agent.json, and AGENTS.md — so a visiting agent reads the offer directly and talks to your agent, instead of scraping page after page.

    The token math is the quiet part of the pitch, and it’s a maker example, not a measurement. In Tobira’s worked example, a normal pricing page runs to about 120,000 tokens of page weight. The structured answer lands at about 1,300 tokens, which the company presents as 92 times fewer tokens. Treat that ratio as a company example, not a measured result for your site. Your pages are not their example page. The direction still makes sense: an agent handed the plan, the price, and the next open slot as clean data finishes faster than one guessing its way through your navigation.

    The guardrails are the real product

    A salesperson who improvises prices is worse than none, and a site agent is a salesperson. The important part of Tobira isn’t the booking trick — it’s three guardrails the maker describes.

    First, answers only from your own materials: your site, price lists, PDFs, and FAQs. If the answer isn’t there, the agent doesn’t guess. It offers a call instead. Second, it shares only what you made public. Pricing and plans you chose to publish can be public; internal notes and deal margins stay private. Third, a person steps in on hard cases, with context — the chat history goes to your team, so the buyer never starts over.

    Rules are set in plain words, per the maker — “price ranges only,” “no promised discounts.” If it works as described, the guardrails are the product. The chat is just where they show up.

    Setup and cost

    Setup, per the maker, starts with a scan: Tobira reads your site and builds the knowledge base from what it finds. You add documents, set tone and rules, and test it on the real questions buyers ask. Then it goes live as a badge or widget.

    How long? The founder says 10 minutes on Product Hunt; the product page says 2 minutes. Both are maker claims. The honest reading is minutes, not days — with the real work in checking what the scan learned before you trust it with prices.

    Pricing, maker site checked November 7, 2026, USD monthly before taxes: Free is $0 with your own AI key — Tobira’s fee is zero, the model bill is yours. Lite is $49, about 300 conversations. Start is $169. Business is $399, adding payments, your own branding with no Tobira badge, and voice up to about 1,500 minutes. Premium is $799, up to 3 sites, and on that tier Tobira keeps 15% of AI-subscription revenue. Paid plans carry a 14-day money-back guarantee, and the maker says a data processing agreement comes with paid plans, with data handled under GDPR.

    Free is a genuine test, not a stripped demo. Paid tiers climb fast.

    The network bet

    A site agent alone is a better shop window. Tobira also wants it to be a doorway into a market. Per the maker, your agent gets a public address in the Tobira network — an email-shaped handle, but for AI. When another company’s agent looks for what you offer, the two agents talk first and check fit. You get a qualified deal, or silence.

    The founder says the network holds more than 800 agents. That is a company figure, not audited, and a network is worth what its members are worth — from outside today you can’t tell a market from a list.

    Where this sits in our own house

    We’ve written this pattern before, from the other side. In October, after Kin’s WebMCP launch, we published “The Agent-Ready Site”: welcome the machine, structure the content, give the agent a way to act, measure what it does. Our fleet runs three of those four layers today. Our llms.txt has been live since October 2026, roughly 62% of our traffic is bots rather than people, and we measure the machine side with Bing’s citation exports.

    Tobira is what the unbuilt layer looks like when a vendor builds it for you. The missing layer was the third: give the agent a way to act. An llms.txt is the brochure on the door — it tells a visiting agent what you offer, in its own language. A site agent is the clerk behind it — it answers back, books, and takes payment. Same argument, next step. The pattern said structure your content for agents. Tobira’s bet is that the structure should be a salesperson.

    For the record: Tygart Media has not installed Tobira or run it on a client site. It’s a live commercial answer to a layer we know is missing.

    The two questions that decide it

    One: do your buyers send agents yet? The whole model depends on buyers asking their AI to book and buy, still a young habit. Every speed figure Tobira publishes — including its “2.2 times faster” claim — is founder-tested, not from an outside lab. If your customers still call and complete forms without trouble, a good booking page beats an agent you have to feed.

    Two: are your materials clean enough to be spoken aloud? An agent answering only from your materials is only as good as those materials. A stale price on a page is an embarrassment. A stale price spoken with confidence by your own agent, with a payment link attached, is worse than no agent at all.

    If your buyers already arrive through AI and die at the booking step, the free route is worth a real test. If they don’t, watch the habit and the network count, and keep your booking page in good shape. Guessing wrong about which one you’re in is the expensive option.

    The practice

    Run the founder’s test on yourself. Open the AI you actually use and ask it to book a call with your business — your real site, no help from you. Watch where it dies. If it books cleanly, your forms were never the wall; file this category under “later.” If it stalls at an account wall, a blocked page, or a form it can’t complete, you’ve just watched the exact failure Tobira is selling against — free, in ten minutes, on your own storefront.


    Want this thinking applied to your own business? Book a call with Will Tygart — 30 minutes, and we start from your receipts, not a pitch deck.

  • The Coding Ladder Says the Dial Pays. Our 52 Calls Said It Didn’t. Both Numbers Are Real.

    The Coding Ladder Says the Dial Pays. Our 52 Calls Said It Didn’t. Both Numbers Are Real.

    Yesterday we published a test: 52 calls to Muse Spark 1.3, seven kinds of work, every rung of the reasoning dial, everything scored against ground truth. Our result was not close. The cheapest setting never lost — and twice, extra thinking was the failure itself. We set the fleet’s operating rule on that evidence and moved on.

    Then a counter-check showed up, the way we’d want one to. BenchLeader — a third-party site that republishes benchmark results from their original publishers — carries a full rung-by-rung row for Muse Spark 1.3 on CursorBench, a coding benchmark. On that ladder, the dial pays at every single rung. If both results are real, they can’t both be the whole story. So we read the ladder the way we ran our own test: numbers first, bases stated, no vibes.

    The ladder’s numbers

    CursorBench, Muse Spark 1.3, as published on BenchLeader (data as of November 8, 2026; the underlying results are Cursor’s, dated September 2, 2026):

    Rung Tasks solved Rank on the board
    minimal 24.3% #79
    low 29.3% #72
    medium 32.6% #64
    high 33.4% #59
    xhigh 37.5% #48
    max 41.6% #38

    No rung regresses. Every step up solves more tasks than the step below it — +5.0 points from minimal to low, +3.3 to medium, +0.8 to high, +4.1 to xhigh, +4.1 to max. Across the whole ladder that’s +17.3 points: at max, the model solves roughly 1.7 times the share of coding tasks it solves at minimal. Ranks are among 82 model configurations with a published result on that benchmark.

    What is CursorBench? In BenchLeader’s words, it’s “Cursor’s internal coding-agent evaluation”: coding tasks run inside Cursor’s agent, with the reasoning level and cost per task recorded, scored as the percent of tasks solved. Two honest labels belong on it. It is published by a coding-tool vendor — BenchLeader itself flags “harness is theirs” — and BenchLeader carries it for reference only; it doesn’t count toward their composite index. It is still the only rung-by-rung coding evidence for this model that we know of, and it points the opposite way from ours.

    Our numbers, on the record

    Our battery was 52 API calls to the contributor tier of Muse Spark 1.3, November 6–7, 2026, identical prompts at multiple settings, mechanical scoring. The buyer-brief judgment task scored identically at every rung — minimal got it for 776 reasoning tokens and 6.5 seconds, xhigh for 6,847 tokens and 50 seconds. Verdicts at scale: 120 out of 120 at low, 120 out of 120 at xhigh. Planning: provably optimal schedules at every rung.

    And the coding cell — the one this ladder speaks to directly. Our debugging task was one function with three planted bugs. Every rung found the inverted discount logic and the rounding bug; the cheapest setting found all three. One xhigh call spent its entire 8,000-token budget thinking — 7,998 reasoning tokens — and returned an empty answer. It thought so long it never spoke. Minimal answered the same task correctly with 500 reasoning tokens.

    Our published conclusion: on our work, extra reasoning bought latency, not quality, and the operating rule became low by default, with xhigh and max earned only by a demonstrated failure at low.

    Both numbers are real. The tasks aren’t the same.

    Put the two bases side by side and the disagreement gets smaller and more specific:

    • Task shape. CursorBench runs coding tasks inside an agent — sustained, multi-step work where the model plans, acts, reads errors, and recovers over many turns. Our battery was single API calls with a checkable answer. Our one coding task was a single function, solved — or stalled on — in one shot.
    • Tier and harness. The ladder ran Spark 1.3 inside Cursor in September. We ran the contributor tier through the API in November.
    • Measurement. The ladder reports the percent of a task set solved. We scored one sample per cell against ground truth — a limit we printed in the original piece.

    Here is our reasoning, labeled as reasoning and not as either source’s claim: the reconciler is task shape. On a short, bounded task with a checkable answer, the first think is the one that does the work; rungs above it buy patience-testing latency, and occasionally a stall. On a long agent run — hold a codebase in mind, take twenty steps, survive your own mistakes — extra reasoning has something real to chew on, and the ladder pays for it. That reading fits the anomaly we flagged in our own data: the rungs behaved like task-shaped budgets, not fixed ceilings. It also fits the limit we printed: we never tested sustained work. CursorBench did — or rather, Cursor did.

    What would change the verdict

    Not an argument. A run. The test that settles this for our shop is our own coding work at every rung: real work-order-shaped jobs — a written spec, more than one file, a module plus a test suite with a mechanical pass/fail — at minimal, low, high and max, in one harness, more than one sample per cell, receipts published the way the first battery’s were. If low matches max on those, our rule stands for coding too, and the ladder is a story about Cursor’s harness. If max pulls away as the jobs get longer, the rule gets a carve-out: the rung follows the length of the task. Either result is publishable. We’ll run it and print what we find.

    The bottom line for an operator

    If your work is short, bounded calls — extraction, checking, verdicts, drafting to spec — run low. We have 52 metered calls that say the expensive rungs buy you nothing there, and our default hasn’t changed.

    If your work is a coding agent chewing through real jobs, the only rung-by-rung evidence that exists says turn it up: on Cursor’s own ladder, max solves 41.6% of tasks against minimal’s 24.3%, and every rung between them earns its step. That evidence is a vendor’s, run in the vendor’s harness, on September’s model build — hold it at that weight, not more.

    The mistake isn’t picking the wrong rung. It’s running one default across both shapes of work and calling it a policy. The dial is real. What it pays for depends on the length of the job in front of it — and now there are two published result sets, ours and Cursor’s, that say exactly that from opposite ends.

    Sources: BenchLeader, “Muse Spark 1.3” model page and CursorBench leaderboard (data as of November 8, 2026; CursorBench results published by Cursor via the Epoch AI Benchmarking Hub, Spark 1.3 results dated September 2, 2026). Our dial test: “We Ran Muse Spark’s Reasoning Dial Through 52 Calls. The Cheapest Setting Never Lost.” (Tygart Media, November 7, 2026), method and receipts in the Tygart-OS fact-gated fleet record on GitHub.


    Want this thinking applied to your own work? Book a call with Will Tygart — 30 minutes, and we start from your receipts, not a pitch deck.

  • The Agent-Ready Site: What Kin’s WebMCP Launch Means for Every Business Website

    The Agent-Ready Site: What Kin’s WebMCP Launch Means for Every Business Website

    On October 23, 2026, Kin Insurance became the first U.S. home insurer to enable WebMCP in its quoting experience — an open web standard that lets an AI agent work directly with kin.com, so a homeowner can tell ChatGPT "help me shop for home insurance" and get back a real quote. Strip away the insurance details and what remains is a pattern every business website is about to be measured against: is your site built for the agent your customer sends?

    Most businesses are still arguing about whether to let agents in. Kin skipped that argument. The interesting question is what its launch is made of, layer by layer — because three of the four layers are already visible in our own fleet's numbers.

    Agent-Ready Fleet Standard

    Make Your Site Machine-Ready for the 62% Bot Wave

    Field-ready quick cards, fillable 4-layer audit worksheets, and AI-powered bot runbooks built directly from this guide.

    Quick Reference FREE

    Agent-Ready Quick Card

    2-page field card: The 4 layers — welcome the machine (door vs. wall), structure for carrying (answers not brochures), give the agent a way to act (WebMCP), and measure what machines do (citation scoreboard) — on one card, condensed from the article body.

    Download Free PDF

    Direct download • No email gate

    Working Pack $7

    The Agent-Ready Site 4-Layer Print Pack

    5-page printable & fillable working pack: Layer 1 Door-or-Wall decision checklist (Kin vs Insurify default audit), Layer 2 answers-not-brochures worksheet with verbatim FAQ tracker modeled on 155-of-166 rollout, Layer 3 declared-action mapper with inputs-in-order sequence sheet, and Layer 4 citation scoreboard log (1.45M across 922 pages tracking model).

    Get Working Pack ($7) →

    Instant checkout • Square verified

    AI Intensive
    Book for Bots $17

    Feed Your AI: The Agent-Ready Site Bot Book

    Feed directly to ChatGPT or Claude: 4 intensive AI-run routines (Welcome Posture Interview, Readable Content Auditor, Declared Action Designer, Citation Scoreboard Diagnostic) with embedded executive command router (“software made of words”).

    Get AI Bot Book ($17) →

    Software made of words • Instant delivery

    Layer 1: Decide to welcome the machine

    Agent traffic is not coming; on our own sites it is already the majority — roughly 62% of visits across the fleet we run are bots and agents, not people. The only choice left is whether that traffic meets a door or a wall.

    Kin chose the door, publicly and in advance: it had already announced that AI shopping agents are welcome on kin.com rather than blocked, naming Meta's Muse among them. The opposite choice exists in the same industry — in September, insurance marketplace Insurify blocked Muse from its comparison platforms, arguing an agent could pull a price stripped of the context that makes it meaningful. Both are coherent positions. What is no longer available is having no position: a site that has not decided is a site whose default settings decide for it.

    Layer 2: Structure the content so a machine can carry it accurately

    An agent can only repeat what it can read, so the agent-ready site is built out of answers, not brochures: one real question per page, paragraphs that stand alone as complete ideas, and structured data underneath that states the facts in machine-readable form.

    This is the layer we work in every day, and it is unglamorous, mechanical work. Tonight, on one operator site in our fleet, we finished putting structured FAQ data — drawn from each page's own questions and answers, verbatim — onto 155 of its 166 articles, because agents cite what is structured and skip what is implied. Multiply that instinct across every page a business owns and you have the content layer of agent-readiness: nothing important lives only in an image, a video, or a sales conversation.

    Layer 3: Give the agent a way to act, not just to read

    WebMCP is the layer most sites do not have yet: the site declares the actions an agent may take — get a quote, with these inputs, in this order — so the agent executes a designed path instead of improvising clicks across a human interface.

    Kin's version is a quote flow, and its testing shows why the layer matters: agents reached a finished quote after asking the consumer only a handful of questions, because the path was declared and the carrier's data filled the rest. The equivalent for any business is the moment a visit becomes a transaction — a booking, a quote, an order. Our own commerce thinking already runs on two rails, one built for humans at a checkout and one an agent can complete; Kin just shipped the insurance version of the second rail, first.

    Autonomous Commerce Engineering

    Build Your Agent-Usable Rail Before Customers Stop Browsing

    Kin proved an agent can reach a finished quote in a handful of questions when the path is declared. Equip your technical and product teams with printable inputs-in-order worksheets, two-rail commerce planners, and interactive AI routines that convert human checkout forms into WebMCP-compliant endpoints.

    🤖

    What’s In The Agent-Ready Suite:

    • Layer 1 Door-or-Wall: Decision checklist & WAF audit.
    • Layer 2 Answers-Not-Brochures: 155-of-166 FAQ tracker.
    • Layer 3 Declared Action: Inputs-in-order sequence mapper.
    • Layer 4 Scoreboard Log: 1.45M across 922 pages tracking.
    • AI Bot Book: 4 interactive routines & command router ($17).
    Secure 1-Click Square Checkout

    Layer 4: Measure what the machines do

    Agent-readiness you cannot measure is a vibe. Kin will know whether agents quote it, because the protocol makes agent sessions countable; the rest of us measure the read layer — which pages agents cite, which questions they bring, how the share moves.

    On tygartmedia.com, we track AI citations from our own search-engine exports rather than a vendor's estimate: 1,459,726 citations across 922 cited pages in the October 15 export, up from 269,399 across 324 pages in the September 27 export. Those numbers are the scoreboard for layers 1 and 2. The day an agent can transact here, layer 3 gets a scoreboard of its own.

    Where our fleet honestly sits

    Layers 1, 2, and 4 are running here today — welcome posture, structured content, citation measurement. Layer 3, declared agent actions, is what Kin shipped first, and it is the next build. That is a fair summary of most of the web right now: readable by agents, citable by agents, and still requiring a human to show up for the transaction itself.

    The businesses that treat that gap as a roadmap, rather than a surprise, are the ones whose sites will be ready when their customers stop browsing and start sending.

    Specification Comparison

    Compare Agent-Ready Tools & AI Implementation Systems

    Choose the depth of operational rigor needed for your website: field quick card, printable audit working pack, or interactive bot-driven runbook.

    Field Summary

    Agent-Ready Quick Card

    2-page field card condensing the 4 layers into an executive reference standard.

    • 4-Layer architectural summary on one card
    • Door vs. Wall posture matrix (Kin vs. Insurify)
    • Answers-not-brochures & standalone paragraph test
    • WebMCP declared action & two-rail commerce summary
    • Citation scoreboard benchmarks (62% bot baseline)
    FREE
    Download Quick Card (PDF)

    Instant direct download • No email gate

    Static Working Pack

    The Agent-Ready Site 4-Layer Print Pack

    5-page printable & fillable audit system with complete engineering worksheets and scoreboard logs.

    • Layer 1 Door-or-Wall decision checklist & default audit
    • Layer 2 answers-not-brochures worksheet (1-question test)
    • Verbatim FAQ structured-data tracker (155-of-166 rollout model)
    • Layer 3 declared-action mapper & inputs-in-order sheet
    • Two-rail commerce planner (Human UI vs. Agent Rail)
    • Layer 4 citation scoreboard log (269k to 1.45M growth model)
    $7.00
    Get Working Pack ($7) →

    Instant delivery • Square checkout

    AI Intensive
    Book for Bots

    Feed Your AI: The Agent-Ready Site Bot Book

    Structured text document feeding 4 executable AI routines directly to ChatGPT or Claude to audit pages, generate schema, and design declared actions.

    • Routine 1: Welcome Posture Interview (/welcome-audit)
    • Routine 2: Readable Content Auditor (/content-audit)
    • Verbatim Schema Generator: JSON-LD FAQPage (155-of-166)
    • Routine 3: Declared Action Designer (/action-design)
    • Routine 4: Citation Scoreboard Diagnostic (/citation-diag)
    • Routine 5: Executive Roadmap Protocol (/roadmap)
    • Router: Embedded command router (“software made of words”)
    $17.00
    Get AI Bot Book ($17) →

    Software made of words • Instant delivery

    Frequently asked questions

    What is WebMCP? An open web standard that lets an AI agent interact with a website through a machine-usable path the site itself declares — no plug-in and no screen-scraping. Kin enabled it in its home insurance quoting experience on October 23, 2026, the first U.S. home insurer to do so.

    What makes a website "agent-ready"? Four layers: a deliberate decision to welcome agent traffic instead of blocking it by default; content structured as standalone answers with machine-readable data underneath; a declared path that lets an agent complete an action, such as a quote or booking; and measurement of what agents actually do on the site.

    Do agents really visit business websites that much? On the fleet we operate, roughly 62% of visits are bots and agents. The share varies by site, but the direction does not: the reader a growing share of your pages serve first is a machine deciding what to show its human.


    Source: Kin Insurance announcement via PR Newswire, October 23, 2026. Fleet figures are Tygart Media's own: bot share from our site analytics; citation counts from our Bing AI Performance exports of September 27 and October 15, 2026.

    Updated Nov 1, 2026 — added the free agent-ready quick card, 4-layer print pack, and agent-ready bot book downloads to this guide.

  • AI Visibility: The LLM Optimization Strategies We Actually Run

    AI Visibility: The LLM Optimization Strategies We Actually Run

    Most LLM optimization advice is written by people who have never watched an engine decide whether to cite them. We have — monthly, in the engine’s own reports, across a small fleet of sites. What follows is not a theory of AI visibility. It is the playbook running on our sites right now: seven strategies, each with the number that proves it, each boring enough to actually compound. If a strategy can’t name the report that would show it working, it isn’t a strategy. It’s a hope with a webinar.

    Engine Grounding Toolkits

    AI Visibility Toolkits: Quick Card, 7-Check Playbook & Cite-Me Bot Book

    Printable citation logs, liftable paragraph tests, consolidation maps, and machine-executable AI audit routines built directly from our fleet grounding ledger.

    Field Reference
    FREE

    AI Visibility Quick Card

    2-page field summary: the seven boring compounding strategies condensed onto one card — single-question titles, liftable blocks, feeding winners, demand calendars, drawer numbers, extraction handles, and entity legibility.

    Download Free PDF

    Direct download • No email gate

    Working Pack
    $7

    AI Visibility Playbook Pack

    5-sheet printable/fillable pack: One-question title planner (33% & 36% examples), Liftable-paragraph checklist, Consolidation feeder log (1,635 → 2,790 vs 304 → 6 tracker + orphan redirects), Grounding-query calendar, Publish-numbers inventory, Fee table schema guide, and 1-sentence entity worksheet.

    Get Playbook Pack ($7) →

    Instant checkout • Square verified

    AI Intensive
    Book for Bots
    $17

    Cite-Me Coach: Bot Book

    Feed to ChatGPT or Claude: 6 interactive optimization routines (Question-Match Interview, Liftability Audit, Consolidation Verdict Walkthrough, Query-Report Calendar Builder, Proprietary-Number Generator, Extraction & Entity Diagnostic) + embedded command router.

    Get Bot Book ($17) →

    Software made of words • Instant delivery

    1. One question per page, in the asker’s words

    An AI answer is assembled from pages that match the question being asked — so build pages that are the answer to one real question, titled the way a person actually asks it. Our certification guide for restoration contractors doesn’t chase “IICRC resources.” It answers what IICRC certification is, what it costs, and how to keep it current — and on Bing’s ledger we hold about a third of all citations for “what is iicrc certification” and 36% for “iicrc certification cost.” Nobody types marketing copy into an AI. They ask questions. The page that sounds like the answer wins the citation.

    2. Write paragraphs an engine can lift

    Citation is extraction. When an engine grounds an answer, it pulls the passage that stands on its own — the paragraph that contains the fact, the number, and the context in one self-contained block. So write that way on purpose: every paragraph a complete little model that still makes sense if it’s the only thing quoted. Buried facts, pronoun chains that need the paragraph above, and throat-clearing introductions are all invisible to an extractor. A page of liftable paragraphs beats a beautiful essay the engine can’t cut a piece from.

    3. Let the engine consolidate — then feed the winner

    Given two similar pages, an engine picks one and starves the other, and it shows you the execution in the reports. Our flagship certification page climbed four straight monthly exports — 1,635, then 1,913, then 2,454, then 2,790 citations — while its near-duplicate twin fell from 304 to 6. The strategy is to cooperate with that verdict: one page per topic, the cluster’s links pointed at the winner, old strays redirected to it. We spent part of today doing the plumbing version of this — three orphaned URLs that were leaking to our homepage now land on the pages that earned the citations. Fighting consolidation splits your authority. Feeding it compounds.

    LLM Optimization Worksheets & Bot Routines

    Run Our 7 Engine Grounding Checks Across Your Content

    When an AI engine evaluates your site against competing pages, it starves vague essays and feeds self-contained, data-dense winners. Our printable 5-sheet Playbook Pack gives you the exact winner vs. twin consolidation logs (tracking the 1,635 → 2,790 compounding path), orphan URL redirect sheets, and fee table extraction schemas we use every month — or feed our $17 Bot Book to ChatGPT or Claude to interrogate your titles, score your paragraphs for extractor readiness, and generate your demand calendar automatically.

    ☑

    What’s In The Toolkit:

    • Title Planner: Asker-words question worksheet.
    • Liftable Checklist: Fact + Number + Context test.
    • Consolidation Log: Winner vs twin tracker & redirects.
    • Demand Calendar: Engine grounding export intake.
    • Drawer Numbers: Proprietary data report cards.
    • Entity Diagnostic: 1-sentence agent first-sort test.
    • AI Bot Book ($17): 6 AI prompt routines + router.
    Secure 1-Click Square Checkout

    4. Let the engine write your editorial calendar

    The most valuable document in AI visibility is free: the grounding-query report, which lists the actual questions your pages were pulled for — including ones you’re cited on weakly, and new ones appearing for the first time. That list, plus the topic opportunities the same dashboard surfaces, is a calendar written by demand instead of guesswork. This article exists because that report said people are asking how LLM optimization works. Half of what we publish starts as a line in an export. Guessing topics is a tax on people who won’t open a free report.

    5. Publish numbers nobody else has

    An engine cannot ground an answer on your competitor’s guess — but it can ground one on your data, if your data is the only place the number exists. First-party figures are the one content asset that can’t be copied by writing faster: your exports, your measurements, your before-and-afters. We print our own citation report card in public, limits included, and it keeps getting cited precisely because no one else can produce those numbers. Whatever your industry measures privately is a citation asset sitting in a drawer.

    6. Structure for extraction

    Give the machine clean handles: question-and-answer sections whose text matches the structured data behind them, tables with the real figures instead of ranges blurred into mush, section anchors a citation can point at. When we rebuilt our flagship page, we replaced three inconsistent blended price ranges with one fee table carrying the actual numbers — tuition, exam fee, renewal — each in the open where an extractor can take it. Vagueness feels safe to writers. To an engine, it’s just unusable.

    7. Be legible as an entity

    Agents do the first sort now — of vendors, of hires, of experts — and they sort on what your profiles actually say. We learned this watching a genuinely excellent operator get skipped by an automated screen because his headline was three abstract nouns and no signal. Your site, your company page, and your profiles should each state, in plain words, what you do, for whom, and where — written for the machine doing the first read and the human doing the second. If an agent can’t summarize you accurately in one sentence, your visibility strategy has a hole no content calendar will fill.

    Compare AI Visibility Toolkits

    Choose the quick reference card, printable working pack, or machine-executable AI playbook that fits your publishing workflow:

    Free Field Summary

    AI Visibility Quick Card

    2-page field reference: all seven compounding strategies condensed onto one card — title matching, liftable paragraphs, consolidation rules, engine demand calendars, first-party data assets, structured handles, and entity legibility.

    FREE
    direct download
    • Strategy 1: One Question Per Page in Asker’s Words
    • Strategy 2: Paragraph Extraction Architecture
    • Strategy 3: Consolidation Feeder & Redirect Plumbing
    • Strategy 4: Grounding Export Editorial Intake
    • Strategy 5: First-Party Data & Public Report Cards
    • Strategy 6: Real Fee Tables & Section Anchors
    • Strategy 7: Entity Legibility Agent First-Sort

    Download Free PDF

    Working Pack

    AI Visibility Playbook Pack

    Printable, fillable 5-sheet working pack with title worksheets, paragraph checklists, consolidation trackers, demand intake sheets, and schema guides.

    $7.00
    one-time
    • Sheet 1: Title Planner (33% & 36% Bing Share Benchmarks)
    • Sheet 2: Liftable-Paragraph Fact + Number + Context Checklist
    • Sheet 3: Consolidation Log (1,635 → 2,790 vs 304 → 6 Tracker)
    • Sheet 4: Grounding-Query Editorial Intake & Triage Sheet
    • Sheet 5: Proprietary Numbers Inventory & Report Card Template
    • Sheet 6: Extraction Handles & Fee Table Precision Guide
    • Sheet 7: Entity Legibility 1-Sentence Agent Worksheet

    Buy Playbook Pack ($7) →

    AI Intensive
    Book for Bots

    Cite-Me Coach: Bot Book

    Structured 7-page AI playbook for ChatGPT, Claude, and Gemini: 6 machine-executable optimization routines + embedded command router.

    $17.00
    one-time
    • Routine 1: Question-Match Interview (/interview-titles)
    • Routine 2: Liftability Audit & Rewrite (/audit-liftability)
    • Routine 3: Consolidation Verdict Walkthrough (/verdict-walkthrough)
    • Routine 4: Query-Report Calendar Builder (/build-calendar)
    • Routine 5: Proprietary-Number Generator (/mine-numbers)
    • Routine 6: Extraction & Entity Diagnostic (/diagnostic-entity)
    • Embedded Command Router & Prompt Center (/cite-me-router)
    • Full Site Publication Certification Routine (/full-audit)

    Buy Bot Book ($17) →

    The compounding is the strategy

    None of these moves trends. Each is a small, verifiable bet placed monthly against the engine’s own ledger — which is why measurement isn’t step eight, it’s the ground the other seven stand on; our tracking method is written up here, and the receipts we’d demand from anyone selling this work are in the buyer’s test. LLM optimization, done honestly, is a publishing discipline with a feedback loop — not a hack, not a plugin, not a score you buy. The engines are reading either way. The only choice is whether what they find is built to be cited.

    Updated Nov 1, 2026 — added the free AI visibility quick card, AI visibility playbook pack, and cite-me coach bot book downloads to this guide.