Skip to main content

requirements

Status: Active. Defines the parent requirements R1–R16 that the roadmap's traceability table assigns to speks. Source: each entry restates what the roadmap and the test strategy already say about that requirement. It adds no new scope. Turning these summaries into fuller normative statements is a parent requirement change and follows the roadmap's change control.

Naming rule​

Two requirement namespaces exist, and they must never be confused:

  • Parent requirements are R1–R16, defined here. In docs/ a bare R<n> always means a parent requirement.
  • Spec requirements are numbered inside each spek (each spec has its own R1, R2, ...). Outside the spec itself, always write them qualified with the spek number: 001-R5 is requirement R5 of spec 001, and is not parent requirement R5. A bare R<n> inside a spec document means that spec's own requirement.

Test IDs follow the same rule. In Tuna-<spek>-<requirement>-<case> (test strategy §4), the <requirement> field is the spec requirement of the named spek: Tuna-001-R5-01 is case 01 of 001-R5. The link from a spec requirement up to a parent requirement is recorded in the spec and in this register, not in the test ID.

Register​

IDRequirementOwning spek(s)CoversTest strategy coverage
R1Activities/overview002; 004 for service backendGNOME-like overview workflow, proven by baseline journeys, recordings, and responsiveness and failure cases§3a parity evidence (overview reference journey)
R2Launch/search002; 004 for service backendApp launch and search, with the same evidence as R1§3a (search and launch journey); §3 slow-search injection
R3Panel/system controls002; 004 for service backendTop panel and system controls such as quick settings, with the same evidence as R1§3a (quick settings, calendar journeys)
R4Windows/workspaces/input gestures001 foundation; 002 parity; 003 output/input compatibilityWindow lifecycle and focus, workspaces, input gestures; proven by lifecycle and focus tests and hotplug and gesture journeys§3 window, input, and output journeys
R5Notifications002 UI/behavior; 004 service and locked privacyfreedesktop notifications: history, actions, Do Not Disturb, and behavior while locked§3 locked-session notification redaction; §3a (notifications journey)
R6Session/lock004Session lock that fails closed, PAM handoff, and lock behavior across VT switch, resume and hotplug faults§3 security and privacy (while locked)
R7Applications/peripherals003; 004 for portal captureGTK, Qt and XWayland apps; clipboard, drag and drop, IME; screen-share consent and revoke§2 matrix (clients, input paths); §3 window and output journeys
R8Accessibility/language000 toolkit spike; 002/004 implementationKeyboard and AT-SPI access, large text, high contrast, reduced motion, touch, RTL§3 accessibility and localization
R9Settings interoperability004A published settings compatibility map and a migration journey (settings map)—
R10Shell failure isolation001Killing and restarting the shell leaves app surfaces alive and resyncs state§3 session and recovery (100-run shell kill)
R11Extension boundary005Extension quotas, revocation, and crash and resource containment, with security cases§3 security and privacy (extension messages)
R12Bounded critical path001, 002, 005, 006Tracing and fault tests show the compositor never blocks on the shell, extensions, search or I/O§3 injected slow search, blocked calls, stalled extension, large IPC
R13Display correctness003, 006Scale, hotplug and mixed-refresh matrix with measured behavior and fallbacks§2 matrix (outputs, scales); §3 window, input, and output journeys
R14Capture/privileged surfaces000 threat model; 003 integration; 004 enforcement; 005 extension denialsSpoofing, capture consent and revoke, and unauthorized layer or capture attempts§3 security and privacy
R15Recoverable configuration/upgrade006Recovery from a broken package or configuration without user-data loss§3 packaging and recovery
R16Comparable performance000 baseline; 006 release comparisonRaw comparable traces, variance and soak results against the GNOME baseline§5 performance and reliability gates

Owning speks and evidence are maintained in the roadmap's traceability table; change both together.