aboutsummaryrefslogtreecommitdiff
path: root/rigel/AGENTS.md
diff options
context:
space:
mode:
Diffstat (limited to 'rigel/AGENTS.md')
-rw-r--r--rigel/AGENTS.md41
1 files changed, 41 insertions, 0 deletions
diff --git a/rigel/AGENTS.md b/rigel/AGENTS.md
new file mode 100644
index 0000000..a285661
--- /dev/null
+++ b/rigel/AGENTS.md
@@ -0,0 +1,41 @@
+# rigel — machine overlay package
+
+Parent rules: `../AGENTS.md` (repo root). Machine-level context for the
+laptop itself lives in the rigel workspace (`~/git/rigel/AGENTS.md`);
+this file describes THIS package's contents and the stow mechanics.
+
+Deploy: `stow --adopt -t ~ rigel` after `stow --adopt -t ~ sway` (the
+shared package must land first).
+
+## Contents
+
+- `.config/sway/machines/rigel.conf` — rigel's machine overlay: outputs,
+ touchpad, session-stack autostart, lock/idle, power-profile bindings.
+ Included LAST by the shared sway config.
+- `.config/sway/session-daemons.sh` — per-session supervisor (pipewire,
+ mako, waybar, ppd-switch) instead of bare sway `exec`: on OpenRC/elogind,
+ sway-exec'ed daemons become orphans of dead sessions. Idempotent across
+ reloads; restart-on-crash for some daemons.
+- `.config/sway/fibonacci` — dwm-dwindle listener (POSIX sh + jq, no
+ python runtime). Keeps every new tiled window in the bottom-right
+ corner: finds the corner leaf, re-homes off-focus births beside it via
+ mark+move, and wraps the newborn alternately (`split toggle`) so the
+ pattern self-perpetuates. `--monitor` on the sway subscribe is required
+ — without it swaymsg exits after one event and births in the reconnect
+ gap get lost. Floating and tabbed/stacked containers are left alone.
+ flock-singleton per sway socket, so reloads don't stack duplicates; the
+ exec path must stay `/home/nicholas/.config/sway/fibonacci` (no .py)
+ because the machine conf execs it by that absolute path.
+- `.config/sway/ppd-switch.sh` — auto-switches power-profiles-daemon on
+ AC/battery transitions; its /proc comm matches its filename, which is
+ why the supervisor manages it by that exact name.
+- `.config/sway/veila-session-start.sh` — veila session wiring.
+
+## Rules
+
+- `machines/rigel.conf` never receives styling; the shared sway `config`
+ never receives rigel paths, outputs, or exec lines. Move a line between
+ the two only with a comment explaining which fact made it machine-level.
+- New machine coming in? Copy this package as `<newmachine>/`, reshape
+ `machines/<newmachine>.conf` for its hardware, and give it the same
+ script/AGENTS treatment.