# How components can help us govern agents

DevFeed: [How components can help us govern agents](<https://devfeed.tech/articles/how-components-can-help-us-govern-agents-124135.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4244633/how-components-can-help-us-govern-agents.html>)

Author: Jon Udell

Published: 2026-11-09T09:00:00Z

Content type: opinion

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [Low code](<https://devfeed.tech/topics/low-code.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [React](<https://devfeed.tech/topics/react.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Library](<https://devfeed.tech/topics/library.md>), [Design system](<https://devfeed.tech/topics/design-system.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-development-approaches-generative-ai-software-development](<https://devfeed.tech/tags/artificial-intelligence-development-approaches-generative-ai-software-development.md>), [components](<https://devfeed.tech/tags/components.md>), [css](<https://devfeed.tech/tags/css.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [development-approaches](<https://devfeed.tech/tags/development-approaches.md>), [domain](<https://devfeed.tech/tags/domain.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [framework](<https://devfeed.tech/tags/framework.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [html](<https://devfeed.tech/tags/html.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llms](<https://devfeed.tech/tags/llms.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [markup](<https://devfeed.tech/tags/markup.md>), [programming](<https://devfeed.tech/tags/programming.md>), [react](<https://devfeed.tech/tags/react.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [solution](<https://devfeed.tech/tags/solution.md>), [standards](<https://devfeed.tech/tags/standards.md>), [storytype-feature](<https://devfeed.tech/tags/storytype-feature.md>)

## AI overview

The excerpt argues that reusable components can make agent-built applications easier to govern by constraining configuration and providing shared observability. XMLUI uses concise semantic XML to compose wrappers around React components, with lifecycle events that avoid requiring agents to write cleanup logic. Its shared tracing can record interactions by accessible labels and bridge opaque chart events into meaningful data events. For higher-risk integrations, the proposed component contract lets a runtime validate settings such as registered SFTP hosts and host-key verification before starting, while recording transfers alongside UI activity. The author's case is that maintained components can centralize instrumentation, policy checks, and fixes across apps; the excerpt presents this as an architectural approach, not proof that every component or vendor is reliable.

## Source excerpt

My most-cited BYTE cover story was 1994's Componentware, which made the case for a two-tier architecture best exemplified then by Visual Basic and its component ecosystem. The prevailing strategy for software reuse, object-oriented programming, hadn't gained the traction we all expected. Visual Basic showed us why it hadn't. Objects were written in the same languages, and by the same specialized coders, as the programs that reused those objects. VB flipped the script. Code-savvy component builders created building blocks that domain-savvy systems thinkers could wire together. Then the web flipped the script again. The browser was the new canvas, and it left the component ecosystem behind. Plugins came and went. The web platform eventually did define standards for components but they've been eclipsed by the web's de facto standard framework, React, and its component architecture. And just like objects 30 years ago, React components are both produced and consumed by specialized coders. There wasn't a good way for a modern solution builder to tap into React's component ecosystem. The framework that I co-maintain, XMLUI, harks back to the VB model. A UI is defined by concise semantic XML markup that refers to a catalog of components. There is no visual canvas but, as we debated whether or how to recreate that experience, the question became moot. When agents write declarative markup in conversation with us, direct manipulation matters less than it used to. A better target language for LLMs It's no accident that Markdown has become a primary way for humans and AIs to collaborate. Why not HTML and CSS? Markdown constrains AIs to a smaller set of patterns, and that's a good general rule. Our new agentic team members are powerful but undisciplined. Left to their own devices they behave in unpredictable ways. The fewer degrees of freedom we allow them, the better things will go for all of us. The same principle applies to coding. When you ask an LLM to build an app with Reac