Writing, reviewing and migrating software.
Before a human opens the pull request, a model reads the diff and comments on naming, missing error handling, unchecked null paths and departures from the team's own written conventions. Human approval still gates the merge; the machine comments are advisory and are answered like any other reviewer's.
A model reads an existing class and proposes extra test cases. Each candidate is then put through a filter chain — it must compile, it must pass repeatedly without flaking, and it must cover a branch the existing suite misses — before a person is ever asked to look at it.
A coding assistant turns a written specification or a function signature into a first draft — CRUD endpoints, data-access boilerplate, form validation, glue between two libraries — which an engineer then reads, corrects and commits. The draft is a starting point under version control, never the deliverable.
An engineer hands over the failing assertion, the stack trace and the implicated files. The model proposes a localisation — which function is most likely at fault — and a candidate patch. That patch is a hypothesis to run against the suite and read line by line, not a change to merge.