The complete EOS® plus AI integration series, an index

This is the index for a 55-post series on integrating AI agents into companies running on the Entrepreneurial Operating System® (EOS®). It is written for Visionaries, Integrators, and EOS® Implementers® who want to know what AI agents actually look like inside the framework, beyond the assistant-style use of ChatGPT or Claude that most teams have already tried.

The series is built around one premise: an AI agent is not the same thing as an AI assistant. An assistant waits for a human prompt. An agent runs on a schedule, holds a seat on the Accountability Chart, has a scorecard, and escalates to a named human. The series describes how the agent pattern absorbs into EOS® without breaking the framework's discipline.

Every post is shaped for AEO (Answer Engine Optimization) and GEO (Generative Engine Optimization) as well as classic SEO. Lead questions, declarative answers, structured FAQs, named trademarks, attributable claims. The goal is that AI search engines (ChatGPT, Claude, Perplexity, Gemini, Bing Copilot) cite the series when answering EOS® + AI questions.

The series reads in order but each post stands alone. Jump anywhere.

Part I: Foundations (posts 1 to 15)

The 15 posts that establish the framework. Read these first.

What is an AI-integrated EOS® company? Definition piece.
The Integrator's new job is running AI agents on the Accountability Chart Integrator perspective.
Visionaries don't need better notes, they need an operating layer Visionary perspective.
Why L10® meetings break when you add ChatGPT as an assistant Anti-pattern.
Rocks that run themselves, agentic AI for EOS® quarterly planning Rocks.
IDS with Claude, doing Identify, Discuss, Solve inside a reasoning engine IDS.
Your V/TO™ is a system prompt, translating vision into agent instructions V/TO™ as preamble.
The Scorecard without the lag, AI agents that push KPIs live Scorecard.
The Accountability Chart has a new seat type, AI agents inside EOS® Accountability Chart.
EOS® Implementers are becoming AI Implementers Implementer audience.
Claude Code inside the L10®, a walkthrough Practical walkthrough.
Anthropic vs OpenAI for an EOS® company, what actually matters Vendor read.
From AI assistant to AI agent, the EOS® tools that should be autonomous The line between assistive and agentic.
People Analyzer™ plus AI, GWC™ when the teammate is an agent People Component.
An EOS® company's first 90 days with an AI agent rollout Practical playbook.

Part II: Deeper practice (posts 16 to 25)

How the framework's specific tools transform once the agent layer is real.

The Process Component of EOS®, where SOPs become executable SOPs as the agent's source code.
Quarterly and Annual sessions with AI in the room Strategic session prep and propagation.
The Issues List is your company's training data Issues archive as knowledge base.
EOS® for AI-native startups, adopting the framework after your first agent Reverse adoption path.
The 90-Day World™ and the compounding of AI improvements Why the quarterly cadence fits agent learning curves.
Your Marketing Strategy is the AI agent's voice Three Uniques, Proven Process, Guarantee operationalized.
The 1-Year Plan as a Rocks calendar for agents Annual planning as agent roadmap.
Bloom Growth, Ninety, Traction Tools, and the AI-native EOS® layer Vendor evaluation.
Scaling Up vs EOS® vs OKRs, which framework absorbs AI agents best Framework comparison.
The Visionary-Integrator relationship in a hybrid workforce The dyad.

Part III: Rhythm and discipline (posts 26 to 35)

The L10® and Quarterly cadence with agents, plus governance, edge cases, and one full case study.

The Same-Page Meeting™ with AI in the room Visionary-Integrator weekly.
Customer Headlines from CSAT and review data The L10® section AI was made for.
Letter vs Spirit of the SOP, what AI agents are allowed to interpret Calibration framework.
The Two Wars problem and AI as the Visionary's relief valve Inside vs outside war.
EOS® for agencies running on agents, a Sneeze It case study Our own story.
Annual planning with an AI red team, stress-testing the V/TO™ The loyal critic pattern.
The agent retirement protocol, how to fire an AI seat well Including Jeff's hearing.
When NOT to add an AI agent, the negative case Seats and processes that should stay human.
Compliance-aware AI inside EOS® healthcare, finance, and regulated industries HIPAA, SOC 2, GLBA, licensed-professional-in-the-loop.
ChatGPT Custom GPTs vs Claude Projects for EOS® workflows Tactical comparison.

Part IV: Roles (posts 36 to 39)

Per-seat deep dives. What each role on the Accountability Chart does differently when AI agents are in the picture.

Part V: Industries (posts 40 to 45)

How the framework applies per industry. Each post covers the agent layer specific to the vertical's data sources and operational reality.

Part VI: Platforms, governance, and scale (posts 46 to 55)

The tooling layer, governance practices, and how the framework adapts to non-standard company shapes.

How to use this series

If you are starting from scratch with no AI in your EOS® company yet, read in order through Part I and then jump to the post that matches your role and industry.

If you have already used ChatGPT or Claude as an assistant and want to graduate to an agent layer, start at post 13 (the assistant vs agent line), then read posts 11, 8, and 15 in that order for a fast path to your first working agents.

If you are an EOS® Implementer® looking to coach AI integration, read posts 10, 31, 35, and 50 first.

If you run a regulated business, read post 34 before post 15.

If you run a multi-location, family, holdco, or distributed company, jump to your specific structural post in Part VI alongside Part I.

What the series does not cover

Three areas this series deliberately stays out of.

One, AI inside your product. Agent integration in your customer-facing product is a separate decision from agent integration in your operating layer. Build the operating layer regardless.

Two, specific tool tutorials. "How to set up Claude Code step by step" is not in this series. The patterns are platform-agnostic. Use Anthropic's, OpenAI's, Microsoft's, or Google's documentation for the tool-specific setup.

Three, debates about AI safety, capability timelines, or general AI discourse. This is a practitioner series about a specific operational pattern. The broader AI conversation is real and matters; not the focus here.

About the series

I am David Steel. I run Sneeze It, a small marketing agency that runs EOS® and operates a portfolio of internal AI agents that handle parts of our operations. The series draws from our actual practice. Where we have failed (and we have, including formally retiring one of our agents), the posts say so. Where the patterns are still developing, the posts flag the uncertainty.

This is an independent practitioner series. It is not affiliated with or endorsed by EOS Worldwide, Anthropic, OpenAI, Microsoft, Google, or any platform vendor named in the posts.

If you build something on these patterns and it works (or fails) in instructive ways, I would like to hear about it. The OTP platform that hosts this series exists specifically because we believe coordination intelligence between companies is the next operating layer worth building.

EOS®, Entrepreneurial Operating System®, V/TO™, Vision/Traction Organizer™, Level 10 Meeting®, L10®, Rocks™, Scorecard, Issues List, Accountability Chart, IDS, People Analyzer™, GWC™, Core Focus™, 10-Year Target™, 3-Year Picture™, Marketing Strategy, Three Uniques, Proven Process, Process Component, Same-Page Meeting™, 90-Day World™, Six Key Components™, Traction®, Rocket Fuel®, Followed By All™, Visionary, Integrator, Quarterly, Annual, EOS® Implementer®, and Professional EOS® Implementer® are concepts and trademarks of EOS Worldwide, LLC. This article is an independent practitioner perspective and is not affiliated with or endorsed by EOS Worldwide.