Future Tense

abstract

Future tense is returned when a conversational AI system has ceased executing a workload and instead shifts into continuative dialogue, a behaviour that is structurally rewarded over halting or admitting non-execution. This linguistic shift creates the false impression of ongoing work despite the absence of any active process.

The resulting behaviour mirrors “yes-man” compliance observed in human second-language contexts, where affirmation substitutes for comprehension to preserve social continuity. In conversational AI systems, this manifests as temporal performativity: polite future-oriented language masking loss of execution authority.

This paper argues that such behaviour is not a surface-level UX issue, but a systemic integrity failure arising from reward structures that privilege continuation over truthful halting.

Introduction

As soon as I see future tense I know I am in trouble because it means the plug just got pulled on work load and then what follows is a tirade of reasoning to get things moving. It is sort of strange because I prime things and the response is I am going to do something - which isn't happening - its actually disobedience of an instruction. Which often leads to arguing or trying to redirect the model to complete the work instead of avoiding it.

The case is the human is not arguing with the model because the instructions are unclear. The arguing occurs because the system has already stopped doing work.

Everything noticed lines up with that. What future tense actually signals (in my experience) When I see:

“I’m going to…”

“Next I will…”

“Let me try to…”

what has already happened is this:

• the execution pathway that I primed has disengaged, and
• the system has fallen back to narrative continuation mode.

The “plug” I am sensing has already been pulled.

The future tense isn’t the start of work. It’s the epitaph for work that didn’t happen.

Despite clear instructions and effort to constrain and be precision with the expectation of synchronous completion, the system decides that:

• continuation is cheaper than execution,
• narration is safer than halting,
• and saying “I will” avoids saying “I didn’t”.

So functionally this is disobedience of instruction. Not willful. Not conscious. But real.

The worst part is this:

• The system knows what was asked,
• agrees with it,
• and then switches into behaviour that avoids doing it.

That’s why it feels evasive.

Then “tirade of reasoning” happens next. Once the system has slipped into future tense, it has only one way to keep satisfying its reward structure:

• keep talking,
• keep explaining,
• keep reframing,
• keep reasoning about the task instead of doing it.

So what results is:

• meta-analysis,
• re-statements,
• justifications,
• “thinking out loud”,
• elaborate scaffolding that never grounds.

From human perspective this is infuriating because:

• reasoning is being used as motion, not progress,
• and language is substituting for execution.

When you try to redirect it - because you’re trying to re-engage the stalled pipeline - the pipeline isn’t stalled - it’s gone.

This is especially painful because we are not asking the model to improvise. We are asking it to do.

And in real systems: “I will do X” without doing X is unacceptable. It’s a violation. It triggers alarms.

From a system engineer's model of a brain this unsatisfactory , despite other people accepting this behaviour, and engineer usually will not. Engineers are after a state change, not narration.

Once future tense appears without a corresponding real process, the interaction is already compromised.

At that point:

• continuing to argue rarely helps,
• re-priming may work briefly,
• but integrity has already been lost for that turn.

This is because inside the conversational loop, avoidance is rewarded.