Principles
Adaptive should not mean unpredictable.
A principle is only useful if it changes how the product behaves. Each one below is paired with that behaviour, and with what the current prototype actually does.
Stable when you need it.
Your accepted workspace should not rearrange itself while you are using it. Adaptation happens when you ask for it, not in the middle of a task.
In practice
A significant layout change is shown as a preview first. You accept it or keep what you have, and you can undo it afterwards.
In the prototype today
Layout preview, accept and undo are implemented and covered by the end-to-end tests.
Clear about its limits.
Unsupported actions should stay unsupported, not become optimistic guesses. Knowing what Roscelin cannot do is as useful as knowing what it can.
In practice
An action the integration does not support, such as deleting a task, is shown as unavailable, with a way to open the item in the original app.
In the prototype today
Implemented. Requests for an action that is not in the integration’s list are refused, and that refusal is tested.
Designed for different people.
Simple, expert, keyboard-first and accessible interactions belong in the same product, not in separate editions.
In practice
Density, text size, contrast, reduced motion and wording are part of your profile, and every control is reachable from the keyboard.
In the prototype today
These settings and arrow-key navigation are implemented. A screen-reader pass has not been done yet.
Honest about outcomes.
An attempted action is not the same as a verified result. Roscelin should say what it knows, and say when it does not know.
In practice
A change is reported as done only after the app has been read again and shows the intended result. If that cannot be confirmed, the result is shown as unknown and is not sent again.
In the prototype today
Implemented and tested against Vikunja, including after the extension is interrupted mid-change. One known gap, the same-field race, is documented on the project status page.
You stay in control.
Roscelin should never become the only way to reach your work, and it should be easy to stop.
In practice
The original app is always one step away. A stop control halts all actions until you resume.
In the prototype today
An “open in original app” link, a stop button with a keyboard shortcut, a per-app pause and an activity log are implemented.