merlins-potion

Persistent agent profiles are created by storing metadata, prompts, and extensions under the /a0/agents/<profile>/ directory path. This mechanism ensures that agent configurations remain available across multiple workflow execution cycles without requiring manual reconfiguration.

The Holobiont Genome Protocol is a structured payload format used to dynamically spawn on-demand subordinate agents via the call_subordinate function. It enables automated agent instantiation and coordination while reducing manual setup overhead in complex AI governance tasks.

Pre-flight approvals require submitting a PRE-FLIGHT SPEC and obtaining explicit King Arthur profile authorization before any agent instantiation occurs. This protocol ensures controlled governance validation before dynamically spawning subordinate agents across workflows.

Yes, the four-layer signaling system supports structured communication using YAML, XML, JSON, and Markdown formats simultaneously. This multi-format approach enables flexible, structured data exchange between persistent agent profiles and dynamically spawned subordinate agents.

Yes, King Arthur's primary profile is required for orchestration as it provides the explicit pre-flight approval needed before subordinate agents can be instantiated. The integration with this primary profile governs the entire dynamic agent spawning lifecycle.

On-demand subordinate agents require explicit pre-flight approval for each instantiation and rely on the Holobiont Genome Protocol payload structure, meaning workflows cannot bypass the King Arthur governance validation or operate independently of the four-layer signaling system.