Ship and move on — stack now, reconcile later.
Stacked Changes let developers and agents keep shipping small, dependent steps without stopping to coordinate every edge up front. Vex preserves each Change and its dependency order, so the team can organize, review, and reconcile the chain before it lands.
How stacked Changes work
Agents keep shipping. Vex keeps the chain legible.
Keep iterating instead of waiting for every adjacent change to settle. Vex keeps dependency order, patchsets, checks, and policy attached so the team can organize the work later and reconcile the accepted stack before it lands within one component.
Running product
The focused edge makes every member’s chain position and check state readable while the grouped view preserves dependency order.
The visible stack is contained within one repository component.
/vex/changes?view=stack
Vex organization · 11 Aug 2026
How the graph resolves
The Change relationship is stored in source, so the review surface can show it directly instead of reconstructing a stack from branch targets.
Source graph / dependent changes3 Changes
AChange AAdd timezone columnAccepted BChange BReturn timezone from APIIn review CChange CShow timezone in settingsWaiting for B
Stable identity
A Change keeps its identity while its patchsets evolve.
Explicit order
The graph records which Changes are required by later work.
Focused review
Review each step separately while preserving the shape of the whole idea.
Guarded landing
Inside one component, Vex checks the required stack before it lands.
Change detail
The Change page ties required checks and every member of the landing closure to one durable Change identity.
The Land 4 Changes action applies to this single-repository stack, not a federated aggregate.
/vex/change/625
Vex organization · 11 Aug 2026
Start with proof