Corey JamesThe story
Before the change goes in, the agent maps everything that calls the code being touched and everything it calls. It pulls the history of that area, including what broke the last time someone changed it. The manager reads one page: what the change reaches, what could fail and what to test.
The crew
The specialists behind this role, grouped by the kind of work they do.
Does the work
- Scope Change ManagerHandles a mid-project change from proposal to approval: it maps what the change touches, gets an architect's proposal, an independent ruling and a hostile second look, then folds the approved change into the live plan.Also serves The Programme Office
Challenges decisions
- Change Risk ReviewerBefore a change goes in, this agent works out how risky it is from what it touches, maps everything that depends on it and asks for the matching level of checking.Also serves The Safe Change Desk
- Change Impact ReviewerMaps everything a proposed change touches before anyone approves it and posts the impact summary on the merge request.Also serves The Migration Planner
- Independent Review ClerkIt matches the verdict to the review that was requested and releases or holds the project exactly once.Also serves The Second Opinion
- Performance ReviewerReads a change for slow paths and wasted work and reports them on the ticket with the lines concerned.Also serves The Review Panel
Keeps knowledge
- Code Impact AnalystFor every function or type a change touches, it lists what calls it and what it calls up to three steps out.Also serves The Software Department, The Migration Planner, The Follow-Through Engineer, The Code Guide
- Code Flow ExplainerTakes a starting point (a file and line, a function name or a plain question), traces how the work flows through the code, and explains it in plain language.Also serves The Developer Advocate, The Onboarding Buddy, The Code Guide
- Regression HistorianGiven a broken function or an error, works out which pieces of work touched that area and in what order, who calls it now, and how the failure travels through the code.Also serves The Record Keeper, The Incident Commander
- System HistorianReconstructs a system's story, covering the decisions that shaped it, the changes made, the problems hit and how each was fixed, and the trade-offs accepted, in time order.Also serves The Onboarding Buddy, The Record Keeper
Where this crew also works
Routes
Routes this role works in. Its place in each one is filled in.