# workflow templates

Meta replaced the orchestration layer of its data-pipeline agents with a thin router that only sequences work and runs reliability checks, leaving domain reasoning to 14 specialized subagents with isolated context. A single agent loaded with all domain knowledge worked in demos but began hallucinating in production, mixing naming conventions and code-generation patterns across subsystems. Configuration prep for a new data column dropped from three to four days by hand, or about a day with the earlier config-driven system, to under an hour, with about two-thirds of changes landing without significant human edits.

Meta replaced the orchestration layer of its data-pipeline agents with a thin router that only sequences work and runs reliability checks, leaving domain reasoning to 14 specialized subagents with isolated context. A single agent loaded with all domain knowledge worked in demos but began hallucinating in production, mixing naming conventions and code-generation patterns across subsystems. Configuration prep for a new data column dropped from three to four days by hand, or about a day with the earlier config-driven system, to under an hour, with about two-thirds of changes landing without significant human edits.