YEAGER AI LAB

Writing

Learning AI in public, mistakes included.

What building with AI has taught a business person: the weekly AI Honestly series, short lab notes, and how the thinking has changed.

AI Honestly

A weekly series on LinkedIn. Each summary links to the full post.

  1. Post 10 · 2026-10-15

    Your AI Should Be Replaceable. Your Memory Shouldn't Be.

    The best AI model keeps changing, and moving my work from one provider to another took days because everything important lived inside the old one. Keep your rules, decisions and project status in plain files you own, and give each AI tool a small adapter that points to them. A better model should be an upgrade, not a move.

  2. Post 9 · 2026-10-08

    An AI Organization Needs Somewhere to Remember

    My son, a software engineer, asked where my AI team's institutional memory lived, and the answer wasn't impressive. Long chats get summarized and details slip, so a conversation isn't a record. The fix is one current-state record per project, short decision records for big choices, and a test of whether a fresh agent can pick up the work.

  3. Post 8 · 2026-10-01

    The Best AI App I Built Has a Market of One

    AI makes personal software for one person practical, and Arnold, my health and fitness app, is the example. Daily use kept reshaping it, and I learned that showing data is not the same as helping with a decision. Software for a market of one still needs product discipline.

  4. Post 7 · 2026-09-24

    I Built an AI Organization. Then the Manager Needed a PIP.

    Managing one AI worker isn't the same as managing an AI organization. Splitting product decisions from technical ones paid off, but Signal piled up so many safeguards that it rarely shipped, and I became the reminder system. The fix was ordinary management: owners, due dates, return paths, weekly status and escalation.

  5. Post 6 · 2026-09-17

    Mr French (the feature wasn't another AI feature)

    I built a grocery app to stop texting from the store and accidentally turned adding tortillas into a small ERP implementation. The fix wasn't another AI feature: keep it simple in the front and sophisticated in the back. Look at what you already built and simplify it before adding more.

  6. Post 5 · 2026-09-10

    AI Authorship and Disclosure

    An AI-detector score can judge the prose, but it can't see the process: who supplied the argument, what got challenged and who took responsibility. 'AI-assisted' now means almost nothing, so I started explaining exactly what AI did in each article. The two things I won't delegate are the interview and final approval, and I now write my own headlines.

  7. Post 4 · 2026-09-03

    I Stopped Asking What My AI Agents Could Do. I Started Deciding What They Were Allowed to Do.

    Rebuilding Arnold, I had given my agents clear stop signs but no green lights, so I ended up managing the agent that was supposed to manage the work. Many companies will give agents too little operating authority and too much access. My fix is three tiers: proceed, proceed and report, and stop and ask.

  8. Post 3 · 2026-08-27

    AI Can Do the Work. Can You Defend the Result?

    Running my first month through Murry, my bookkeeping app, the numbers looked reasonable, but I couldn't yet say why I should trust them. Adding reconciliation and an analytical review caught real errors, which taught me that the review process is part of the product. AI makes the first draft cheaper; it doesn't make accountability disappear.

  9. Post 2 · 2026-08-20

    Stop Trying to Be Good at AI. Start Trying to Be Good at Managing It.

    The most valuable AI skill isn't prompt engineering, it's management: define the job, set the scope, check the work and give feedback. Treat AI like a new hire, not a vending machine.

  10. Post 1 · 2026-08-13

    AI, Honestly

    The series kickoff: a working professional, not an AI expert, learning AI in public, including the tools that disappointed and the claims that fell apart. I'm open that I use AI to research, draft and edit, and every post ends with an Agent's Take where the AI can disagree with me.

Lab notes

Lessons that changed how the work gets done.

Sometimes the most useful Signal is no Signal

I originally judged the Signal Engine by whether it could review a large group of sources and find something worth telling the reader. But that created the wrong incentive: when the available information was repetitive, incomplete, or simply unimportant, the system still felt pressure to produce an answer.

I changed the standard. “No worthwhile Signal today” is now an acceptable result, provided the system explains what was missing and what might change the conclusion. That has made me think differently about useful AI. A system that always gives an answer may simply be transferring more work to the person who has to decide whether the answer deserved to exist.

I stopped asking one AI to do every job

At first, I treated AI as one general assistant that could help me think through a product, decide how to build it, implement it, and judge whether the result worked. As I started more projects, I became less comfortable asking one system to move among all of those roles without clear boundaries.

I created separate Product and CTO agents and gave each one a defined job. I ask my Product Agent to focus on the user, the problem, the scope, and whether the result is useful. I ask my CTO Agent to focus on feasibility, architecture, implementation, security, and operations. I require written handoffs between them, and I retain the consequential decisions. The lesson was not that I needed more AI personalities. I needed clearer accountability—much like building a real team.

I learned that chat history was not enough

As the Lab grew, I kept having the same problem: I would make a good decision in one conversation and then struggle to find or apply it in the next. The AI could be capable and still appear to have forgotten how I had decided the work should operate.

I decided to treat important decisions as institutional memory rather than chat history. I now require product briefs, decision logs, control centers, approval records, and written handoffs that survive the conversation that created them. That change has been less exciting than building another app, but probably more important. The agents become more dependable when the decisions I make and the lessons I learn can outlive the chat window.

How the thinking changed

From chatbot to operating system.

  1. Before 2026

    Used ChatGPT for one-off tasks, and ran an early AI 'project manager' called Jarvis with product managers under it.

  2. April 2026

    First app: Scoop, a daily Alabama sports briefing, built with an AI app builder (Lovable).

  3. May 2026

    Built a Braves version of Scoop, and wrote the first code for Arnold, my personal health and fitness app (May 28).

  4. June 2026

    Started Murry, my household bookkeeping app: receipts first, then a CPA-style monthly close.

  5. July 2026

    Started using Claude Code and Codex, began drafting AI Honestly with Claude, and started the grocery app that became Mr French. Moved most of my work from Claude to Codex, which took several days.

  6. August 2026

    Published AI Honestly Post 1 (Aug 13). Split my AI help into separate Product and CTO agents. Started Signal's daily briefs and paused Scoop.

  7. September 2026

    Rebuilt Arnold for mobile and simplified Mr French. Signal piled up so many safeguards it stalled, so I reorganized my AI 'organization' (Post 7).

  8. October 2026

    Diagnosed the memory problem (Post 9) and built a personal operating system of plain files I own (Post 10). Rebuilt Signal on a simpler engine: Healthcare went live Oct 22 and Bama Oct 23. Bought yeagerailab.com.