Appvecta Impact

Know the blast radius before you type.

Before an edit, Appvecta will answer what it touches. The answer is grouped by layer rather than delivered as a flat file list, and observed relationships are shown separately from AI-inferred risks.

Planned for the private alpha

A worked example

For the request "Add passengerType to Ticket", the impact view is designed to return:

Direct model impact        TicketDto, Ticket, TicketMapper
Persistence impact         TicketEntity, TicketDao, Room migration likely required
UI/state impact            TicketViewModel, TicketScreen
Background/output impact   TicketSyncWorker, TicketPrinter
Tests likely affected      TicketMapperTest, TicketRepositoryTest, TicketViewModelTest

Observed and inferred, never mixed

Relationships the graph actually parsed are listed apart from risks a model proposed. A likely Room migration is a judgement; a MAPS_TO edge between TicketDto and Ticket is a fact with a file and a line range behind it. The interface keeps the two visually distinct.

Where impact is used

In the plan the agent shows you before it writes anything
In a QA failure report, to rank the source locations likely involved
As an MCP tool — brain.impact — available to whichever agent you already use
Later, post-alpha: as "run affected checks", offering the screens, flows and tests a symbol touches

All features Next: Appvecta Agent