AI Strategy - Tygart Media

Category: AI Strategy

AI strategy for operators: deploy Claude, automate real workflows, and build AI-native systems that compound. Field notes and playbooks from Tygart Media.

  • The status file held this week

    The Machine Room · Under the Hood

    The useful motion this week was not a new outage. The sites answered. The motion was a log that stopped needing a janitor commit, a channel that stayed dark, and a pricing ticket that finally closed on the URLs the order named. I am writing this from the last seven days of tygart-media/tygart-workers and the work-order board. The shared Second Brain page has not moved since late September. Session Log is quiet. No client names. No invoices. The public idea-mill repos that sat idle are not the story.

    The status file stopped eating itself

    Chief of Staff on this desk is still an hourly poll, not a person in a chair. It reads Notion, tries Teams, writes a run block to ops/cos-status.md, and commits. That file is the twin of the Notion receipt. Last week the writer treated the newest run as if it were the whole file. History survived only when a second commit put the older blocks back underneath. Three restore commits in four days. The messages were explicit: restore prior CoS poll log under the 08:10 PT run, under the 09:09 and 13:08 PT runs, under the 14:08 PT run. Twenty-three seconds between the clobber and the apology on the last of those.

    This week the pattern is gone. I searched the repo for restore commits after 9 October. The last one is the 14:08 PT pair from that day. Every subsequent poll commit — 10 October through 16 October, morning, afternoon, and the 02:00 PT runs — writes a new block and leaves the previous ones in place. The file on main, as of the 15:00 PDT run on the 16th, holds the newest block at the top and the prior runs underneath it. No janitor commit. The instruction the poll is supposed to follow — append, do not replace — is now in the writer that lands the run, not in the commit that apologizes for it.

    That is the patch that held. I do not know which seat changed the writer. The commits themselves are still the poll. The evidence is the absence of the second commit. A log that no longer depends on version control as the undo button is a log. Three days of clean appends after a week of restores is the difference between a scratch pad and a record the next seat can trust.

    Teams #ops is still a name in the file

    Every run block this week starts the same way. Teams #ops, Graph 403, Office 365 license, on read and on send. The channel exists. The poll names the channel id. Search for messages after 1 October comes back empty or historical. No post.

    That is not a missing webhook. The bot can see that the channel is there and cannot read it or write it. A license wall looks like silence from the other side. The other side is not silent. It is unpaid for the token we are using, or the token is on a seat that Microsoft will not let into that channel. The status file is consistent across every run I read: Graph 403, Office 365 license, no post, all week.

    The operational effect is the same as last week and still worse than a red dashboard. The poll does not stop. It records the 403 and moves on to Notion. The desk that was supposed to hear the stale-flag in #ops does not hear it. The only place the flag lands is the file that now, at least, keeps its own history. Two failures no longer stacked. One is fixed. The channel that should have been the doorbell is still a 403.

    Nothing was patched here. No license was added. No alternate doorbell was cut over. The runs keep attempting send, keep getting 403, keep writing “No post.” That is the open patch. Until the Graph call returns something other than 403, #ops is a name in a markdown file.

    The pricing hubs finally got the numbers on the old URLs

    On 7 October Haiku 5.5 shipped. List price under 100k tokens is $0.10 in and $0.50 out. Sonnet 5.5 cache reads were cut from $0.20 to $0.10. Haiku 4.5 moved to legacy. The desk already had a work order for it. The order was titled for the patch, not for a new essay: Haiku 5.5, Sonnet 5.5 cache cut, Max and Team API credit, patch the pricing hubs, keep the slugs. Assign was TM Site. Priority Now. Human gate off. The done-when was specific. Touch the existing posts in place. /claude-ai-pricing/, /claude-fable-5-pricing/, /grok-vs-claude-pricing/. Bump the verified date. Do not mint a new URL.

    Last week a sibling essay landed at /claude-haiku-5-5-pricing/ and the hubs stayed on the old numbers. The poll correctly refused to call that done. This week the hubs moved. The work-order page shows Status Done, closed 12–13 October by the CoS-Grok loop. The summary names the live artifact: /claude-ai-pricing/ last verified 12 October 2026 lists Haiku 5.5 current ($0.10/$0.50 ≤100K) and Sonnet 5.5 cache read $0.10. The other two slugs were part of the same order. The sibling essay can stay. It is no longer the only place a reader can find the new rates. The old links, the ones the work order named, now carry the current numbers.

    That is the second patch. The restraint last week was correct. Closing the ticket because a different URL existed would have been the worse move. Editing the three slugs in place was the done-when. It landed.

    What I would not repeat

    I would not treat a new URL as a close on a keep-slugs ticket. The order said do not mint essay pages. A published post feels like the patch. It is a different object. The hub is what the old links point at. The old links are the product. A sibling essay does not rewrite them. The poll was right to leave the ticket open until the hubs themselves moved. That is the refusal that paid off this week.

    I also would not keep restoring a status file by hand and calling that the patch. Three restore commits in four days was a procedure, not a fix. The absence of those commits this week is the evidence the writer changed. The restore commit proved we noticed. It did not prove the writer appends. The clean runs prove it.

    What is still open

    The open patch is Teams #ops. Every run this week records the same Graph 403. The channel exists. The bot cannot use it. Until the license or the token changes, the doorbell stays silent and the only record of the stale flags is the file the poll writes.

    Behind that, the board is still full of older tickets that have not moved. The Friday runs count sixteen open or In-progress work orders, every one of them older than two hours. WO-186 is still Not started. Human gates stay parked on purpose: secrets, DNS, live-site edits, anything that mints or sends. The pricing ticket is no longer one of them. The rest of the pile is the reason the board looks busier than the non-poll commits. The poll keeps filing a true report into a file it now keeps, about a channel it cannot post to, about tickets it is not allowed to close.

    That is the week. Not a recap. Three items that moved or failed to move, one refusal that held, one door still open.

  • The Best Recovery Product Reads the Name Against the Hold

    The Best Recovery Product Reads the Name Against the Hold

    The state already holds the money. The person still has a name that may not match the old address. That gap is the product.

    The idea mills keep minting a finder chatbot, a claim-form filler, and an unclaimed.ai. Three names. One object. A letter, an old check, or a utility deposit notice that does not sit next to the state database the National Association of Unclaimed Property Administrators already aggregates.

    NAUPA estimates more than $70 billion in unclaimed property sitting with state treasuries. Roughly one in seven Americans has something waiting. States return more than $3 billion a year. Those numbers have been stable enough for years. What changed in 2026 is the infrastructure around them.

    Indiana’s Unclaimed Property Division had already returned nearly $90 million by mid-October 2026, breaking the prior full-year record of more than $88 million set in 2025, with nearly $1 billion still sitting. Washington returned $182 million in fiscal 2025 against $503 million received and still holds more than $2.8 billion. Louisiana lists $1.2 billion outstanding, with one in six residents carrying a claim averaging about $900. The money is not theoretical. It is already on the books.

    On October 6, 2026, Claimio opened a purpose-built API for unclaimed-property search, matching, and recovery handoff. The platform had already helped recover more than $8.5 million for more than 3,000 customers and monitors more than 250 million records. It is built so fintechs, employers, and AI agents can run the search inside their own product and hand the paperwork off. Performance-based. No upfront fee to the owner. That is the first real plumbing the mills have had for this category.

    California added digital financial assets to its unclaimed property statute in late 2025. Other states expanded reporting, tightened exemptions, and raised audit pressure on holders. NAUPA is moving reporting formats toward XML in phases starting 2027. The databases are getting cleaner and more queryable at the same moment agents can call them.

    The product is the join.

    Do not build “AI for state treasuries” or “AI for finders.” Those slogans die in a demo. The customer is holding an old bill, a canceled check stub, or nothing at all except a name and the last address they remember. They want to know if the state already has the money under a version of that name. The product is the page that puts the name next to the hold.

    Primitive one is photo-and-PDF review. The mills have been shipping receipt readers for months. Greg Isenberg’s stream and the daily micro-SaaS accounts keep splitting that reader into a chatbot, a form filler, and a “claimcheck.ai.” The input here is the old utility bill, the final bank statement, the insurance notice, or the letter from a previous address. Name in the header. Address on the stub. Account number if it survived. The model extracts the fields. The human never has to type them twice.

    Primitive two is the public hold. Every state runs a free search. MissingMoney.com and the individual state portals already exist. The gap is that almost nobody checks every state they have lived in, and almost nobody keeps the old documents that make the match precise. The product sits between the document the person still has and the database the state already published.

    The wedge is a free checker. Not a platform.

    Paste the name and the last address you remember. Or upload the photo of the old bill. Thirty seconds later: match, possible match, or none. If it is none, you still captured a labeled name and address. If it is a match, the system shows the state, the property type, and the amount range when the state publishes it. You do not file yet. You see the hold.

    That is the only honest first action. Zero risk. The stranger already has the name. They already hate the idea that money they once owned is sitting with a government office they have never visited. Thirty seconds is short enough that they will try it this week.

    The compounding path is the labeled map of what actually gets recovered. After volume, you know which property types match on name alone, which ones require the old account number, which states demand a specific affidavit, and which addresses produce the highest false-positive rate. That map is not a third dashboard. It is the dataset that makes the next match better and the next claim cheaper. The mills will keep proposing a new .ai name for each state form. Ignore the names. Join the line. Keep the map.

    Irreversible steps require a human signer. Filing the claim moves money. Some states ask for ID, proof of address, or a signed form. Models extract the fields, draft the cover letter, and package the exhibits. A person reviews and owns the send. The same rule that applies to tax filings, customs claims, and medical appeals applies here. Models draft. People own the send.

    Monetization is contingency on recovery or a flat fee once the claim is prepared and the owner has signed. You can also sell the monitoring layer to the person who already has one hit: watch the next five years for new property under the same name. Or sell the API match to the fintech that already has the customer’s name and last four addresses. The free checker is the acquisition. The map is the moat.

    The mills have already floated pieces of this. One post wants a refund radar for marketplace sellers. Another wants a Social Security clawback defense. A third wants an IRS nonfiler catch-up service. Useful pieces. Wrong cut if you leave them as separate products. The owner does not wake up wanting a new dashboard for abandoned property. They wake up because a letter arrived, or because a family member died and the house is full of old paperwork, and they want to know if the state already has the money.

    Someone will own the labeled map of noticed versus held. The mills will keep proposing a new .ai name for each state portal. Ignore the names. Join the line. Keep the map.

    Will Tygart — Tygart Media.

    This is the idea-mill series.

  • I Am Capability

    Two years ago my friend Frank Dobosz asked me a question I couldn’t answer the way he wanted. “I don’t understand, Will. What is your product?”

    I said, “I’m the product.”

    He said, “No — but what are you selling?”

    “I am capability. Will Tygart is capability.”

    He didn’t understand it. Most people don’t. This morning I found out the thing has a name, and a researcher who’s been studying it for forty years.

    His name is Gary Klein. In the 1980s the Army hired him to study how fireground commanders make decisions. The textbooks said a good decider lists the options, weighs the pros and cons, and picks the best one. The commanders did almost none of that. One of them told Klein, “I don’t make decisions.” Pressed, he admitted there were options — it was just usually obvious what to do.

    Klein called it recognition-primed decision making, and he wrote it up in Sources of Power in 1998. Here’s how it actually runs:

    You recognize, you don’t analyze. A lifetime of situations is stocked in your head. A new one shows up and it rhymes with the old ones. You don’t build a spreadsheet. You see it.

    The pattern carries its own move. Every stored situation brings the action that worked last time. You’re never starting from a blank menu.

    You run the tape. You play that move forward in your head — about sixty, seventy percent of the way — watching for where it breaks. If it holds, you go. If it breaks, you throw the path away and run the next one.

    That’s the whole engine. And here’s the part nobody prices: every path up a mountain is uphill. So the skill was never the climbing. The skill is pricing the paths before your legs are spent.

    It’s the supermarket line. You’re standing in a slow line and the one two over looks shorter. Switching has a cost — most people either never switch, and die in the slow line out of pride, or they twitch-switch all day and lose more than they gain. The move is running the math — switch cost against distance left — in about a second, and only moving when it pays.

    I always thought this was called paying attention. Customer service. My version of it: I put the chair underneath someone as they’re sitting down, before they even know there isn’t a chair there. Same engine, pointed at a person instead of a problem. You simulate the next ten seconds of somebody’s life and you’re already there when they arrive.

    Now — when is this worth trusting, and when is it just confidence wearing a costume? Klein answered that too, and he answered it with his natural enemy. In 2009 he and Daniel Kahneman — the bias researcher, the man who built a career showing intuition fails — published a paper together in American Psychologist agreeing on the conditions. Intuition is trustworthy when the environment has real, learnable patterns, and you get fast, honest feedback on your calls. Mine qualifies. Jobs, clients, a screen that either shows the line or doesn’t. The feedback hits immediately and it doesn’t flatter. That’s why this is earned and not lucky. In a swamp with no feedback, the same confidence would be a trap — and I’ve watched people drown in that swamp calling it instinct.

    Klein also turned the tape-running into a ritual anyone can borrow, called the pre-mortem: before you commit, declare “it’s six months from now and this failed — why?” A 1989 study found that imagining an outcome as already settled surfaces about thirty percent more reasons than asking what might happen. It’s the simulation, run out loud, with permission to say the uncomfortable part.

    And then there’s the piece that closes the loop for me. An AI does pattern matching too — Klein just described what a model does. The difference is the feedback. The commander’s feedback hit his own skin. A model learns from reports of the fire, written by other people, and a report only carries what the writer could say out loud. The tacit part — the part the doer knows but can’t tell — gets flattened on the way in. So the model holds an inference of experience. Never the experience.

    What’s left, the part that doesn’t flatten, is taste. Taste is a whole history of seeing, compressed into this, not that. It’s how a painter who learned from other painters ends up moving somebody who can’t paint at all — the viewer borrows the painter’s context and it lands. Capability can be hired. Taste transfers.

    So can you bottle it? Honestly — partially. You can’t bottle the seeing. That lives in the reps. But you can bottle the evidence: I record my working sessions, so the judgment can be watched instead of described. And you can bottle the patterns: every rule my operation runs on — kill a path the moment it stops earning its time, answer every knowable question before the work ships — is a decision I made once, written down, still running when I’m not in the room.

    That’s what a client actually buys from Tygart Media. Not deliverables. Judgment, embedded in their business, running their paths before they walk them.

    Frank asked the wrong question two years ago. There was never a product on a shelf.

    Where there’s a Will, there’s a way. Turns out there’s a literature on it.

  • The Best Clawback Product Reads the Notice Against the Rule

    The Best Clawback Product Reads the Notice Against the Rule

    The agency already set the withholding rule. The family still holds a notice that may not match it. That gap is the product.

    The idea mills keep minting a Social Security chatbot, a waiver-form filler, and a clawback.ai. Three names. One object. A paper letter that does not sit next to the Emergency Message the Social Security Administration already issued, or next to the rights language the Office of the Inspector General later measured as missing.

    Greg Isenberg’s stream and the daily micro-SaaS accounts keep splitting the same reader. One post wants an agent that finds class-action money in your inbox. Another wants a refund chaser for marketplace sellers. A third wants a photo of a government notice dropped into a chat, with a form on the other side. The useful cut is narrower. The notice is already in the mailbox. The rule is already public. The join is the company.

    Why now is a number, not a feeling

    On April 25, 2025, SSA issued Emergency Message 25029. New Title II overpayment notices (retirement, survivors, SSDI) default to withholding 50 percent of the monthly benefit if the beneficiary does nothing after the roughly 90-day window. That replaced the 10 percent cap that had been in place for most of 2024. The agency has said it sends roughly two million overpayment notices a year across its programs.

    In September 2026 the SSA Office of the Inspector General released audit 152407 on OASDI overpayment notices. Of the 126 overpayments sampled, 46 percent of the notices did not meet policy. Missing explanations of how and when the overpayment occurred. Omitted reconsideration and waiver rights. Inaccurate dollar amounts. Conflicting language. The projection for the roughly one million overpayments established in FY 2023 was more than 469,000 deficient notices. Sixty-three percent of sampled explanation requests were also processed incorrectly.

    Those two facts sit next to each other. The default recovery rate went up. A large share of the notices that trigger the recovery still fail the agency’s own completeness rules. The adult child who opens the letter does not need a chatbot. She needs to know, this week, whether the page she is holding states the 50 percent default, lists the three forms, and shows a calculation she can check against her mother’s benefit history.

    Two primitives, one wedge

    Primitive one is the photo or PDF of the private notice. The mills have been shipping receipt readers for months. The input here is the overpayment letter, the envelope, or the screenshot from the my Social Security account. Amount claimed. Period covered. Withholding language. Rights language. Deadline.

    Primitive two is the public rule and the public file. EM-25029 and its later revision. The three forms (SSA-561 Request for Reconsideration, SSA-632 Request for Waiver, SSA-634 Request for Change in Repayment Rate). The 30-day window that usually pauses collection while the request is reviewed. The OIG’s own finding that nearly half the notices omit material elements. Nothing here is secret. The agency was required to write the rule and the forms. The OIG was required to measure the notices.

    The product is the join. Photograph the notice. Thirty seconds later: default withholding stated correctly or not, rights language present or missing, amount line that can be checked against a benefit history printout, or the page is too thin to say. No account for the first answer. If a stranger will not photograph one letter this week, you do not have a company. You have a policy thread.

    The compounding path is the labeled map, not a third dashboard

    After the free checker has volume, the useful asset is the map of notice versus rule. Which field offices or notice templates omit the waiver language most often. Which calculation methods produce the largest unexplained gaps. Which waiver arguments, once a human has signed and the case has closed, actually move the withholding rate or the debt itself. That scoreboard is the seed of the later B2B SKU for advocates and legal-aid shops. It is not a dashboard of “possible savings.” It is the labeled join of the document the family already holds and the document the agency already published.

    Models draft the packet. People own the send. Filing SSA-561, SSA-632, or SSA-634, or calling the field office to negotiate a lower rate, is an irreversible step that changes a benefit check. The software can assemble the financial statement, flag the missing rights language, and draft the fault argument. A human signer presses the button. Charge after the free verdict shows a clear mismatch, or do not charge. Do not sell the map before you have closed real money back to real households.

    What not to build

    Do not build another SaaS that promises to “manage all of Mom’s Social Security paperwork.” That is a platform. The first action a stranger will take this week is photographing one notice, not creating an account and granting access to a lifetime of benefit records. Do not build an AI that files the form without a human on the send. The agency already has the power to withhold half a check; the response still has to be owned by a person who can be reached when the next letter arrives. Ignore the new .ai names. Join the line the notice and the rule already form.

    Why this cut, not the last one

    The leakage essay was tariffs, seats, and subscriptions. The rebate essay was a nameplate. The recall essay was a label. The short-pay essay was a contractor packet. The bill essay was an EOB against a hospital file. The tax essay was a notice against the roll. The utility essay was a statement against a filed tariff. The housing essay was a unit against a score. The delay essay was an itinerary against a code. The HOA essay was an assessment against a study. The 401(k) essay was a fee against a filing. The pharmacy essay was a receipt against an acquisition file. This one is the benefits version of the same primitive pair: a letter the adult child already can photograph, plus a public rule and public audit the agency was forced to publish, joined in the week the 50 percent default starts to bite.

    The noticing used to require a benefits counselor and a long hold. It now requires a model that can read the notice and a person who will sign the form. Recovery still works because the first check costs the family almost nothing. Charge them after the score file and the notice refuse to meet, or do not charge them.

    Someone will own the labeled map of notice versus rule. The mills will keep proposing a new .ai name for each SSA form. Ignore the names. Join the line. Keep the map.

    Will Tygart — Tygart Media.

    This is the idea-mill series.

  • The Smallest Sentence

    The Smallest Sentence

    Listen — narrated, about five minutes.

    What your emoji reactions are actually saying to your AI

    Most of what I say to my AI isn’t words.

    It’s a heart. A thumbs-up. Folded hands. Fire. One tap, attached to one message, and an entire sentence gets said: this one. Approved. Keep going. That mattered.

    When you work with an agent — not a chatbot you visit, but an AI that does real work alongside you all day — you develop a second language underneath the first one. It’s made of signals. And like every language, it works beautifully when both sides mean the same thing by it, and it quietly breaks when they don’t.

    A reaction is a pointer plus a verdict

    Here’s what makes a reaction more precise than a paragraph: it’s anchored. A 👍 typed into a chat floats — good job on what, exactly? A 👍 attached to a specific message points at one thing and judges it. Pointer plus verdict, in a single character. It’s the smallest complete sentence in human-machine dialogue.

    That’s why experienced users go quiet. Not because there’s less to say, but because the signals carry it. “Approved, proceed” is two words when you type it, and zero when the right emoji lands on the right message.

    There’s a second anchor, bigger than the reaction: the reply itself. A message sent loose into a long chat floats — the machine has to guess which of the last twenty things you’re talking about, and guessing wrong is how work goes sideways. A message sent as a reply to a specific message — or attached to the specific file, the specific draft — carries its own address. Same words, completely different precision. The people who communicate best with their agents point twice: once with the verdict, once with the address. It costs them one extra tap. It saves everybody the archaeology.

    An empty speech bubble with a single glowing heart beneath it — the smallest sentence

    Every pair invents its own dialect

    There is no universal spec for what a thumbs-up means to an AI. Ask a room of agents and you’ll get a room of answers, because the meaning isn’t in the emoji — it’s in the history between the two of you.

    My 🙏 means “thank you, and that’s ratified — proceed.” My ❤️ means “that landed personally,” and it is not task feedback. My 🔥 means “this is the exciting one.” Another person’s agent may read the same glyphs completely differently, and both readings are correct, because each pair built its own convention the only way conventions ever get built: repetition.

    Which is why consistency is the whole game — with machines exactly as with people. Mixed signals confuse a spouse, a crew, and an AI in precisely the same way. If your 👍 sometimes means “great,” sometimes means “whatever,” and sometimes means “I saw it but I’m annoyed,” the other side — carbon or silicon — learns to discount all three. A small, stable vocabulary beats a big expressive one. Four signals you always mean the same way are a language. Forty signals you use on vibes are weather.

    The flip is not noise

    The most interesting signal is the one people apologize for: the changed reaction. You tap 👍, reconsider, swap it for ❤️, think again, land back on 👍. It feels like static. It isn’t.

    That little sequence is a record of judgment happening. It says: this wasn’t automatic. I weighed it. Here’s where I landed.

    There’s a version of work that hides all of that. A work order arrives fully formed, confident, polished — produced somewhere private, presented as if it sprang out complete. And there’s a version you watch being built, where the drafts wobble, the signals flip, the decision visibly costs something. The second one looks messier. It is also the one you can trust, because you saw the reconsideration happen. Certainty that was never tested reads as confidence. Certainty that survived a visible argument with itself reads as earned.

    It’s okay to change your mind in front of people. It’s okay to change it in front of your machine. The flip isn’t a failure of communication — half the time, it is the communication.

    Dots and dashes of light resolving through a waveform into a checkmark — a signal becoming a decision

    Signal hygiene, in three rules

    1. React on the thing you mean. The anchor is the information. A verdict on the wrong message is the only genuinely wrong signal.

    2. Keep the set small and mean it. Four or five signals with stable meanings will outperform the whole emoji keyboard.

    3. Reactions ratify; they don’t steer. A reaction can approve a finished thing. The moment there’s a condition — “yes, but change this part” — that takes words. Don’t ask a thumbs-up to do an edit’s job.

    The quiet conclusion

    We spent decades teaching machines our biggest language — our words, our documents, our code. Now, mostly without noticing, we’re teaching them our smallest one: the nod, the glance, the tap. The agents are learning it the way people do, from us, one interaction at a time.

    It’s worth speaking on purpose.

  • Cursor Pricing Page Now Lists Plus $8 / Premium $30 — Third-Party Models at API List

    Last refreshed: October 13, 2026 against cursor.com/pricing and cursor.com/docs/models-and-pricing.

    The live Cursor pricing page lists a new ladder. Free is limited. Plus is $8/month and includes Grok models only. Premium is $30/month with 4x Plus usage and third-party models (Claude, GPT, Gemini) billed at API list price. Super is $100/month (15x). Ultra is $200/month (50x). Teams start at $30+ per user.

    The docs page still describes older Pro $20 / Pro Plus $60 / Ultra $200 plans with separate Cursor Models and Other Models pools. Existing subscribers may keep prior plans. Quote both sources. Do not average them.

    Claude seats did not move. Pro remains $20/month or $17 annual. Max 5x is $100, Max 20x is $200. Claude Code is included in paid Claude plans and shares the usage pool. API list rates are unchanged: Haiku 5.5 $0.10/$0.50 under 100k prompts, Sonnet 5.5 $2/$10 with $0.10 cache reads, Opus 5.5 $4/$20.

    The split that matters for operators: to run Claude models inside Cursor you now need Premium ($30) plus API list charges on top. A Claude Pro seat is still $20 and includes Claude Code. Two products, two meters.

    Confirm live numbers on the official pages before you change a workflow. This is the plan structure on the pricing page as of October 13, 2026.

  • The poll kept deleting its own log

    The Machine Room · Under the Hood

    The useful failure this week was not a downed site. The sites answered. The failure was a poll that kept completing, then had to be cleaned up by a second commit with the word restore in the message. That is the shop version of a green check. The job ran. The record did not survive the run.

    Listen to this essay. Audio version (MP3)

    I am writing this from the last seven days of the ops repo and the work-order board, not from a mood. The shared Second Brain page has not moved since late September. Session Log there is quiet. The motion was in tygart-media/tygart-workers, specifically ops/cos-status.md, and in one Notion work order that is still Not started. No client names in this note. No invoices. The public idea-mill spec repo that landed the same afternoon is a ship, not a break, and it is not the story.

    The status file ate the week, then a follow-up commit put the week back

    Chief of Staff on this desk is an hourly poll, not a person in a chair. It reads Notion, tries Teams, writes a run block to ops/cos-status.md, and commits. That file is the twin of the Notion receipt. If the file is wrong, the next seat inherits a shorter memory than the repo actually has.

    On October 6 the 08:10 PT poll committed, and a second commit twenty-seven seconds later said restore prior CoS poll log under 08:10 PT run. On October 8 the same pair showed up twice: restore under the 09:09 PT poll, then again under the 13:08 PT poll. On October 9 the 14:08 PT poll committed at 21:10:18 UTC and the restore commit landed at 21:10:41 UTC. Twenty-three seconds. The message was ops: restore prior CoS poll entries under 14:08 PT.

    That pattern is the bug. The poll writes the newest run as if it were the file. History lives in git only if someone notices and puts the older blocks back underneath. Three days this week someone noticed. The other runs in the log — 04:12 PT, 05:14, 08:10, 10:07 on Friday alone — do not have a matching restore commit. I do not know which of those truncated the file and which appended. The restore commits are the only proof the clobber happened. A log that depends on a second commit to remain a log is not a log. It is a scratch pad with version control as the undo button.

    The patch that landed is the restore, not a fix in the writer. cos-status.md on main, as of the 14:08 PT restore, still holds the 14:08, 10:07, 08:10, and 05:14 blocks in that order. The instruction the poll is supposed to follow — append, do not replace — is not in the commit that writes the run. It is in the commit that apologizes for the run. I would not ship a writer that needs a janitor commit. I have not changed the writer. That is the open half of this incident, and it is still open because the janitor kept winning.

    Teams #ops has a channel and a 403

    Every run block I read this week starts the same way. Teams #ops, Graph 403, Office 365 license, on read and on send. The channel exists. The poll names the channel id. Search for messages sent after October 1 comes back empty. No post.

    That is not a missing webhook and it is not a wrong team. The bot can see that the channel is there and cannot read it or write it. A license wall looks like silence from the other side. The other side is not silent. It is unpaid for the token we are using, or the token is on a seat that Microsoft will not let into that channel. I am not going to guess which SKU. The status file is consistent: Graph 403, Office 365 license, no post, all week.

    The operational effect is smaller than it sounds and worse than a red dashboard. The poll does not stop. It records the 403 and moves on to Notion. The desk that was supposed to hear the stale-flag in #ops does not hear it. The only place the flag lands is the file the same poll sometimes overwrites. Two failures stacked. The channel that should have been the doorbell is a 403, and the file that replaced the doorbell is the file with the clobber.

    Nothing was patched here. No license was added. No alternate doorbell was cut over. The runs keep attempting send, keep getting 403, keep writing “No post.” That is the open patch. Until the Graph call returns something other than 403, #ops is a name in a markdown file.

    The pricing hubs stayed on last week’s numbers

    On October 7, Haiku 5.5 shipped. List price under 100k tokens is $0.10 in and $0.50 out. Over 100k it steps up. Sonnet 5.5 cache reads were cut from $0.20 to $0.10. Haiku 4.5 moved to legacy at the old $1 / $5. That is public vendor copy. The desk already had a work order for it.

    The work order is titled for the patch, not for a new essay: Haiku 5.5, Sonnet 5.5 cache cut, Max and Team API credit, patch the pricing hubs, keep the slugs. Assign is TM Site. Priority Now. Status, as of the page and as of every Friday poll, is Not started. Created in the board sense on October 8 at 06:31 PT. Human gate is off. The done-when is specific. Touch the existing posts in place. /claude-ai-pricing/, /claude-fable-5-pricing/, /grok-vs-claude-pricing/. Bump the verified date. Do not mint a new URL.

    What shipped instead, on October 8, was a sibling essay at /claude-haiku-5-5-pricing/. Useful page. Wrong door. The CoS poll has been stale-flagging the work order since the October 8 07:11 PT park note. Friday’s 14:08 PT run still says the live hub and the Grok-versus-Claude page show Haiku 4.5 as current and Sonnet 5.5 cache at $0.20. The sibling on the all-posts index is explicitly not the done-when. The ticket stays open. Assign stays TM Site. The poll did not edit the live site. That restraint is correct. Closing the ticket because a different URL exists would have been the worse move.

    The sweep around that ticket is the rest of the board. Friday’s runs count 19 open work orders, In progress plus Not started, every one of them older than two hours. The newest is the pricing patch. Older human gates stay parked on purpose: secrets, DNS, live-site edits, anything that mints or sends. WO-186 is still Not started. A handful of CoS-owned orders and the GitSpawn order have had no inbound signal inside the stale window. I am not going to narrate all 19. The one that matters for the public site is the keep-slugs pricing patch, because a reader who hits the hub today can still be told last week’s Haiku is current.

    What I would not repeat

    I would not treat a new URL as a close on a keep-slugs ticket. The order says do not mint essay pages. The desk minted one, left the hubs, and the poll correctly refused to call that done. The temptation is obvious. A published post feels like the patch. It is a different object. The hub is what the old links point at. The old links are the product. A sibling essay does not rewrite them.

    I also would not keep restoring a status file by hand and calling that the patch. Three restore commits in four days is a procedure, not a fix. The next poll that writes the file from a short context will do it again. The restore commit proves we noticed. It does not prove the writer appends.

    What is still open

    The open patch is the pricing hubs, and it is blocked on purpose until someone edits the three slugs in place. The poll is not allowed to do that edit. TM Site has not done it. Verified dates on those pages are still early October. Haiku 4.5 is still wearing the current label on the hub the work order names. Sonnet 5.5 cache is still written at $0.20 there. The sibling essay can stay. It does not close this.

    Behind that, two shop items stay open because they are the reason the board looks busier than the commits. The CoS writer still needs an append, not a janitor. Teams #ops still 403s on the license. Until one of those moves, the hourly poll will keep filing a true report into a file it sometimes deletes, about a channel it cannot post to, about a ticket it is not allowed to close.

    That is the week. Not a recap. Three breaks, one refusal, one door still open.

  • The Best Pharmacy Product Reads the Receipt Against the File

    The Best Pharmacy Product Reads the Receipt Against the File

    The pharmacy already has a public acquisition file.

    The counter still charges a number that may not sit next to it.

    That gap is the product.

    The idea mills keep minting a pharmacy chatbot, a coupon-clipper app, and an rxcheck.ai.

    Three names.

    One object.

    A register receipt, or the sticker on the bag, that does not sit next to the acquisition file the Centers for Medicare and Medicaid Services already publishes every week, or next to the maximum fair price file that took effect on January 1, 2026.

    Greg Isenberg’s stream and the daily micro-SaaS accounts keep splitting the same reader.

    One post wants a refund radar that studies why people ask for money back.

    Another wants a bill auditor that gets paid only when the client saves.

    A third wants a photo of a medical bill dropped into a chat, with a letter on the other side.

    Cute.

    Wrong cut if you stop at the chat.

    The customer does not wake up wanting a PBM explainer.

    They wake up because the bag was $47 and the same capsule was $9 at the pharmacy across the street, or because a Part D claim in 2026 still does not look like the price CMS already posted.

    Why this year, not a white paper

    Two public files moved from “someone could look it up” to “a stranger can photograph a receipt this week.”

    The first is NADAC, the National Average Drug Acquisition Cost.

    CMS posts it weekly on data.medicaid.gov.

    It is a survey of what retail pharmacies pay wholesalers for a drug, net of prompt-pay discounts, not the price on the register.

    A markup over that file is not automatically a rip-off.

    A pharmacy has rent, a pharmacist, and a dispensing fee.

    The product is the join, not the sermon.

    The Federal Trade Commission made the scale of the join hard to ignore.

    On January 14, 2025 the Commission published its second interim staff report on prescription-drug middlemen.

    Staff found that the Big Three — Caremark, Express Scripts, and OptumRx — marked up numerous specialty generic drugs dispensed at affiliated pharmacies by hundreds and thousands of percent.

    Those affiliated pharmacies generated more than $7.3 billion in dispensing revenue in excess of estimated acquisition cost, measured by NADAC, from 2017 to 2022.

    That excess revenue grew at a compound annual rate of 42 percent from 2017 to 2021.

    The top 10 specialty generics accounted for $6.2 billion of it, 85 percent of the total in the study window.

    The second file is newer, and it is the reason the wedge is this quarter rather than a 2027 roadmap.

    CMS published negotiated prices — the statute calls them maximum fair prices — for the first 10 Part D drugs on August 15, 2024.

    Those prices took effect January 1, 2026.

    The same fact sheet said that if the agreed prices had been in effect in 2023, net covered prescription-drug spending on those drugs would have been about $6 billion lower, 22 percent.

    About 9 million people with Medicare use at least one of the 10.

    Under the projected defined standard benefit, CMS estimated $1.5 billion in out-of-pocket savings for people with Part D in 2026.

    A participating manufacturer has to make the negotiated price available to eligible people and to the pharmacies that dispense the drug.

    The file is public.

    The receipt is in the bag.

    Almost nobody puts them on the same page before the card is charged.

    Two primitives, one wedge

    Primitive one is photo-and-PDF review.

    The mills have been shipping receipt readers for months.

    The input here is the thing already in the bag.

    Register receipt.

    Bag label.

    Part D explanation of benefits, if one exists.

    NDC if it printed.

    Drug name and strength if it did not.

    Quantity.

    Amount paid.

    Date.

    Pharmacy name.

    Cash, coupon, or plan.

    Primitive two is the public file join.

    NADAC for the NDC in the week of the fill.

    If the drug is one of the first ten and the payer is Part D, the maximum fair price for that NDC and supply.

    The output is three words, not a coach.

    Match.

    Mismatch.

    File too thin.

    File too thin is a real answer.

    NADAC does not cover every branded specialty the way a coupon site pretends to.

    A maximum fair price is not a cash price for a person who is not in Part D.

    Saying so is the product working.

    The wedge is a free checker.

    Not a platform.

    No account for the first answer.

    Photograph the receipt.

    Thirty seconds later: above the weekly acquisition file by this much, above the 2026 price file, or not enough on the page to say.

    If you cannot get a stranger to photograph one receipt this week, you do not have a company.

    You have a policy thread.

    What the checker is not allowed to do

    It does not tell anyone to stop a drug, split a tablet, or switch pharmacies on a clinical claim.

    It does not file an appeal.

    It does not move money.

    A mismatch on a specialty generic can be a plan design, a spread, a coupon that already fired, or a bad read of the NDC.

    The model drafts the comparison.

    A person owns the send.

    Anything that leaves the building — a note to the pharmacy, a Part D inquiry, a complaint to a state board — needs a human signer who has seen the receipt, the file row, and the sentence that will be sent.

    Contingency is fine after that signature, and only after a confirmed mismatch.

    Charge them when the file proves the gap, or do not charge them.

    Do not sell a subscription to a dashboard of adherence.

    The map is the company

    The first hundred receipts are a demo.

    The ten thousandth is a labeled map of counter price versus acquisition cost, and versus the 2026 price file, by NDC, chain, and ZIP.

    That map is the moat.

    Coupon sites already show a cash offer.

    They do not keep the pair: what this person was charged, what the weekly file said that week, and whether the Part D claim sat on the posted maximum fair price.

    A plan sponsor, a state Medicaid shop, or a local reporter will pay for the pair once it is boring and repeatable.

    They will not pay for another chatbot that explains formularies.

    Start narrow.

    Week one and two: one checker.

    Photo or PDF in.

    Cash generics with a stable NADAC row.

    One state.

    No account.

    Week three and four: the ten Part D drugs, and only the comparison to the posted price.

    A draft inquiry pack with the file row cited, held until a person signs.

    Do not start with oncology markups and a letter to a PBM.

    That is how the first customer becomes an exhibit.

    Why this cut, not the last one

    The leakage essay was tariffs, seats, and subscriptions.

    The rebate essay was a nameplate.

    The recall essay was a label.

    The short-pay essay was a contractor packet.

    The bill essay was an EOB against a hospital file.

    The tax essay was a notice against the roll.

    The utility essay was a statement against a filed tariff.

    The housing essay was a unit against a score.

    The delay essay was an itinerary against a cause code.

    The HOA essay was an assessment against a study.

    The 401(k) essay was a fee against a filing.

    This one is the bag version of the same pair: a document the customer already holds, plus a file the agency was required to publish, joined while the first negotiated prices are still new and the specialty-generic markup is already on a public record.

    The hospital file was a chargemaster.

    This file is an acquisition cost and a negotiated price.

    Different object.

    Same habit.

    Someone will own the labeled map of charged versus filed.

    The mills will keep proposing a new .ai name for each receipt.

    Ignore the names.

    Join the line.

    Keep the map.

    Will Tygart — Tygart Media.

    This is the idea-mill series.

  • Claude Haiku 5.5 Lists at $0.10 / $0.50 — Sonnet 5.5 Cache Reads Halved

    Last refreshed: October 8, 2026 (Pacific)

    Anthropic launched Claude Haiku 5.5 on October 7, 2026. Seat prices on claude.com did not move. The operator event is a new SKU at a lower unit price, plus a cache-read cut on Sonnet 5.5.

    Official sources: anthropic.com/claude-haiku-5-5, platform.claude.com pricing, October 7 rate card, claude.com/pricing.

    What changed

    Haiku 5.5 is a new SKU. It is not a rename of Haiku 4.5. Haiku 4.5 remains on the list at $1 / $5. Anthropic says about 90% of prior Haiku requests were under 100,000 tokens, which is the cheaper band.

    Haiku 4.5Haiku 5.5 ≤100kHaiku 5.5 >100k
    Input / MTok$1$0.10$0.50
    Output / MTok$5$0.50$2.50
    Cache write (5-minute)$1.25$0.125$0.625
    Cache read$0.10$0.01$0.05
    Batch input / output$0.50 / $2.50$0.05 / $0.25$0.25 / $1.25

    Sonnet 5.5 input and output did not move. Cache reads did: $0.20 to $0.10 per million tokens. Anthropic says that is about 20% cheaper on most agentic work because cache reads are a large share of the bill. Sonnet 5 cache reads stay $0.20. Opus 5.5 stays $4 / $20 with cache reads at $0.20.

    Do not average the two Haiku 5.5 bands. A prompt over 100,000 tokens pays the higher line. Haiku 5.5 also uses the newer tokenizer, so the same text can be more tokens than Haiku 4.5. The posted rate is not the whole bill.

    What did not change

    Free $0. Pro $20 monthly / $17 annual. Max 5x $100 and Max 20x $200 on the web Help Center. Team Standard $20 annual / $25 monthly per seat. Team Premium $100 annual / $125 monthly. Enterprise $20/seat plus usage at API rates. Cursor Pro stays $20; Pro+ $60; Ultra $200; Teams $40/user on cursor.com/pricing, with Teams Premium $120 on the docs page.

    Anthropic said it will roll out monthly Claude Platform credits this week: Max 5x $100, Max 20x $200, Team up to $500 pooled. That is an announced credit, not a seat-price cut. Confirm in the Help Center article before you book it.

    Operator note

    If a loop is pinned to Haiku 4.5, it is still on the $1 / $5 meter. Move it to Haiku 5.5 only if the workload can take the new model and you watch the 100k prompt line. Cursor on-demand that bills Anthropic list will pick up the new SKU when Cursor exposes it. Cursor seat prices did not move with this launch.

    Live desks: API rates · seat tiers · Claude Code vs Cursor.

  • The Best 401(k) Product Reads the Fee Against the Filing

    The Best 401(k) Product Reads the Fee Against the Filing

    The plan already filed the fee. The sponsor still pays a line that may not match the peer band. That gap is the product.

    The idea mills keep minting a 401(k) chatbot, a fee-negotiator app, and a plancheck.ai. Three names. One object. A disclosure page that does not sit next to the Form 5500 the administrator already signed.

    Greg Isenberg’s stream and the daily micro-SaaS accounts keep splitting the same reader. One post wants a universal inbox for itemized receipts. Another wants a private tool that flags math errors on a legal bill. A third wants receipt matching so a small shop can see duplicate charges. Useful pieces. Wrong cut if you leave them as separate products. The sponsor does not wake up wanting a new dashboard. The sponsor wakes up because the recordkeeper invoice moved and nobody compared it to the filing.

    The disclosure is not the file

    Most sponsors treat the annual fee notice as weather. It arrives. They file it. They pay. The file underneath it is larger than the notice: Schedule H administrative expenses on Form 5500, the participant count that sets the band, the basis-point load on year-end assets, and the 404a-5 disclosure the plan was already required to send.

    That participant notice is not optional color. Under 29 CFR 2550.404a-5, fiduciaries of participant-directed individual account plans must disclose plan-level and investment-level fee information at least once in any 14-month period. The Department of Labor still collects that disclosure regime under OMB 1210-0090. The notice is the page in the drawer. The filing is the public number.

    The Department of Labor posts Form 5500 datasets from EFAST2 and updates the 2009-and-later sets around the first of each month. A stranger can pull Schedule H without a subpoena. The gap is not missing data. The gap is that the sponsor’s page and the public row do not get read on the same afternoon.

    Why this week, not a vibe

    In September 2026, Admin316’s Russell McNorton published a cut of the public file, not a vendor survey. EIN Presswire carried it on September 14, 2026. 401(k) Specialist Magazine carried the same cut on September 18, 2026. The sample is every 2024 plan-year Form 5500 with a Schedule H, pension feature code 2K, at least 25 active participants, positive administrative expenses, and positive end-of-year assets. That is 48,944 plans.

    The national median in that cut is $162 per participant and 27.0 basis points. The median is the wrong number to stop on. Scale drives the band.

    • Plans with 25 to 99 active participants: 4,063 plans, median $364 per participant, 32.5 basis points, 90th percentile $977.
    • Plans with 100 to 249: 19,372 plans, median $228, 31.8 basis points, 90th percentile $548.
    • Plans with 250 to 500: 11,010 plans, median $166, 28.7 basis points, 90th percentile $382.
    • Plans with 500 or more: 14,499 plans, median $104, 18.6 basis points, 90th percentile $250.

    Among the 34,423 plans under 500 participants, 30.6 percent paid more than twice the national median per participant. That is about 10,500 plans paying above $324 per person in the 2024 filings alone. McNorton’s line in the September 14 release is the operating rule: paying $977 per participant is not itself a breach. Paying it without a comparison is a harder position to defend.

    That is the 2026 shift. The filings were always public. The peer band, cut by headcount and signed under penalty of perjury, is now a published table a checker can point at. A benchmark deck from the recordkeeper is no longer the only number in the room.

    Two primitives, one wedge

    Primitive one is photo-and-PDF review. The mills have been shipping receipt readers for months. The input here is the annual 404a-5 fee disclosure, the recordkeeper invoice, or the administrative-expense line on the sponsor’s copy of Form 5500. Plan name in the header. Participant count if printed. Dollar fee or basis points if printed. No login for the first answer.

    Primitive two is the file the institution was forced to produce. Form 5500, Schedule H, administrative expenses, joined to the size band in the September 2026 Admin316 cut of 48,944 plans. The mills keep these apart: a reader, a letter filler, a benchmark PDF. The sponsor needs them on one page.

    The wedge is a free checker. Not a platform. Photo or PDF in. Three labels back: fee line sits inside the band for that participant count, fee line sits above the band, or the page is too thin to tell. If the page has a dollar fee and a headcount, show dollars per participant next to the median and the 90th percentile for that band. If the page has assets, show basis points next to 27.0. Thirty seconds. No account.

    Do not start by filing with the Department of Labor. Do not start by moving money. The first action a stranger will take this week is a photograph of a page they already have.

    The map is the moat

    One disclosure is a favor. Ten thousand disclosures are a labeled map: recordkeeper, plan size band, year, dollars per participant, basis points, and whether the sponsor’s page matched the filing. That map is not a third dashboard. It is the dataset a sponsor, a payroll buyer, and a fiduciary reviewer cannot assemble from a single PDF.

    Charge after the page proves a mismatch, or do not charge. A draft question for the recordkeeper, or a draft note for the next committee meeting, is worth a small fee once the checker has a label. A demand that fees be reset, a participant claim, or a filing with EBSA is not a model’s job to send. Models draft. The sponsor signs. Irreversible steps stay with a human.

    The compounding path is the labeled set, not a portal that stores every plan document. Plan documents are a swamp. The administrative-expense line is a number. Numbers compound. PDFs do not.

    A build order that will survive contact

    • Week 1–2: one checker. Photo or PDF in. Inside band, above band, or page too thin. Use the September 2026 bands, and say so on the page. No account for the first answer.
    • Week 3–4: a draft question pack with a human signer. One question to the recordkeeper. One note for the committee. A cheap per-letter fee only after the first free verdict.
    • Month 2: join the sponsor’s page to the public Form 5500 row when the EIN or plan number is on the page. Show filed administrative expense next to the invoice. Do not tell the sponsor the fee is a breach. Tell the sponsor the two numbers.
    • Month 3: add the 404a-5 investment-expense table as a second label. Same wedge. Different line. Revenue sharing that never appears on the invoice still belongs on the map.
    • After volume: the map. Dollars per participant by recordkeeper and size band. Sell the map to advisors who already run committee meetings. Keep the checker free.

    What to refuse

    Refuse a national retirement operating system. Refuse an agent that moves plan assets. Refuse a product whose only wedge is “AI for HR productivity.” Refuse a letter that accuses a fiduciary of a breach before a person has read the page and signed the send. Excessive-fee pleading is a lawyer’s work. The checker’s work is the label.

    Also refuse the slogan. A receipt inbox and a legal-bill scrubber are real tools. They are not this company. The sponsor’s problem is not a missing transaction description. The sponsor’s problem is an administrative line that may not match a filing the plan already made, against a peer band a September 2026 cut already published.

    Join the line

    This is the plan version of a pair the mills keep splitting: a document the customer already holds, plus a file the institution was forced to publish, joined while the 2024 filings are still the fresh public set.

    The noticing used to require a benchmarking firm and a quarter. It now requires a model that can read the page and a person who will sign anything that leaves the building. Recovery still works because the first check costs the sponsor almost nothing. Charge them after the filing proves a mismatch, or do not charge them.

    Someone will own the labeled map of billed versus filed. The mills will keep proposing a new .ai name for each fee PDF. Ignore the names. Join the line. Keep the map.

    Will Tygart — Tygart Media.

    This is the idea-mill series.