ApertureOscillation

Design tensions are identified by oscillating question scope across narrow tactical and wide strategic passes to analyze component logic against system coherence. ApertureOscillation requires a tactical target and strategic context to return divergence analysis, scope recommendations, and alignment findings.

Scope framing evaluates a build request through both component-level and project-level perspectives to ensure requirements alignment. This prevents isolated failures by synthesizing where narrow tactical logic diverges from wide strategic system requirements before approach commitment.

Run a pre-commit design review by providing the AI with both a tactical target and strategic context to process a three-pass workflow. This generates narrow component logic, wide system requirements, and a synthesis pass producing design tensions and coherence assessments.

Yes, scope oscillation operates without dependencies to analyze workflow orchestration by applying narrow and wide framing passes. It processes your tactical target and strategic context directly to surface scope recommendations and alignment findings.

Design tension analysis is not suitable when you lack either a distinct tactical target or strategic context, as both inputs are required. It should also be bypassed if you only need shallow single-zoom answers without cross-checking component logic against broader project context.

The best way to align feature scope is running a three-pass workflow that oscillates between narrow component logic and wide system requirements. This produces a synthesis pass detailing design tensions and coherence assessments to validate alignment before approach commitment.