Why I Built Three Agentic Frameworks — And Connected Them With a Single Document

A few months ago, something shifted in how I see this profession. I realized the deep divide between functional consultants and technical developers — almost a caste system in the Microsoft Dynamics world — was about to dissolve. Back then I thought it would take years. Now I believe it is months away.

That conviction pushed me to rethink my own profile. I needed to become more hybrid: someone who could move fluidly between AL code, Power Platform orchestration, and data modeling. But I also needed tools that matched that ambition — tools that updated the role of the AL professional for the agentic era.

ALDC Was the Starting Point

ALDC — the AL Development Conductor — was born from that urgency. Many of you already know it, use it, and have told me it inspired your own approaches. That was always the goal. I do not believe in inner circles. Open source means open.

The framework brings a structured agent role model to GitHub Copilot for Business Central: an architect that designs, a spec layer that details, and a conductor that executes through specialized subagents. It replaces vibe coding — the habit of prompting an LLM and shipping whatever comes back — with governed, auditable AL development.

Then Came the Friction Points

Because I have the curse of never stopping — some call it FOMO, and they are not entirely wrong — I started looking at other daily friction points beyond AL.

When I build Copilot Studio agents for Business Central, I face the same coordination problems: multiple skills, no clear orchestration, no validation gates. That thinking produced CIRCE, an agent framework for Copilot Studio built on the Skills for Copilot Studio foundation by Giorgio Ughini and the Microsoft Power CAT team. Five specialized agents — Author, Manage, Test, Troubleshoot, Conductor — with 33+ modular skills and a dedicated BC Extension Pack.

When I design Power BI solutions on top of BC data, the gap between a star schema on paper and a working semantic model is still painfully manual. That gap produced Delfos, a three-tier agentic squad for Power BI: an Architect that plans, a Lead Squad that coordinates, and four domain experts covering data modeling, DAX, visualization, and performance.

Three Frameworks, One Architecture

ALDC, CIRCE, and Delfos cover Business Central, Copilot Studio, and Power BI respectively. Each lives in its own workspace because each operates inside a different application with direct access to its own tooling. They do not share sessions or context — that would not be optimal.

What they do share is architecture. Five patterns run through all three:

• Agent squads / swarms with clear role separation
• Mandatory human validation at every critical gate
• Skills evidencing — agents must declare which skills they loaded and what patterns they applied (this is deliberately educational, designed for adoption)
• Cross-session memory — still an active research area, but foundational to the design
• A governed workflow that replaces prompt-and-pray with structured orchestration

The Extension Manifest — One Document, Two Destinations

What connects the three frameworks is a concrete artifact: the Extension Manifest. When ALDC finishes a BC extension, it generates a manifest that feeds directly into CIRCE (with MCP connection coordinates and relevant tools) and into Delfos (with data structures, typed fields, and star schema hints).

One document. Two destinations. Zero manual translation between teams.

What Comes Next

I am preparing a series of content to expand and share this vision. Starting with an article that breaks down the architecture, the five shared patterns, the manifest mechanism, and why vibe coding is just technical debt with a chatbot on top.

Link coming soon.

AI is not something you talk about. It is something you build.

Original Post https://techspheredynamics.com/2026/04/03/why-i-built-three-agentic-frameworks-and-connected-them-with-a-single-document/