Determining the Scope of Analysis

After a trigger is received, SynapseAudit determines what code should be analyzed.

Scope is derived entirely from editor context and user action.

Depending on how the analysis was initiated, SynapseAudit will operate on:

• The currently active file in the editor, or

• A specific block of code selected by the developer

This scoped approach is intentional.

By limiting analysis to explicitly visible or selected code, SynapseAudit ensures that:

• Analysis remains relevant to the task at hand

• Results are easy to understand in context

• Performance remains predictable

• Developers retain full control over what is examined

There is no automatic expansion of scope beyond what the developer has provided.