Decisões não desaparecem quando ficam antigas.

Felunyx is based directly on Arch Linux.

Felunyx uses `systemd`.

Felunyx is a rolling-release distribution.

The Felunyx repository has priority over Arch repositories, but contains only justified native, patched, adapted, or curated packages.

Linux Zen is the default kernel and Linux LTS is installed as a fallback.

Automatic installations use Btrfs with separated system and home scopes.

System restoration preserves home by default. Restoring home first creates a safety snapshot.

Felunyx ships one ISO with a deeply customized Calamares installer.

GRUB is recommended by default; Limine is an official alternative; exactly one is installed.

One graphical profile is selected during installation.

KDE Plasma is the first reference desktop and initial implementation target.

XFCE and Hyprland are official profiles added after the shared platform stabilizes.

The native Felunyx Desktop is not on the critical path for the first usable distribution release.

All official profiles share Felunyx services, Central, Settings, recovery, design tokens, and session concepts.

Official functionality must be available through a high-quality GUI. Configuration files are optional advanced interfaces, not requirements.

GUI and CLI use the same backend and expose the same transaction evidence.

Configuration inheritance is `Global → Monitor → Workspace → Set → Application`.

The GUI displays configuration provenance and uses “Restore inherited value.”

The official native session is Wayland-only, with XWayland started on demand for compatibility.

The compositor is written in Rust on Smithay. Superseded by D-105 and D-106: Rust + Smithay remains the preferred technology lineage, but Felunyx no longer assumes the compositor should be assembled directly from bare Smithay building blocks.

Shell and graphical system applications use Qt 6/QML.

QML owns presentation; Rust owns state, validation, policy, and privileged behavior.

Compositor, shell, Central, Settings, greeter, and services are separate failure domains.

D-Bus is used for typed services, standard portals for sandbox integration, and Wayland protocols for compositor-specific behavior.

A shared `Felunyx.UI` module defines the visual system.

Each workspace has exactly one primary mode: Floating, Snap, Tiling, Rolling, or Monocle.

Stacking is transversal and compatible with every primary mode.

Mode changes preview the whole workspace and require explicit application.

Floating is the first-use default.

Smart Tiling preserves a stable main area when focus changes. A new main window is explicitly promoted.

Rolling defaults to horizontal on landscape monitors and vertical on portrait monitors.

A new window added to a stack does not steal focus.

Dragging a tab out reinserts it according to the workspace’s primary mode.

One-level session-temporary layout undo may be enabled, but is disabled by default.

Direct mode shortcuts exist but are disabled by default and fully remappable.

Workspaces are dynamic and independent per monitor.

One empty trailing workspace is maintained. Empty intermediate workspaces disappear.

Naming a workspace does not pin it. Pinning is explicit.

Overview uses abstract layout diagrams rather than live thumbnails by default.

Workspaces from a disconnected monitor move temporarily to the primary display while retaining source identity.

Reconnecting a known monitor asks before restoration by default; an automatic per-monitor policy is available.

Workspace naming suggestions are local, optional, and never applied automatically.

Ordinary application rules organize windows after launch; they never launch applications.

Sets may launch applications and restore workspaces, layouts, documents, projects, and tabs.

Approved rules may create missing destination workspaces without asking again.

A Set previews its effects and reuses already-open applications where possible.

Leaving a Set restores temporary configuration and never terminates applications without confirmation.

Session restoration prefers exact application state when the application supports it.

Sensitive and private application contexts are excluded from restoration by default.

Login session restoration supports Ask, Automatic, and Never policies.

The bottom bar behaves as an authored modern taskbar, not a generic panel.

Intelligent autohide is the default and reveals the bar progressively near the screen edge.

The bar uses restrained frosted glass, fine noise, subtle border, and adaptive opacity.

Tray items are collapsed by default; quick controls and notifications are separate panels.

Notification popups appear above the lower-right bar area, with at most three visible.

Dismissed notifications do not enter a hidden permanent history.

Only Felunyx or the user may pin a notification. Applications cannot self-pin.

The clock shows time above date and follows locale unless overridden.

The launcher is traditional and compact, but must not visually copy the Windows Start menu.

Launcher home shows separate Fixed and Recent application grids; files appear only in search.

“All applications” is a separate launcher view.

The default desktop has no icons; icons, folders, and widgets remain optional.

Window controls stay on the right with a thin, integrated titlebar.

Default source priority is Felunyx → Arch → curated AUR → Flatpak → Nix.

The user may override a source recommendation and sees the reason for the default.

AUR updates join the same user-facing transaction while retaining a distinct build and verification stage.

AUR packages are built, checked, and signed by Felunyx infrastructure where available; clients validate signatures and metadata freshness.

Failed verification blocks the affected version in the managed layer.

Full system updates always show the plan and require confirmation.

The CLI requires an explicit `--assume-yes`-style flag for non-interactive confirmation.

Risk classification combines curated critical packages, dependency impact, and special rules.

Risk levels are Low, Moderate, and High.

Automatic snapshot modes are Smart, Always, and Never; Smart is the default.

Reboot-pending state identifies the component that requires restart and persists until the new state is validated.

No background repair process silently changes the system.

Recovery categories are Boot, System, Storage, Packages, and Diagnostics.

Recovery follows Analysis → Proposal → Confirmation → Result.

Proposed recovery commands are displayed directly before execution.

Boot failure asks the user among LTS, snapshot, repair, recovery, and power options; it does not auto-select by timeout.

Recovery provides a full terminal.

Networking is available by default; remote access and report submission remain off without consent.

Recovery retains Felunyx identity but prioritizes contrast, stability, and low graphical complexity.

The brand is “Felunyx”; “Felunyx OS” is the formal distribution name.

The visual foundation is graphite with restrained blue/violet accents and a subtle ethereal edge.

The lynx mark balances geometric minimalism with expressive stylization. Superseded by D-107: the lynx remains part of Felunyx identity as a mascot and secondary emblem, but no longer owns the primary brand-mark role.

StartAllBack is an ergonomic launcher/taskbar reference only, never a direct visual reference.

The project begins as a phased monorepo. Components split into separate repositories only when ownership, release cadence, or access requirements justify it.

The repository is licensed under GPL-3.0 unless a component states another compatible license.

Work pauses at every phase boundary for review.

Disk encryption is prominently recommended in automatic installation but remains an explicit user choice.

A host firewall is enabled with a conservative desktop policy.

Telemetry is absent by default; any future diagnostics program must be opt-in, inspectable, and separately approved.

Secure Boot support is a release objective, but is not advertised until installation, update, kernel fallback, and recovery paths are automated and tested.

The first internal ISO implements KDE only; XFCE and Hyprland enter after platform contracts stabilize.

The package CLI placeholder is `fel`; the final command name is chosen before its public interface freezes.

Exact Btrfs subvolume names are chosen in Phase 2 when the image and installer tests exist.

Exact Rust crate, D-Bus interface, and database names are chosen in the owning component specifications.

Stable/testing/development channel topology is finalized in Phase 7 after build and repository operating costs are measured.

The native desktop’s first public channel is chosen only after nested, TTY, multi-monitor, XWayland, portal, input-method, and tablet prototypes pass.

Exact default applications are selected during the KDE reference phase using integration, accessibility, maintenance, and source-policy criteria.

Set activation preserves the current arrangement and opens or reuses additional Set workspaces by default; replacing the current arrangement is an explicit preview choice.

Validation is divided into Remote (R), Virtual (V), and Hardware (H) gates; every completion claim names the strongest gate actually passed.

A phase blocked only by an unavailable V or H gate may permit isolated preparatory work for the next phase without marking either phase complete.

Missing physical access is mitigated through primary-source review, static validation, reference comparison, and explicit pending V/H tests; documentation conformity is never reported as runtime proof.

The native Felunyx compositor derives from a mature Wayland compositor foundation rather than rebuilding low-level compositor infrastructure unnecessarily. Low-level backend and protocol work stays upstream-derived where sustainable; Felunyx owns workspace, layout, stack, focus, restoration, rules, Work Environment integration, and shell-facing policy.

`pop-os/cosmic-comp` is the preferred first Phase 8 compositor foundation because it preserves the Rust + Smithay lineage. Long-term adoption requires explicit decoupling from unnecessary COSMIC desktop services, compatibility validation, a replaceable Qt/QML shell boundary, and a sustainable upstream synchronization delta.

The primary Felunyx brand mark is a simple, recognizable stylized `F` suitable for small and large surfaces. The lynx remains the project mascot and may appear as a secondary emblem or expressive identity asset, but it is not the primary logo.

Felunyx does not prevent users from installing other desktop environments or window managers, but only official profiles receive Felunyx-validated integration, configuration, compatibility guarantees, and project support. Unofficial environments may work, but are outside that validation boundary.