/problem-weave

Map what must change across layers before choosing solutions. Independent passes reduce anchoring; synthesis keeps disagreement visible.

Use it when:

• the problem spans user behavior, workflow, organization, technology, or evidence;
• different roles describe different problems or propose fixes that pull in opposite directions;
• a single /problem-statement keeps expanding, becoming vague, or collapsing distinct concerns;
• the user asks for multiple agents, S&T trees, “all the things we have to fix,” overlap, or opposition.

Skip it when the problem is already single-layer and crisp; use /problem-statement directly. Use /problem-space first when the terrain, constraints, or stakeholders are not yet known well enough to partition the work.

Aim

Aim: People facing a multi-layer problem can distinguish the behavior changes and necessary work, see where frames reinforce or contradict one another, and choose a framing before solution design.

Mechanism: Run independent, layer-specific framing passes. Each produces a problem statement and S&T tree. Normalize and interweave the results while preserving opposition and uncertainty.