ApertureOscillation

Design misalignment is resolved by oscillating a single decision across narrow tactical and wide strategic framings to expose divergence. This reveals specific design tensions and scope recommendations ensuring local choices satisfy broader goals.

Checking system coherence requires a two-input check comparing a distinct tactical target against strategic context. This process surfaces hidden misunderstandings that single-scope analysis misses, yielding a coherence and fit assessment for pre-commit review.

Running a scope oscillation analysis involves a fixed three-pass workflow: frame the question narrowly, then strategically, then synthesize the divergence. You must provide both the tactical target and strategic context to generate actionable scope recommendations.

Tactical versus strategic framing is needed when local implementation logic conflicts with system-level requirements during scope negotiation. Oscillating between these framings exposes design tensions that indicate where a feature fits the wrong scope.

Yes, the approach operates without external dependencies to perform pre-commit reviews of feature design. It synthesizes tactical and strategic inputs to produce divergence findings and scope recommendations directly.

Single-scope analysis hides misunderstandings because it evaluates architecture decisions from either a local or global perspective, missing the divergence. Oscillating across scopes exposes where tactical implementation choices fail to satisfy strategic requirements.