doc-set-plannerlisted

# doc-set-planner The orchestration engine of the suite. A broad subject is *planned and decomposed*, not hand-assembled doc-by-doc. One engine + declarative per-group recipes (mirroring an orchestrator -> fan-out pattern): take a subject, decompose it into a group's member documents, fan out to the member genre skills, and reconcile the cross-document MIF `relationships[]` graph. ## Engine flow (genre-agnostic) 1. **Scope** — take the subject + target group; load the group recipe from `recipes/<group>.json`. 2. **Plan** — decompose into the recipe's member docs; emit a plan (what each member covers, the shared MIF namespace, the intended cross-link graph). When a semantic corpus is available, search it for each planned member first (see *Semantic discovery* below) and surface strong hits as "existing coverage — extend instead of create?" decisions in the plan. 3. **Fan-out** — invoke each member skill with its slice; members author independently (in parallel where possible). 4. **Reconcile** — wire MIF `relationships[]` across members per the recipe's cross-link contract; dedupe entities. When a corpus is available, offer find-similar results per member as *candidate* additional `relationships[]` targets for the author to accept or reject. 5. **Validate** — every member passes its own acceptance (`mif-validate --level 1`) **and** the set is *link-complete*: every declared cross-`relationships[]` target resolves to a produced member. ## Re