XIV · Anti-PatternsAnti-pattern✕

Constrained Adaptability

also known as Recalculate-Within-Boundaries Limit, GPS-Reroute Limitation

Agents recalculate within declared tools and rules like a GPS rerouting, but cannot creatively transcend those boundaries to invent new approaches the way humans do.

Context

The team observes the agent successfully adapting to disruptions — switching to backup tools, rerouting around outages, retrying with alternative parameters. They mistake this for genuine adaptability. When a disruption demands a creative workaround not pre-programmed (manual fallback, novel tool combination, challenging the original constraints), the agent fails.

Problem

Conflating Constrained Adaptability with genuine adaptability leads to over-trusting agents in novel situations. The team assumes 'the agent handled the API outage, so it'll handle the system migration too'. It won't — the API outage was within boundaries; the system migration requires inventing.

Forces

  • Constrained adaptability looks genuinely adaptive on demo-day.
  • Novel situations only surface in production at scale.
  • Distinguishing 'within-boundary' from 'beyond-boundary' adaptability requires the team to articulate the boundaries.

Example

A healthcare document-processing agent handles a cloud storage outage by switching to local backup — within-boundary adaptation, ships as a success story. Two months later a vendor system migration requires a temporary manual workflow the agent has not seen. The agent fails silently — keeps trying its programmed alternatives, none of which apply. A human team would have invented a phone-and-spreadsheet workaround. The agent could not.

Diagram

Solution

Therefore:

Acknowledge Constrained Adaptability as the operational character of current agents. Pair with: tool-resilience-framework (within-boundary fallback design), human-in-the-loop (beyond-boundary escalation), agentic-ai-progression-framework (level-rating sets expectations), capability-mapping (documents what the agent can/can't do).

What this pattern forbids. No useful constraint; the missing constraint is explicit boundary articulation and escalation-path design.

And the patterns that stand alongside it, or against it —

  • complementsHuman-in-the-Loop★★— Require explicit human approval at defined points before the agent performs an action.
  • complementsAgentic Skill Atrophy✕— Anti-pattern: let agents take over routine architectural and debugging decisions in code until developers no longer form the implicit knowledge that lets them review the agent's output or recover when it fails.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

References

Provenance