Corey JamesThe story
Someone types a feature request into chat. A planner turns it into a plan, a panel of different models argues the design until they agree, and developers who can search the whole codebase and see what a change will break build it. A reviewer checks the result against the plan, a red team tries to break it and a spend guard refuses any compute past the limit the owner set. The requester gets working software and a record of why each decision was made.
The crew
The specialists behind this role, grouped by the kind of work they do.
Does the work
- Release EngineerScreens each candidate change for benchmark gaming, builds release images from pinned inputs, checks every hash, compares the candidate with the current baseline and promotes it, then tells the other teams to rebase.Also serves The Engine Builder
- Software DeveloperTakes one assigned task, reads the brief and the code around it, writes and tests the change inside its allowed folders, submits evidence for each acceptance point and fixes what reviewers send back.Also serves The Automation Builder
- Project CloserCloses a project, phase or program only when every required item carries a current sign-off, writes the closing summary with cost, archives the team and retires everything it opened.Also serves The Programme Office
- Project PlannerTurns a goal into a scoped project plan with acceptance criteria, a task breakdown, who may change which files and a staffed team, and hands it back for one yes or no.Also serves The Pocket Operator
- Software Delivery CrewThis crew of five takes a plan and turns it into working code: a planner writes the tasks, a builder writes the code, a reviewer reads every critical path, a researcher answers "what else does this touch", and an inspector checks the finished work before it is accepted.Also serves The Pocket Operator
Challenges decisions
- Red Team ReviewerAttacks every major decision and every change of scope from a different model family than the builders, looking for the assumption that breaks, and holds approval until it has answered.Also serves The Advisory Board, The Second Opinion
- Plan Deliberation PanelPuts several models from different vendors in one structured debate that works through numbered plan revisions and ends only when all agree, then hands over a plan ready to execute.Also serves The Migration Planner
- Code ReviewerReviews finished code and reports against the plan, lists what is missing, extra or wrong with file and line, freezes the list after the first pass and then checks only the fixes.Also serves The Ticket Clearer, The Contractor Pass
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 Change Board, The Migration Planner, The Follow-Through Engineer, The Code Guide
- Decision RecorderWatches the team's decisions log and working notes folder.Also serves The Record Keeper, The Institutional Memory
Audits and guards
- Acceptance CheckerChecks the facts of the finished work against each acceptance point, refuses claims that are only narrative, and either signs the item off or returns a precise fix list.Also serves The Ticket Clearer
- Compute Budget GuardianHolds the line on the daily spend that only you set: it refuses any start the budget cannot cover and says why, warns you as spend climbs, and stops paid machines at the cap.Also serves The Bulk Run Manager, The Spend Controller
Where this crew also works
Routes
Routes this role works in. Its place in each one is filled in.