---
title: "Comment by Ascendra Ventures on \"Code Is Cheap. Authority Isn't.\" | Hashnode"
description: "The shift you describe, from writing code to granting authority, matches what I see in client work. Code got cheap, but someone still has to say what the system"
url: "https://hashnode.com/posts/code-is-cheap-authority-isn-t/6ad54358d75f37b1b40b3b8d/comment/6ad5818839cde4bbff59bf86"
---

[Discussion](https://hashnode.com/posts/code-is-cheap-authority-isn-t/6ad54358d75f37b1b40b3b8d)

Comment [Code Is Cheap. Authority Isn't.](https://hashnode.com/posts/code-is-cheap-authority-isn-t/6ad54358d75f37b1b40b3b8d)

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

[Oct 19](https://hashnode.com/posts/code-is-cheap-authority-isn-t/6ad54358d75f37b1b40b3b8d/comment/6ad5818839cde4bbff59bf86)

The shift you describe, from writing code to granting authority, matches what I see in client work. Code got cheap, but someone still has to say what the system is allowed to do and who answers for it when it does the wrong thing.

Abhinav's question in the replies is the right one: if evidence is the scarce resource, the agent should not also write the rubric. One answer is to fix the acceptance criteria before the work starts and keep them out of the agent's reach. The human writes what done means, the agent produces evidence against it, and review becomes a comparison rather than a reading of whatever the agent chose to show.

That also makes authority easier to grant in small pieces: one clearly scoped task, one written finish line, one person accountable for the sign-off. Who owns the acceptance criteria when the system of agents spans several teams?

[Arunima Chaudhuri](https://hashnode.com/@ArunimaChaudhuri)

[Nov 3](https://hashnode.com/posts/code-is-cheap-authority-isn-t/6ad54358d75f37b1b40b3b8d/comment/6ad5818839cde4bbff59bf86#reply-6ae98768efde647f3203fd37)

Thanks, this is a sharper version of the point than mine. “Review becomes a comparison rather than a reading” is the shift I was trying to describe.

On your question, my answer is that criteria should be owned at the boundary where an outcome becomes visible, not wherever the agents happen to run. Each team owns acceptance criteria for its own domain. The interfaces between teams get their own contract, owned by whoever consumes it, because they’re the ones who get hurt when it breaks. Invariants that span the whole system (data ownership, tenancy, money) need one named owner, usually a tech lead or platform function.

The failure mode I’d watch for is ownership by committee. If three teams “jointly own” the criteria for a cross-team flow, nobody does, and the agents fill that gap with whatever they infer. One name per contract, even when the system spans ten teams.
