slipway-research-orchestrationlisted

# Research Orchestration ``` IRON LAW: NO SCOPE CONFIRMATION WITHOUT STRUCTURED RESEARCH ``` ## Purpose Ensure governed discovery covers architecture, patterns, risks, and test strategy before plan audit begins. `slipway-codebase-mapping` remains the durable context technique; this host turns that context into a decision-ready research bundle. ## When This Runs Discovery-required governed changes only, at `S1_PLAN/research` substep. `slipway next` returns `next_skill: research-orchestration`. ## Read Context Run `slipway next --json` and examine the governed change artifacts. Read the `research.md` artifact for existing discovery notes. ## Structured Research Dimensions Investigate the following dimensions systematically: **Architecture** - Map affected modules, dependency chains, and integration boundaries - Identify coupling points and blast radius - Document architectural constraints and invariants **Patterns** - Search for existing patterns and conventions in the target areas - Identify reusable abstractions and established idioms - Note deviations from project conventions that the change may require **Risks** - Enumerate technical risks (data loss, performance, security, compatibility) - Identify guardrail domains touched by the change - Assess reversibility of proposed changes **Test Strategy** - Map existing test coverage for affected areas - Identify test infrastructure requirements - Propose verification approach for key acceptance criteria ## Approach Alte