If your AI-assisted change passes every test, that still does not tell you who inherits it.
The hidden bill starts when nobody records what changed outside the function. A new dependency, API, data path, service responsibility, or shared convention can be perfectly functional and still leave someone else with the upgrade, security, rollback, or explanation work.
That is not proof that AI code is worse. The research is mixed. Some controlled studies found faster or better results on bounded tasks; another found experienced developers slower on complex repositories; other work found no clear downstream maintainability penalty. The narrower problem is easier to defend: cheap generation can make consequential boundaries cheaper to change than they are to understand.
That is how speed moves the work downstream.
Use one pre-merge question for material AI-assisted work:
What boundary changed, who maintains it, and what review did speed replace?
If the answer is “none,” normal review and CI may be enough. If the answer is a new library, public contract, persistent schema, cross-service path, trust boundary, or shared platform rule, name the accountable maintainer and the evidence that supports the choice. Link the contract test, dependency check, ADR, owner assessment, or rollback proof.
Do not turn this into an AI ceremony. Apply the same trigger when a human makes the same consequential change. AI authorship is a risk signal when the change is broad or nobody can explain the design well enough to modify it without asking the model again. It is not a verdict.
Engineers can answer the question in the pull request. Decision owners have a different job: protect enough review and integration time for the answer to be useful. If the component team has not agreed to maintain the new dependency, a green test run does not give you permission to assign them the bill.
On your next material change, write the boundary, maintainer, displaced review, and supporting evidence before merge. If one is missing, say exactly what is missing and hold the decision there.
The tests may be green. You still need a reason to approve.