design-swarmlisted

<!-- ENGINE FILE — one source, two cuts. Installation-specific values (path roots, hooks, governance rule names, reference docs) are referenced generically as `cfg:<key>` and resolved by the config layer: `config/house-config.md` (house cut) or `config/house-config.example.md` (public example). Shared pipeline vocabulary lives in `shared/pipeline-conventions.md`. --> # Design Swarm — divergence-first design pass (stops at written design) **What this is.** A staged design pass where the main chat stays orchestrator, never doer: independent agents work the problem through fixed lenses and competing axioms, return schema-capped digests only, and the operator holds the two gates. Terminal outcome is a written, defensible design spec landed at a durable host path. **This skill does not build.** Adapted from Ari Leavesley's `brainstorming-swarm` v1.0.0 (stage spine, lens set, gates) onto house machinery and house discipline — comparison record: `cfg:refs.swarm_comparison`. ## Non-negotiables (read before running) 1. **Orchestrator, not doer.** The conductor seat routes briefs out and synthesizes digests in. It does not do lens work inline. If you catch yourself writing a lens analysis in the main context, stop and dispatch it. (Exception: `serial_fallback` — one seat role-plays the legs sequentially under the same schemas and gates; announce the mode in the run record.) 2. **Digests only.** Workers return the named fields below, under the word caps. No