79d73cd623
All checks were successful
Check / eval (push) Successful in 3m47s
Add docs/OMARCHY.md for users coming from Omarchy (VISION § F). Leads with the one real difference — imperative dotfiles vs a declarative flake built via the menu, with rollback through NixOS generations — then maps the deltas: install (ISO/nomarchy-install or MIGRATION.md), a familiar keybindings table, theming (SUPER+T / nomarchy-theme-sync), installing software (home.packages / nix shell, no AUR), and update+rollback (nomarchy-pull/-rebuild/-home, boot-menu generations, nomarchy-doctor). Registered in docs/README.md; VISION § F marked shipped. The Nomarchy side is grounded in the code: keybindings pulled from keybinds.nix, and every cited command (7), the nsearch alias, and the named theme slugs (gruvbox/rose-pine/nord) verified to exist. Omarchy-side claims kept to known facts (Arch, dotfiles, pacman/AUR). Verification: V0 (docs-only); commands/slugs/binds checked against the tree. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.8 KiB
1.8 KiB
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 |
| 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 |
|---|---|
| ../agent/README.md | Executable agent loop state: BACKLOG, LOOP, MEMORY, … |
| ../CLAUDE.md | Agent entry point (any harness that reads it) |
| ../.claude/ | Claude Code 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 § ….