synthesis-explore

# Synthesis — Explore (Phase 1 Blind Combinations → Phase 2 Emergent Mechanisms) This is the FIRST synthesis stage. It fuses two jobs that MUST stay ordered: **Phase 1** draws vector combinations BLIND (vector-first, before any tactic exists), and **Phase 2** derives the NOVEL MECHANISM that emerges from each combination. Vector-first thinking is the novelty engine: you commit to combinations BEFORE knowing what tactic they might produce, which is how you escape conventional playbooks. **Output: 15-20 raw vector combinations + 12-18 validated mechanisms. NO TACTIC NAMES. NO EXECUTION STEPS.** (Tactic design is synthesis-build's job.) Vectors and their definitions come from the per-run `growth-factors.json` (the LIGHT DB). Do NOT read `tactics_DB/` (clean-room — moat-critical). The category structure and `{prefix}-NNN-slug` ID format are shared conventions; the specific IDs are whatever this run mined. ## The two phases are WALLED — do them strictly in order **You MUST complete Phase 1 (blind draw + combinations) in FULL before starting Phase 2 (mechanisms).** The output must physically PROVE this ordering: the section `## Blind Draw (IDs only)` must precede `## Vector Combinations`, which must precede `## Validated Mechanisms`. If you catch yourself deriving a mechanism (Phase 2) before the blind draw and combinations (Phase 1) are written, STOP — you have broken the wall; go back. ## Inputs & Output The invoker provides (do not hardcode absolute paths): - `WS/01-diagn...