--- title: "LLM integration is operating design | Len P. van der Hof" description: "Wiring a model is the cheap step. The scarce work is ownership, permission, and review: who owns the prompt, who owns the tools, and whose name the output…" image: "https://lenvanderhof.com/media/generated/blog-hero-operating-design-en-v2.9c62475bb98e.wide.webp" --- [AI Systems](https://lenvanderhof.com/en/blog/category/ai-systems/) Research guide # LLM integration is an operating-design problem The scarce work is ownership, permission, and review, not the model name on the invoice. Len P. van der HofPublished 22 August 20264 min read Ownership, permission, review. The model name is not a seat. Direct answer LLM integration is not an API problem. The call is cheap. The scarce work is operating design: who owns the model and the prompt, what the tools may see and change, who can fail the output, and whose name it carries. A named reviewer and a written override doctrine are the integration. STACK versions the artifacts. MCP is the contract on one tool. Neither substitutes for those four seats being filled. ## Key takeaways - If you cannot name four owners (model, prompt, tools, review), you did not integrate. You subscribed. - HITL is a person who can fail the output, not a dashboard glance. - Override doctrine is the written list of what the model may never do. - STACK and MCP sit next door. This page is the operating seats. The Delegated Mind and The Human-in-the-Loop Life are in production; the seats are already usable. A team “integrates” a model and means they put an API key in a secret store. The invoice has a model name. Slack has a bot. Nobody can say who owns the prompt, who owns the tools, or whose name a bad answer will carry. That is a subscription. It is not an integration. ## Four seats Operating design is four named seats. If any is empty, stop saying integrated. **Model.** Who chose this model, who can change it, and who pays when it is wrong. A default in a vendor console is not an owner. **Prompt and charter.** Who writes the standing instruction, and where it lives. A prompt in six chats is folklore. The charter says what the worker does. The [override doctrine](https://lenvanderhof.com/glossary/override-doctrine/) says what it must refuse: spending above a ceiling, speaking as the company, changing production data, closing a judgment you still own. **Tools.** What the model may see, change, send, or delete. [MCP](https://lenvanderhof.com/en/blog/mcp-explained-for-founders/) is the contract for one server. The operating question is who approved that contract, and who can revoke it at 17:00. **Review.** Who can fail the output against written criteria. A [human in the loop](https://lenvanderhof.com/glossary/human-in-the-loop/) is that person. A glance at a dashboard is not a loop. You would not ship a payment integration without those four. A language model that can mail, spend, or open a pull request is a payment integration with better prose. The worker definition sits next door. [What is an AI agent?](https://lenvanderhof.com/en/blog/what-is-an-ai-agent/) is three tests and a seven-field charter. This page asks who sits in the seats after you decided it is a worker. ## An empty-seat week Monday: someone pastes a key into the host. Tuesday: a prompt lives in three chats and a Notion page. Wednesday: the mail tool can send. Thursday: a customer gets a draft no reviewer saw. Friday: nobody knows whose name is on it. That week had a model. It did not have four names. The repair is not a better wrapper. Write the four names. Put the standing prompt in one file. Revoke send until the first ten calls have a reviewer. If [coordination](https://lenvanderhof.com/en/blog/why-multi-agent-systems-fail/) is already failing, adding a second unowned model makes the board worse, not smarter. ## What STACK is not doing on this page [STACK](https://lenvanderhof.com/frameworks/stack/) is the five-layer map for the repo: structure, toolchain, agent configuration, connection, knowledge and quality. [The Agentic Codebase](https://lenvanderhof.com/books/the-agentic-codebase/) is the live book. Version the artifacts like the app. This page is earlier and smaller. Before you argue about folders, fill the seats. A perfectly versioned prompt with no reviewer is still an unowned outcome. MCP is how a step touches the building: visibility, mutation, log. It is not who signed for the keys. ## The protocol that sits on the seats [The Delegated Mind](https://lenvanderhof.com/books/the-delegated-mind/) treats delegation as governance, not tooling. The protocol is PROVISO: pause, retain agency, observe, verify, integrate, own. The book is in production. It is not for sale. The one-page charter from that manuscript is already the right artifact: what agents may do, what they may never do, how output is verified, who signs off, whose name it carries. If you cannot write that page, you do not have an integration. You have a faster paste. [The Human-in-the-Loop Life](https://lenvanderhof.com/books/the-human-in-the-loop-life/) is the personal side. Human in the loop is not a property of the software. It is a question about you: where you stand in the cycle, at what level, and whether you are actually there. That book is an early draft. Use the question anyway. If approval has become the motion you make on the way to merge, the loop is decorative. ## A twelve-minute audit Pick one live model call in the company. SeatName, not roleFile or log that proves itLast time this seat actually actedModelPrompt / charterToolsReview Then write the one forbidden action, and whose name last week’s worst answer would have carried. Blank lines are the integration. Fill them or take the tools away. The model name on the invoice will not do it. Cite this:LLM integration is an operating-design problem.Len P. van der Hof. [https://lenvanderhof.com/en/blog/llm-integration-is-operating-design/](https://lenvanderhof.com/en/blog/llm-integration-is-operating-design/) · Published 22 August 2026. ## Terminology - [STACK](https://lenvanderhof.com/glossary/stack/) - [MCP](https://lenvanderhof.com/glossary/mcp/) - [Override doctrine](https://lenvanderhof.com/glossary/override-doctrine/) - [Human in the loop](https://lenvanderhof.com/glossary/human-in-the-loop/) ## Sources 1. [STACK framework](https://lenvanderhof.com/frameworks/stack/) 2. [MCP explained for founders](https://lenvanderhof.com/en/blog/mcp-explained-for-founders/) 3. [Override doctrine (glossary)](https://lenvanderhof.com/glossary/override-doctrine/) 4. [Human in the loop (glossary)](https://lenvanderhof.com/glossary/human-in-the-loop/) 5. [The Agentic Codebase](https://lenvanderhof.com/books/the-agentic-codebase/) 6. [The Delegated Mind](https://lenvanderhof.com/books/the-delegated-mind/) 7. [The Human-in-the-Loop Life](https://lenvanderhof.com/books/the-human-in-the-loop-life/) ## Related essays - [What is an AI agent?](https://lenvanderhof.com/en/blog/what-is-an-ai-agent/) - [MCP explained for founders](https://lenvanderhof.com/en/blog/mcp-explained-for-founders/) - [The Agentic Codebase: introduction](https://lenvanderhof.com/en/blog/the-agentic-codebase-introduction/) - [Version the agent OS](https://lenvanderhof.com/en/blog/stack-version-the-agent-os/) - [An agentic workflow is not an automation](https://lenvanderhof.com/en/blog/agentic-workflow-vs-automation/) - [Human in the loop meaning: a named person who can fail the work](https://lenvanderhof.com/en/blog/human-in-the-loop-meaning/) - [MCP meaning: Model Context Protocol, not a product](https://lenvanderhof.com/en/blog/mcp-meaning/) - [What is STACK? Five layers, not a vendor diagram](https://lenvanderhof.com/en/blog/what-is-stack/) ## Further reading - [STACK](https://lenvanderhof.com/frameworks/stack/) - [The Agentic Codebase](https://lenvanderhof.com/books/the-agentic-codebase/) - [MCP explained for founders](https://lenvanderhof.com/en/blog/mcp-explained-for-founders/) - [Override doctrine](https://lenvanderhof.com/glossary/override-doctrine/) - [Human in the loop](https://lenvanderhof.com/glossary/human-in-the-loop/) - [The Delegated Mind](https://lenvanderhof.com/books/the-delegated-mind/) - [The Human-in-the-Loop Life](https://lenvanderhof.com/books/the-human-in-the-loop-life/) About the author ## [Len P. van der Hof](https://lenvanderhof.com/en/authors/len-p-van-der-hof/) Entrepreneur, AI Innovator and Venture Builder Len P. van der Hof builds practical AI systems, digital ventures and evidence-informed tools for founders. ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Person", "@id": "https://lenvanderhof.com/#person", "name": "Len P. van der Hof", "alternateName": [ "Len van der Hof", "L.P. van der Hof", "Leendert Pieter van der Hof" ], "honorificSuffix": "MSc", "url": "https://lenvanderhof.com/", "image": [ "https://lenvanderhof.com/photos/len-portrait-1.jpg", "https://lenvanderhof.com/photos/len-portrait-2.jpg", "https://lenvanderhof.com/photos/len-portrait-3.jpg", "https://lenvanderhof.com/photos/len-portrait-4.jpg", "https://lenvanderhof.com/photos/len-speaking.jpg", "https://lenvanderhof.com/photos/len-hero.jpg" ], "jobTitle": "Entrepreneur, AI Innovator and Venture Builder", "description": "Len P. van der Hof, MSc, is a Dutch entrepreneur and AI innovator in Zwijndrecht. He builds ReasonKit, MindSesh, Undominated.ai, books under his name, the fiction imprint LPH98.lifestyle, and technology ventures through LPH98.ventures. Eleven titles in Systems for the Strategic Self are available now, in English and Dutch.", "address": { "@type": "PostalAddress", "addressLocality": "Zwijndrecht", "addressCountry": "NL" }, "alumniOf": { "@type": "CollegeOrUniversity", "name": "Rotterdam School of Management, Erasmus University" }, "knowsAbout": [ "Artificial intelligence", "AI agents", "Agentic AI systems", "LLM routing", "SEO", "Generative engine optimization", "Answer engine optimization", "Venture building", "Founder performance", "Founder psychology", "Evidence-based decision-making" ], "sameAs": [ "https://www.linkedin.com/in/lenvanderhof/", "https://x.com/LenvanderHof", "https://www.youtube.com/channel/UCTG20buKqYYbitqqf7l3zJA", "https://www.instagram.com/Lenvanderhof/", "https://www.threads.com/@lenvanderhof", "https://github.com/Lenvanderhof", "https://huggingface.co/LPH98", "https://www.npmjs.com/~lenvanderhof", "https://www.goodreads.com/author/show/70983905.Len_P_van_der_Hof", "https://www.amazon.com/author/lenvanderhof", "https://www.bol.com/nl/nl/b/len-p-van-der-hof-msc/609879394/", "https://bsky.app/profile/lenvanderhof.com", "https://mastodon.social/@Lenvanderhof", "https://crates.io/users/Lenvanderhof", "https://cursor.com/@Lenvanderhof", "https://medium.com/@Lenvanderhof", "https://gitlab.com/Lenvanderhof", "https://hub.docker.com/u/lenvanderhof/", "https://dev.to/lenvanderhof", "https://www.facebook.com/Lenvanderhof", "https://soundcloud.com/Lenvanderhof" ], "affiliation": [ { "@id": "https://lenvanderhof.com/#publisher" }, { "@id": "https://lenvanderhof.com/#mindsesh" }, { "@id": "https://lenvanderhof.com/#lifestyle" } ] }, { "@type": "WebSite", "@id": "https://lenvanderhof.com/#website", "url": "https://lenvanderhof.com/", "name": "Len P. van der Hof", "description": "Len P. van der Hof, MSc, is a Dutch entrepreneur and AI innovator in Zwijndrecht. He builds ReasonKit, MindSesh, Undominated.ai, books under his name, the fiction imprint LPH98.lifestyle, and technology ventures through LPH98.ventures. Eleven titles in Systems for the Strategic Self are available now, in English and Dutch.", "inLanguage": [ "en", "nl" ], "publisher": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#publisher", "name": "LPH98.ventures", "url": "https://lph98.ventures", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#mindsesh", "name": "MindSesh", "url": "https://mindsesh.net", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "SoftwareApplication", "@id": "https://lenvanderhof.com/#reasonkit", "name": "ReasonKit", "url": "https://reasonkit.sh", "creator": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "SoftwareApplication", "@id": "https://lenvanderhof.com/#undominated", "name": "Undominated.ai", "url": "https://undominated.ai", "creator": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#lifestyle", "name": "LPH98.lifestyle", "url": "https://lph98.lifestyle", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "ImageObject", "@id": "https://lenvanderhof.com/en/blog/llm-integration-is-operating-design/#primaryimage", "url": "https://lenvanderhof.com/media/generated/blog-hero-operating-design-en-v2.9c62475bb98e.wide.webp", "contentUrl": "https://lenvanderhof.com/media/generated/blog-hero-operating-design-en-v2.9c62475bb98e.wide.webp", "representativeOfPage": true }, { "@type": "BreadcrumbList", "@id": "https://lenvanderhof.com/en/blog/llm-integration-is-operating-design/#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://lenvanderhof.com/" }, { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://lenvanderhof.com/en/blog/" }, { "@type": "ListItem", "position": 3, "name": "AI Systems", "item": "https://lenvanderhof.com/en/blog/category/ai-systems/" }, { "@type": "ListItem", "position": 4, "name": "LLM integration is an operating-design problem", "item": "https://lenvanderhof.com/en/blog/llm-integration-is-operating-design/" } ] }, { "@type": "WebPage", "@id": "https://lenvanderhof.com/en/blog/llm-integration-is-operating-design/#webpage", "url": "https://lenvanderhof.com/en/blog/llm-integration-is-operating-design/", "name": "LLM integration is an operating-design problem", "description": "Wiring a model is the cheap step. The scarce work is ownership, permission, and review: who owns the prompt, who owns the tools, and whose name the output carries.", "isPartOf": { "@id": "https://lenvanderhof.com/#website" }, "primaryImageOfPage": { "@id": "https://lenvanderhof.com/en/blog/llm-integration-is-operating-design/#primaryimage" }, "breadcrumb": { "@id": "https://lenvanderhof.com/en/blog/llm-integration-is-operating-design/#breadcrumb" }, "inLanguage": "en-GB" }, { "@type": "BlogPosting", "@id": "https://lenvanderhof.com/en/blog/llm-integration-is-operating-design/#article", "mainEntityOfPage": { "@id": "https://lenvanderhof.com/en/blog/llm-integration-is-operating-design/#webpage" }, "headline": "LLM integration is an operating-design problem", "description": "Wiring a model is the cheap step. The scarce work is ownership, permission, and review: who owns the prompt, who owns the tools, and whose name the output carries.", "datePublished": "2026-08-22T11:00:00.000Z", "author": { "@id": "https://lenvanderhof.com/#person" }, "publisher": { "@id": "https://lenvanderhof.com/#person" }, "image": [ "https://lenvanderhof.com/media/generated/blog-hero-operating-design-en-v2.9c62475bb98e.square.webp", "https://lenvanderhof.com/media/generated/blog-hero-operating-design-en-v2.9c62475bb98e.landscape.webp", "https://lenvanderhof.com/media/generated/blog-hero-operating-design-en-v2.9c62475bb98e.wide.webp" ], "articleSection": "AI Systems", "inLanguage": "en-GB" } ] } ```