Records the design for drop-in, data-driven workflows/labels/actions: YAML playbooks as pure orchestration data over four typed logic positions (Workflow/Module/Channel/Forge), go:generate-driven schemas, and load-time collision handling (detect+log+report, no auto-arbitration). Flags execution-time idempotency and mid-run failure handling as unresolved gaps to close before Channel/Forge or multi-action playbooks ship.