Adaptive should still mean predictable
Context can simplify a task, but stable navigation and user control come first.
Use context that people can inspect
An explicit task selection is easier to understand than an invisible inference about a person. Begin with a user-selected context and make the selected state clear in text. Avoid collecting personal information when a direct choice is enough.
Preserve the map
Do not move a focused control or silently remove an action when context changes. Keep primary navigation stable, maintain keyboard order, and provide a route to the full action set. An adaptation should be reversible without requiring a page reload.
Evaluate more than clicks
A shorter path can still be harder to understand. Review whether actions have clear names, whether users can explain the current state, and whether the same task remains possible with a keyboard, screen reader, or enlarged text.
A design principle to test
This note proposes criteria for the context-aware interface concept. It does not report a user study or claim usability improvements. Those claims would require a defined protocol, appropriate participation, and recorded observations.