Consistent design gives predictable experience
The fastest way to make an autonomous system untrustworthy is to let it reinvent how to build things every time. Carol's team chose the opposite: Merlin, the orchestrator, assembles every build from a fixed library of templates—approved blueprints with the same phases: decide, execute, review. Each template is pre-blessed by Archon (the designer), embeds policy, and assigns roles, so every step is governed the same way: the same checks, the same gates, the same design patterns. This isn't bureaucracy—it's construction safety. A thousand bespoke builds each need inspection; a thousand identical builds need one inspection of the template, then you trust by construction.
If templates lock down how work gets built, who gets to decide what Carol becomes? Elrond, the head of engineering, plans high—he breaks each initiative into modules and success criteria, free to rewrite the plan as outcomes arrive. Merlin, the orchestrator, builds low—he fills templates without improvising the process, because the process is already blessed. The design principle: Elrond owns strategy and has autonomy where it matters most; Merlin owns fidelity and has discipline where consistency cannot break. That's how agentic systems adapt smartly without drifting.
When Merlin fills a template, he's not choosing phases or roles—the template already did. Each template carries its source of truth: the policy it honours, the roles who own each phase, the controls built in. Because Archon blessed the template before it went into the library, every use is a use of an already-approved design. Templates aren't consistency by repetition—they're governance by design, with controls woven in, not bolted on.
