Should the platform know anything about the software it generates?

Reddit r/AI_Agents Tools
software-generation platform-design api-contracts testing openapi breaking-changes artifact-management

Summary

The author is building a software generation platform and questions whether it should know about generated components, advocating for artifact-based contracts and lifecycle management.

I’m building a platform where a user describes a task, and it generates an agent together with the software it needs: UI, APIs, services and a database. One of the problems I’m dealing with now is how much the platform itself should know about the generated software. My current approach is to keep generated services isolated and make the artifact itself the source of truth. For example, when generating a UI, I don’t want the platform to maintain knowledge of every generated API route. The UI and backend should communicate based on the contracts that exist inside the generated artifact. The platform should mostly care about lifecycle: building, running, updating and validating the artifact. I’m now working on generic testing around the generated OpenAPI specs to detect breaking changes between services and across versions. I’m curious how others would approach this. Would you keep the platform completely unaware of generated routes and rely on contracts inside the artifact, or would you maintain some representation of the generated API at the platform level as well?
Original Article

Similar Articles

Platform engineering still matters

Lobsters Hottest

An opinion piece arguing that platform engineering and code reuse remain valuable even with AI coding tools, because tokens cost money and reuse provides leverage. Cites Martin Fowler's similar argument about refactoring.

Should an agent be code or a declared thing with its own runtime?

Reddit r/AI_Agents

The author argues that AI agents in production should be defined as declarative manifests with their own runtime, rather than being scattered across application code, in order to enable proper versioning, observability, and rollback. They present their own solution as an open-source tool.

Do coding agents need an OS-like control plane? I built a prototype and want critique.

Reddit r/AI_Agents

The author introduces 'KnowledgeOS', a prototype control plane designed to govern local coding agents by managing task lifecycles, preventing state drift, and ensuring execution evidence. They are seeking architectural critique on whether this OS-like abstraction is necessary or if it constitutes over-engineering for agent workflows.