CHANGE GRAPH
See the consequences before committing to change.
Trace a proposed change across requirements, systems, code and teams—with the evidence needed to review its impact.
ARTUS / CHANGE REVIEW WORKSPACE
CR-112 / PROPOSED CHANGE
Enable guest checkout
One request. Several engineering consequences.
FOLLOW THE IMPACT →
REQUIREMENT
Account requirement
REQ-CHK-014 · Rev B
INTERFACE
Checkout API
POST /checkout · Contract v4
IMPLEMENTATION
createOrder()
orders/create-order.ts
VERIFICATION
Guest checkout tests
Coverage needs review
SELECTED / createOrder()
Why affected
Order creation requires customer_id.
Source
create-order.ts · lines 42–48
Owner
Order services team
Illustrative example · Draft interaction design
The request names one feature.
The implementation may depend on assumptions spread across several teams.
From proposed change to informed review.
Explore affected work, inspect its source and make review responsibilities visible.
A change review people can act on.
Keep affected scope, evidence and responsible owners together—without hiding uncertainty.
CR-112 / REVIEW SUMMARY
Enable guest checkout
AFFECTED SCOPE
Account requirement · Checkout API · Order creation
SUPPORTING EVIDENCE
REQ-CHK-014 Rev B · Contract v4 · create-order.ts a61c2e
RESPONSIBLE OWNERS
Product: behaviour · Engineering: identity · QA: coverage
Guest order tracking — needs review
Illustrative example · Draft interaction design
Bring a change your team is investigating.
Explore its dependencies, evidence and review scope with Artus.
