interview-cross-cutting

name	interview-cross-cutting
description	Funnel level 2 — structure the domain into behaviour groups, bounded contexts, integration points, and lifecycle events.

Interview (Cross-cutting)

1. Load [[requirements/interview-techniques]], [[architecture/quality-attributes]], [[methodology/simplicity-discipline]] — CIT, Laddering, CI Perspective Change, and the Active Listening protocol; the quality-attribute taxonomy to elicit; and the simplicity discipline.
2. Read the running interview-notes; append the cross-cutting findings to it.
3. Structure the domain into behaviour groups, bounded contexts, integration points, and lifecycle events. Probe each with CIT and Laddering; IF recall stalls THEN re-frame via CI Perspective Change. Capture the quality attributes stakeholders care about as one-line scenarios (stimulus → response), not bare words, per [[architecture/quality-attributes]].
4. Ask the simplicity question for each behaviour group: "Is this group speculative — not grounded in a cited stakeholder need?" A group with no CIT incident and no laddered constraint grounding it is speculative per [[methodology/simplicity-discipline]]; flag it for drop at consolidation or ground it with a cited need now.
5. Apply Active Listening L2: give a brief synthesis when transitioning between behaviour groups — confirms completeness, offers a recovery point.