Repository Structure

All source code and artifacts of Linxira OS live under the Linxira-OS GitHub organization, organized into four groups: core repositories, first-party system tools, adopted upstream projects, and documentation. This page lists the responsibility of each repository and how they relate, from source to ISO delivery.

Core Repositories

Repositories that carry the distribution's overall architecture, package supply chain, and ISO artifacts:

Repository	Purpose
`linxira-os`	Project overview and governance: product architecture documents, repository governance manifest (`governance/repositories.yaml`), release notes (`releases/`), and support matrix
`packages`	Official package definitions and publishing pipeline: one pinned PKGBUILD per first-party package, with CI that builds in an isolated Arch container, signs, runs `repo-add`, and deploys to GitHub Pages
`linxira-packages`	The signed [linxira] package repository (x86_64), served by GitHub Pages; enable it after installing `linxira-keyring`
`linxira-iso-direct`	Current ISO build profile (Direct-Arch): complete offline installation closure, `linux` + `linux-lts` dual-kernel fallback, and Calamares installer configuration
`linxira-iso`	Deprecated legacy ISO build system (forked from CachyOS-Live-ISO), kept for historical reference only
`linxira-keys`	Private repository: GPG signing-key vault (double-layer encryption), accessible only to key holders; contains no passphrases or plaintext private keys

First-party System Tools

17 tool repositories maintained by Linxira (shelly is a source-built packaging exception):

Repository	Purpose
`linxira-welcome`	Plasma-native status and routing surface: shows system status and install completion, offers fixed tool entry points, never runs software transactions
`linxira-config-hub`	Configuration and diagnostics CLI (`linxira-config`): mirrors (Arch/npm/PyPI/AUR/Go/Flatpak), SSH, network, and headless switching
`linxira-update`	System updater: first-party continuation of the Cachy-Update/Arch-Update code line, with a system tray and pre/post-update checks
`linxira-package-center`	Curated application installer (Quick System Software Setup): catalog-bound planning, delegating the transaction to `linxira-components`
`linxira-component-manager`	Component/capability tree selector (Quick System Runtime Setup): nested capability tree with a plan/confirm/apply flow
`linxira-components`	Catalog-bound pacman transaction backend: creates deterministic plans, confirms them, applies a single root-only pacman transaction, and persists receipts
`linxira-completion-agent`	First-online completion agent: presents software and operations deferred by the installer receipt
`linxira-gaming-manager`	Gaming library and compatibility workspace: Steam library discovery, fixed-argument launching, restic encrypted backups
`linxira-hwd-detector`	Read-only hardware detection derivative of CHWD 1.23.0 (Rust): emits a versioned JSON hardware report
`linxira-hardware-driver-manager`	Hardware and driver manager: read-only reports and fixed-policy plans, with no privileged apply backend
`linxira-kernel-manager`	Read-only kernel and boot reporting: `linux` / `linux-lts` support matrix, GRUB entries, and DKMS state
`linxira-recovery-diagnostics`	Recovery diagnostics: Btrfs/Timeshift/boot/keyring readiness reports and a privacy-filtered support bundle
`linxira-catalog`	Canonical, versioned software component metadata (Catalog v2/v3): applications, components, presets, and offline policy
`linxira-artwork`	Official brand assets: logos, wallpapers, icons, and welcome banners; brand assets retain all rights
`linxira-hooks`	ALPM/Pacman hooks and helper scripts: os-release branding, reboot-required marker, and initramfs regeneration
`linxira-keyring`	Signing keyring package (trusted release key): imports and locally trusts the Linxira release key on install
`shelly`	Graphical package manager (GPL-3.0, source-built from a pinned upstream commit as a packaging exception): manages Arch/AUR/Flatpak/AppImage packages

Adopted Upstream

Upstream projects adopted as forks or re-packages, retaining upstream licenses and attribution:

Repository	Purpose
`CachyOS-Welcome`	Rebase-history candidate of CachyOS Welcome (Rust); superseded by first-party `linxira-welcome`, kept for archival reference
`CachyOS-Settings`	CachyOS system performance and optimization configuration (localized as Linxira-Settings with Linxira branding)
`cachyos-plymouth-theme`	Plymouth boot theme (Jimmac spinner over an ACPI BGRT background, rebranded for Linxira, GPL-3.0)
`cachyos-kde-settings`	KDE desktop settings (localized as linxira-kde-settings, GPL-1.0)
`cachyos-fish-config`	fish shell configuration
`cachyos-zsh-config`	zsh configuration
`cachyos-calamares`	Calamares installer configuration (settings and branding modules)
`cachyos-wallpapers`	Wallpaper collection
`cachyos-hypr-noctalia`	Hyprland + Noctalia compositor configuration
`cachyos-niri-noctalia`	Niri + Noctalia compositor configuration
`cachyos-mangowc-dms`	MangoHud + DMS gaming performance monitoring settings
`chwd`	CHWD hardware detection and driver configuration tool (upstream of `linxira-hwd-detector`, version 1.23.0)
`rate-mirrors`	Fast mirror ranking tool (Rust): finds the fastest mirrors in about 30 seconds
`calamares`	Installer framework: built from the official upstream 3.3.14 release archive (not the CachyOS fork)

Documentation

Repository	Purpose
`linxira-wiki`	Official wiki (MkDocs Material): documents only Linxira-specific features
`Linxira-OS.github.io`	Official website repository (this site)

How the Repositories Relate

The main pipeline from source to the ISO:

packages (PKGBUILDs + CI)
   │  build in an isolated Arch container → sign with the signing subkey → repo-add
   ▼
linxira-packages (signed [linxira] repository, hosted on GitHub Pages)
   │  scripts/fetch-linxira-packages.sh fetches the 16 first-party packages
   ▼
linxira-iso-direct → build-direct-iso.sh → ISO
   │  offline closure: Arch mirrors → build cache → /opt/linxira/offline-repo
   ▼
Calamares installer → pacstrap, fully offline install

The signing chain:

linxira-keys (private, double-layer encrypted vault for signing keys)
   │  the linxira-keyring package ships the public key and trusts it on install
   ▼
enable the signed [linxira] repository (SigLevel = Required DatabaseOptional)

Application selection and installation data flow: linxira-catalog provides the canonical catalog → linxira-package-center / linxira-component-manager build catalog-bound selection plans → linxira-components applies a single root-only pacman transaction and persists receipts. The ISO build, the installer, and every manager share the same catalog and package identities; the packages publishing pipeline is enabled only when the signing Secrets (LINXIRA_GPG_PRIVATE_KEY / LINXIRA_GPG_FINGERPRINT) are configured.