Project Alloy

An opinionated tiling user layer for Fedora Silverblue.

Project Alloy is to Silverblue what Omarchy is to Arch: a curated, beautifully-defaulted, keyboard-driven environment that fuses an immutable base, a Wayland tiling compositor, an opinionated app/tool stack, and a project-authored design system into one coherent system. An alloy is stronger than its component metals.

Short form for slugs, CLI binaries, package names, file extensions: alloy.

Status

Pre-v0. The docs are the project. Code follows.

License

MIT. Copyright (c) 2026 Make Creative, LLC. See LICENSE.

The design system it renders through, alloy_tui, is MIT in its own repo and consumed from crates.io.

Docs

The manual is for people who run Alloy: building an image, installing, the keybindings, how software gets installed, how to roll back, troubleshooting. Everything below it is design rationale, written for whoever works on Alloy.

• docs/MANIFESTO.md — what Alloy is, who it’s for, the thesis.
• docs/STACK.md — every pick (base, compositor, bar, lock, launcher, notifications, screenshot, file manager) with reasoning and what was rejected.
• docs/COMPONENT-LIBRARY.md — alloy_tui crate idioms and how themes reach the widgets.
• docs/RESEARCH-IMMEDIATE-MODE-DESIGN.md — late-term research sketch: what does Figma look like for immediate-mode UI? How do designers and engineers collaborate without designers writing Rust?
• docs/DESIGN-LANGUAGE.md — tinted-greyscale chrome, color reserved for information.
• docs/CONSOLE.md — Alloy Console: the ratatui unified control surface (alloy net, alloy audio, alloy mesh, alloy settings and the alloy config <path> schema-driven editor all shipped). Replaces the “graphical settings app” question.
• docs/CONTINUITY.md — a mesh VPN and file sync as base-image citizens: an Alloy install should be rejoinable, not just installable.
• docs/SHELL.md — Nushell as the login shell; bash unchanged as /bin/sh and /bin/bash. Architecture, interop rules, accepted costs.
• docs/HARDWARE-FW12.md — Framework Laptop 12 as the first hardware target: 2-in-1 stance, touch/tablet/rotation/OSK/fingerprint decisions.
• docs/HARDWARE-FW13.md — Framework Laptop 13 (AMD Ryzen AI 300) as the second target: measured panel, the 1.75x seed, AMD graphics, what is still unverified.
• docs/MIGRATION-FW13.md — cutover runbook for moving fw13 off Pop!_OS: phase order, the disk decision, the build-host role it has to keep playing, and the way back.
• docs/IMAGE.md — Image composition: bootc + Containerfile, source on makenot.work, built locally and natively. No image is published anywhere; you build your own.
• docs/todo.md — open questions and next steps.