All checks were successful
Check / eval (push) Successful in 3m49s
#136 CLOSED: he confirms the incident was clamshell (laptop closed), so the gate already matched the evidence and only the words overclaimed. Swept: idle.nix's comment + its journal line (`dpms-off skipped: docked` → `clamshell (internal $m present but off)`), the ROADMAP entry, and #127's own text. Docked-with-lid-open still blanks and is now explicitly untested rather than implicitly covered. #127 gains the exact protocol he asked for — two tests, separated by risk: A) the mitigation holds (safe, unattended, journal line to grep); B) the decisive one, whether DPMS-off was ever the trigger, run by hand because the shipped mitigation would otherwise skip it. B self-recovers after 45s (dpms on + hyprctl reload — #142's hammer re-lights eDP) because this box has no sshd. All three outcomes are written down with what each implies, including "input wakes it" → revert the mitigation and #135 never exists. #130 decided: fix the contrast, we hold ourselves higher than GNOME — matching upstream is no defence at 2.7:1, under even the large-text floor. Recorded with the two candidate shapes and a preference for darkening our label over the user's accent, plus the note that check-theme-contrast.py covers palette pairings only, so it needs its own assertion or it rots exactly like #98. #143 decided: wait for rofi#2317, do not carry a patch — a patched rofi means every machine compiles rofi from source, on every lock bump, to fix a highlight. Now a watch, not work. #120 deferred to PROPOSED intact: the measurements stand, and the no-binary- cache gotcha probably makes cachix the real first step anyway. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Agent instructions + loop state
Everything an AI agent needs to work on Nomarchy, vendor-neutral and git-tracked. Protocol: LOOP.md. Entry point for every harness: repo-root AGENTS.md.
Instructions (how to work)
| File | Who writes | Role |
|---|---|---|
| LOOP.md | Human | One-iteration protocol (orient → pick → work → verify → commit → record) + the V0–V3 ladder |
| VERIFICATION.md | Human (agents propose) | Enforcement: preflight, honesty rules, visual protocol, hardware-blocked checks, reporting |
| DELEGATION.md | Human (agents propose) | Capability tiers, scout/runner roles, token economy, parallel fan-out |
| GOALS.md | Human (agents propose) | Pillars, quality bars, non-goals |
| CONVENTIONS.md | Human (agents propose) | How to write code/menu/state while shipping |
| THEME-DESIGN.md | Human (agents propose) | Theme/visual design instructions |
State (what's happening)
| File | Who writes | Role |
|---|---|---|
| BACKLOG.md | Both | Prioritized queue — only executable work list |
| JOURNAL.md | Agents | Append-only iteration log (read last 3–5 entries; older → JOURNAL-ARCHIVE.md) |
| MEMORY.md | Agents | Curated durable gotchas |
| HARDWARE-QUEUE.md | Agents append, human checks | On-hardware V3 tests only Bernardo can run |
Product / design docs (not a queue)
| File | Role |
|---|---|
| ../docs/VISION.md | v1.0 product themes — agents slice into BACKLOG PROPOSED |
| ../docs/ROADMAP.md | Design history + shipped log |
| ../docs/README.md | Full docs map |
Harness adapters (vendor-specific, thin)
Shared content never lives in an adapter — adapters only register/route into the files above, in whatever format their harness requires.
| Path | Harness | Role |
|---|---|---|
| ../AGENTS.md | any | Entry point (CLAUDE.md is a symlink to it) |
| ../.claude/settings.json | Claude Code | Tool permissions |
| ../.claude/agents/ | Claude Code | nomarchy-scout / nomarchy-runner role defs (contracts in DELEGATION.md) |
Do not put backlog items, vision text, or policy under an adapter directory — it is not shared with other agent runners.
Rules of thumb
- Execute from BACKLOG only (NOW → NEXT; never PROPOSED without human triage).
- Orient with GOALS + CONVENTIONS + MEMORY + last journal + BACKLOG; when the task is product-shaped, also read the relevant VISION §.
- Record lasting design in ROADMAP ✓ when something ships that future humans should know; delete the BACKLOG line.
- v1 branch is human-only — never advance from an agent session.