Bernardo Magri
4a0b76cc97
All checks were successful
Check / eval (push) Successful in 3m43s
Yarara is nixpkgs' release name. Carrying it in PRETTY_NAME told users something true about our upstream and nothing about our product, in the one string every fetch tool and greeter reads. Upstream hardcodes the codename into VERSION, PRETTY_NAME and VERSION_CODENAME (misc/version.nix) with no switch, and `system.nixos.codeName = ""` is the wrong lever — it renders "26.05 ()". So the assembled strings are overridden through the merge hooks upstream does provide (extraOSReleaseArgs / extraLSBReleaseArgs), which is already where our project URLs live. lsb-release gets the same treatment; it carried the codename in three fields of its own. Empty VERSION_CODENAME/DISTRIB_CODENAME is deliberate: `//` cannot remove a key, os-release(5) makes every field optional, and the file already ships ANSI_COLOR="" and IMAGE_ID="". nixos-version still prints "(Yarara)" and is left alone on purpose: that command reports which nixpkgs the system was built from — the one question the codename actually answers. Reaching it would mean patching a nixpkgs script for no gain. Verified on the built system: PRETTY_NAME="Nomarchy 26.05", VERSION="26.05", VERSION_ID="26.05"; lsb DISTRIB_DESCRIPTION="Nomarchy 26.05", LSB_VERSION="26.05". fastfetch's os line reads PRETTY_NAME, so it follows. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Docs map
Where human and agent documentation lives. Do not invent a third tree for the same facts.
| Path | Audience | Role |
|---|---|---|
| ../README.md | Everyone | What Nomarchy is, install, options tables |
| REQUIREMENTS.md | Users + agents | Minimum system requirements (GPU/OpenGL, RAM, disk, UEFI) |
| VISION.md | Maintainers + agents | Product north star toward v1.0 and beyond — themes, not a task queue |
| ROADMAP.md | Maintainers + agents | Design/decision records + shipped log (historical ✓) |
| HARDWARE.md | Users + agents | Firmware, profiles, drivers, unsupported machines |
| TESTING.md | Maintainers + agents | Verification ladder, honesty rule, ISO/VM recipes |
| RECOVERY.md | Users | Broken theme/desktop/boot → undo |
| OVERRIDES.md | Users | Downstream Nix overrides |
| MIGRATION.md | Users | Existing NixOS → Nomarchy without reinstall |
| OMARCHY.md | Users | Coming from Omarchy — bindings/theme/install/config map |
Related (not under docs/)
| Path | Role |
|---|---|
| ../AGENTS.md | Agent entry point, any vendor/harness (CLAUDE.md symlinks to it) |
| ../agent/README.md | Agent instructions + executable loop state: BACKLOG, LOOP, VERIFICATION, … |
| ../.claude/ | Claude Code adapter only: permissions + subagent defs |
How work flows
VISION (what we want the product to feel like)
│
▼ human triages slices into…
BACKLOG (what's next, ordered — agents execute only this)
│
▼ lasting design notes after ship →
ROADMAP ✓ entries
Agents do not implement directly from VISION or ROADMAP. They take
the top actionable item in agent/BACKLOG.md (see agent/LOOP.md).
They may append PROPOSED pitches that reference VISION § … or
ROADMAP § ….