Bob Michaels/ai
Writing by Bob MichaelsRSS

Writing.

Arguments I can defend with data, about where the web is going and what it costs to arrive late.

There is no CMS behind this page. Every essay is a file in the repository, reviewed and shipped from git, which is the same claim the writing makes.

Newest first.

19 essays

July 30, 2026

Built with AI

5 min read

The CMS Era Is Sunsetting

WordPress peaked at 43.6% of all websites in 2025 and posted its first decline since W3Techs began tracking in 2011. Bob Michaels, building the web since 1994, argues the CMS era is sunsetting: websites are becoming software again, built with AI, readable by AI, and transacting with AI.

Read the essay →

July 28, 2026

Built with AI

10 min read

Human in Control: Draw the Approval Map Before the Workflow

Human in the loop usually means a person is present. Human in control means a person can inspect the evidence, stop the action, and own the decision. Here is the approval map to draw before you automate: action classes, named owners, evidence packets, four decision states, and the thresholds that keep it from becoming bureaucracy.

Read the essay →

July 23, 2026

Built with AI

9 min read

How to Evaluate an Agent Before It Touches Production

An AI agent is a stateful business process with tools and permissions, and it should be evaluated like one. Here is the four-class test matrix (normal, edge, adversarial, forbidden), the trace record, the two scores that must stay separate, and the release gates that decide production.

Read the essay →

July 21, 2026

Built with AI

9 min read

One Model Is Not an AI Strategy

A multi-model strategy is a stable task contract with portable evidence, and the vendors' own documentation explains why you need one: models retire on the provider's clock, notice windows run from two weeks to six months, and compatible APIs cover the request shape, never the behavior. Here is the dependency map and the exit test.

Read the essay →

July 14, 2026

Built with AI

9 min read

Grounded Means Cited or Declined

Retrieval is a component. Grounding is a contract: for consequential claims, the system cites approved evidence, states uncertainty, or declines, and logs which one happened. Here is the contract, the standard behind it, and the test that tells you whether a system honors it.

Read the essay →

July 9, 2026

Readable by AI

8 min read

How You Win the AI Head-to-Head

Losing the AI comparison is a finding, and findings have a method. Here is the loop I run to move the recommendation: query on a locked list, decode why the winner wins, engineer that evidence on your domain with one consolidated message, and verify by retesting. With the measured results, honestly framed.

Read the essay →

July 2, 2026

Readable by AI

8 min read

Stop Topic Chasing. Start Winning the Head-to-Head.

Topic chasing is the keyword-and-coverage playbook, and it measures inputs. The head-to-head measures who AI actually recommends. Here is the difference, the evidence for both halves, and how to keep your content program while changing its finish line.

Read the essay →

June 25, 2026

Built with AI

7 min read

Accessibility Is an AI Architecture Requirement

AI interfaces stream text, update live, and fail in new ways, and every one of those behaviors has an accessibility contract. Here is how WCAG maps onto chat and agent interfaces, and why it belongs in architecture, not remediation.

Read the essay →

May 28, 2026

Built with AI

9 min read

The Seven Actions an AI Agent Should Never Take Without a Named Owner

Agent permissions are being granted by integration scope instead of business consequence. Seven action classes need a named human owner no matter how automated execution gets: external communication, publication, financial commitment, access changes, destructive data actions, production deployment, and legal representation. Here is the list, with the bounded exceptions that keep it fast.

Read the essay →

How this page works

No database, no admin panel, no plugins.

Each essay is a typed entry in a registry and a component in the repository. The index, the sitemap, and the feed all read that one source, so publishing is a commit and nothing can drift out of sync. I build client sites the same way.