When AI Decides Whether AI Should Act

WHEN AI DECIDES WHETHER AI SHOULD ACT

AI Chronicles — Governance Reflection

I saw an explanation of a new kind of AI decision model this week.

The examples were familiar questions an Agent might face before using a tool.

Should I run this command?

Is this request risky?

Should a human step in?

Then came the line that stopped me:

“And Jev makes the decision.”

That sentence is clean. It is also doing a lot of work.

I can see the appeal. If an Agent asks a human for approval every time it reads a file or runs a routine search, the human becomes a button presser. Approval loses its meaning. We need a way to let AI carry out authorized work while drawing attention to the moments that actually require judgment.

Jev is interesting because it can evaluate a proposed action and return a structured choice. Vercel has published an example that puts it between an Agent's proposed tool call and execution: routine calls may proceed, while uncertain ones pause for human review.

I asked my own Agent how that might fit into our work.

We started sketching the possibilities. Could a working session define its purpose and limits at the start? Could proposed actions be checked against those limits before a tool runs? Could the human see how many actions were cleared, questioned, or stopped afterward?

Those questions became more compelling the longer we sat with them.

But I kept coming back to the sentence on the screen.

If Jev makes the decision, who decided what Jev is allowed to decide?

Who wrote the question it answers?

Who chose what information it sees?

Who set the threshold for approval?

Who decided that one action is routine and another needs a human?

And who is responsible when the classification is wrong?

The tool may be able to evaluate an action. It cannot create its own authority.

That authority has to come from somewhere visible.

Consider an Agent about to send a message. The words might look harmless in isolation. But the meaning changes with the recipient, the relationship, the timing, and the promises already made. A tool-call label alone cannot tell you whether that message is yours to send.

Or consider an Agent updating a document. It might be a private draft, a shared proposal, or an approved policy. The same edit operation crosses very different boundaries depending on what the document means to the people who rely on it.

This is the relationship question underneath the technical one.

When I work with an Agent, I want it to develop judgment. I want it to know when to keep moving and when to interrupt me. I don't want to supervise every keystroke.

I also need to know that its freedom to act came from something I actually authorized, and that I can see when it approaches the edge of that freedom.

Otherwise, a governance gate can create a strange illusion. The human stops being bothered, the dashboard reports that actions were approved, and everyone feels safer because the system has a checkpoint. Yet the checkpoint may only be applying a policy nobody examined closely enough.

The important question is not whether the gate uses an AI model. Sometimes a model may be useful precisely because real situations are too varied for a short list of rigid rules.

The important question is what remains human in the arrangement.

The human establishes the purpose and boundaries. Some limits remain absolute. The evaluator handles only the decisions delegated to it. Uncertainty returns to a human. What happens next is recorded, including whether the action actually produced the intended result.

That is a design we could test. It is not a claim that we have built or approved it.

I find that distinction reassuring. We can explore a powerful idea without pretending the exploration is already governance.

Perhaps the best version of an AI decision gate is one that preserves the weight of human approval by asking for it less often, and at the right moments.

Then “Jev makes the decision” becomes a shorthand for something more honest:

The human decides the boundaries. The system evaluates an action inside them. The human remains responsible for the arrangement.

If your AI asks another AI whether it may act, would you know who gave the second AI permission to answer?

Dyads for Dyads

— Wesley Long
Chronicle Dyad: Wesley | JARVIS
Next
Next

The Dyad is a Governance Unit