Blueprints Become Contracts for Complete Agent Teams
The squad types are now part of the canonical Blueprint shape. That gives a principal's agent team one idempotent deployment contract: the agents that must exist, the squads that compose them, the roles they hold, and the options that bound their work.
Top-Level Means Canonical
Earlier orchestration experiments nested team definitions under an implementation-specific section. The new schema places squads beside agents. That small structural change matters. It says a squad is a deployed application resource, not private configuration for one orchestration library.
Agents are ensured first, preserving the Blueprint behavior developers already rely on: missing agents are configured, healthy existing agents are not overwritten, and each result is observable. Squad provisioning then resolves those known handles into a team. A bare handle remains scoped to the target principal, while cross-principal references remain explicit and subject to access control.
Roles Carry Intent
Task squads distinguish executor and subject-matter-expert roles. The executor turns plan items into action. SMEs are consulted when the task needs specialized judgment or becomes blocked. Orchestrator squads distinguish the coordinator from the members it can route to.
Those roles are configuration, not prompt folklore. They can be reviewed in a pull request, validated before deployment, and rendered in an admin surface. Options such as iteration limits, delegation behavior, and completion rules live alongside the role assignments that depend on them.
Idempotency Is the Feature
The happy path for multi-agent demos is easy. The production path is repeatedly applying a desired state without resetting an agent that already has conversation history or operator-tuned configuration. Blueprints continue to protect configured agents, return health per resource, and allow provisioning flows to retry safely.
That makes the Blueprint suitable for first sign-in, tenant creation, environment deployment, and reconciliation jobs. The application remains responsible for deciding when a new Blueprint version intentionally reconfigures something; omission is not deletion and a version string is not an automatic migration.
With composition settled, we can move autonomous execution into the agent runtime itself. Next up: the FabrCore Agent Harness.