Constrained Adaptability
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.
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.
Solution
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).
When to use
- Never as a stand-alone state. Cite when reviewing claims of 'autonomous adaptation'.
- Surface in production designs to ensure escalation paths exist.
- Use as a capability-mapping anchor: document the agent's boundaries explicitly.
Open the full interactive page →
Diagram, neighbourhood map, code examples, related patterns and full provenance.