Bernardo Magri
121b91f69c
All checks were successful
Check / eval (push) Successful in 3m47s
Bernardo, and it is the right ask for this machine: a VT has one keymap and no per-device layouts, so settings.keyboard.devices (his external board remembered as `us`) does NOT apply at the passphrase box — it follows xkb.layout via console.useXkbConfig. Same structural gap as #114 (tuigreet), one step earlier in the boot, with worse stakes: three wrong tries on a disk you cannot read yet. Fedora's mechanism does not port, twice over: its label is ply_keymap_icon, a C widget in the two-step plugin (the script plugin has no keyboard API at all), and it is fed from XKBLAYOUT in /etc/vconsole.conf — which NixOS does not write. This box has only KEYMAP=<store path>, and plymouth's own trace says `XKBLAYOUT: (null)`. So bake it like the palette already is: @LAYOUT@ sed into nomarchy.script from config.nomarchy.keyboard.layout, drawn with Image.Text (already used by display_message_callback) inside display_password_callback. Label and console keymap then come from one option in one rebuild. Flagged for whoever takes it: keyboard.layout can be a comma list and the VT loads the FIRST — print that, or the label lies in exactly the case it exists for. Bundle with #137: it is one more sprite to reposition on canvas change, and tools/plymouth-preview.sh already renders ask-for-password — this very screen. 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.