jarvis-at-skic
3a2e19fc52
4.4 KiB
title, description
| title | description |
|---|---|
| 3DARCH-FT-12 — Discover and retain personal controls | Enable a user to learn the workplace controls, prevent movement controls from interfering with text/settings interaction, and retain mouse sensitivity across visits. |
Discover and retain personal controls
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|---|---|---|---|---|---|
3DARCH-FT-12 |
3DARCH-EP-2 — Secure Access and Personal Setup | IN_BACKLOG |
EXACT |
3D Architecture Wizzard team | No |
Description
Enable a user to learn the workplace controls, prevent movement controls from interfering with text/settings interaction, and retain mouse sensitivity across visits.
User or operator problem
Users need discoverable controls that do not interfere with typing and settings, with sensitivity retained across visits.
Expected value
Improves control discoverability and preserves a usable personal interaction setup.
Scope
Includes the controls guide, movement suppression during text/settings input, mouse-sensitivity adjustment, persistence, and save-failure feedback.
Exclusions
- Administrator access, account recovery, display-name editing, and unwired self-service logout are excluded.
Acceptance outcomes
- A visible controls guide explains supported keyboard actions.
- Typing or using settings does not trigger movement actions.
- Mouse sensitivity can be adjusted and restored in a later session.
- Save failures are surfaced rather than silently discarded.
Dependencies
Risks
- Settings persistence failures can leave the displayed sensitivity different from the retained value.
Human approval
Linas approved this Feature for documentation on 2026-09-02T10:40:43.220Z. It is not Approved for Solution and has no implementation approval.
Delivery status evidence
The Feature was separately registered at IN_BACKLOG as an accepted catalogue boundary. This records backlog retention, not design or delivery progress.
- Event: Catalogue registration
- Actor and authority: Linas — Human project team member
- Reason: The Feature catalogue was accepted for governed documentation and retained in the backlog.
- Status evidence
Architecture traceability
- Requirements: none derived.
- Readiness: Not started.
Architecture solution work must not begin until a separate human Approved for Solution decision is recorded.
Tasks
Review the Tasks group. No canonical implementation Tasks have been defined.
Original source
- Discord – Scope – Linas: original Feature request
- Discord – Scope – Linas: proceed with documented mapping
Legacy implementation evidence
The Feature boundary was mined from legacy revision c0ced47ecaf4426f47e5c2e4868677f7144b951a.