Cross-links #
- AI Code Architecture The distinction between “vibe coding” and “agentic engineering” (structured, verified) provides context for “executable architecture,” and the “Coordinator Agent” pattern is an example of a “Harness-of-Harness.”
- AI Code Quality The distinction between “vibe coding” and “agentic engineering” provides context for the shift to system-level quality and the human’s role as “agent manager.”
- Claude-Specific Expertise The “loop” pattern (automated verification code) is a key mechanism differentiating “agentic engineering” from “vibe coding,” and the “Coordinator Agent” pattern could be an implementation of dynamic model routing.
- Team & Org Use of Claude The
CLAUDE.md pattern for shared, version-controlled context is a concrete example of “Agentic Governance” and the structured approach of “agentic engineering.” - Applications of Vibe Coding “Comprehension Debt” provides a strong rationale for the distinction between “vibe coding” and “agentic engineering” and the need for “Agentic Governance.”
- Vibe Coding for People Who Can’t Code: A five-part series. Part V — Doing this at work (Medium) — This article details a pattern for safely introducing “vibe coding” into a corporate environment by addressing the security and data governance risks that arise when moving from personal projects to internal business systems. After an initial attempt to build a new workflow system resulted in security risks by connecting to company systems from an uncontrolled environment, the successful solution was for a technical lead to build a sanctioned, internal, behind-the-firewall “vibe-coding platform.” This approach creates a safe, managed environment where employees can build useful applications against internal company systems, effectively applying the vibe coding technique one level up to solve the institutional adoption problem.
- Companies already run 3 agent platforms. Salesforce’s new Enterprise AI Harness wants to govern all of them. (VentureBeat) — Salesforce has announced its “Trusted Enterprise AI Harness,” a new framework aimed at governing heterogeneous, multi-platform agent environments within large companies. The harness includes six components—Trusted Context, Agency, Action, Governance, Security, and Models—along with an “AI Control Plane” for managing the entire agent lifecycle across third-party systems. This move addresses a quantified market need, with a recent survey showing that 85% of enterprises already run two or more agent orchestration platforms, with an average of 3.1 per organization.
- HelmGuard Raises $7.3 Million for Agentic GRC and Security (SecurityWeek) — The emergence of “agentic governance” as a formal market category is underscored by the $7.3 million seed funding round for HelmGuard, a startup building a platform for agentic governance, risk, and compliance (GRC). The company’s technique involves deploying its own AI agents to continuously collect and assess risk signals directly from source systems, automating assurance and control gap analysis workflows. This approach is designed to replace legacy GRC tools that are tied to static documentation and checklists, providing a live, unified view of risk across the enterprise, including the behavior of other deployed AI agents.
A New Orchestration Pattern Emerges: The Folder as Agent #
- The Folder Is the Agent (Every) — A specific, file-based multi-agent orchestration pattern is detailed as an alternative to complex agent swarms or protocols. In this methodology, each project folder becomes a specialized agent by containing its own context and instructions (a
CLAUDE.md or AGENT.md file). A central Ruby daemon watches a directory for requests; a lead agent breaks down a task and writes subtasks as files to the appropriate “agent” folders; and the daemon spawns worker agents in those folders to execute the work. This approach avoids the need for custom networking or agent-to-agent communication protocols, instead using the file system as a simple, robust messaging layer for dispatch and control.
A Named Technique for UI Generation: Component-Based Prompting #
- Vibe Coding Tip of the Day - Prompting Pages, Layouts & UI (Reddit r/Base44) — A concrete technique for generating more reliable and polished user interfaces with AI app builders is “Component-based prompting.” Instead of giving a vague, high-level goal like “Make me a dashboard,” which often results in a cluttered or broken layout, this method involves first describing the page’s structural and logical rules to the AI. The key is to define the layout structure, component hierarchy, spacing rules, responsive behavior, and how each section should interact before asking the AI to generate the full page, leading to more consistent and professional results.
- Emerging theme: The distinction between “vibe coding” (unstructured, prototype-focused) and “agentic engineering” (structured, verified, production-ready) is now the dominant framing in the discourse. Multiple articles are dedicated to clarifying this spectrum, often citing Andrej Karpathy’s evolution in terminology and emphasizing that the key differentiator is the degree of human-enforced structure and verification, not the tool being used.
- Emerging pattern: The “Coordinator Agent” or “Concierge Agent” is a recurring pattern for managing multi-agent complexity. Rather than having a swarm of agents communicate directly, a single lead agent is tasked with decomposing problems, dispatching tasks to specialized worker agents, and reporting status back to the human operator, often in a structured way that separates status updates from critical alerts.
- Source to watch: The
r/ClaudeCode subreddit appears to be a valuable source for grassroots, practical discussion among developers on emerging agentic patterns, tool workarounds, and infrastructure setups, offering a ground-level view of techniques being developed outside of formal corporate or academic publications.