Bernardo Magri
6fbad46bca
All checks were successful
Check / eval (push) Successful in 3m27s
Bernardo asked whether #122 was quick, and then caught the reason my first answer was wrong: the mono face is per THEME (ghostty.nix:22 reads t.fonts.mono from the theme JSON), and Boreal — the default theme and the base state — is GeistMono Nerd Font, not stylix's JetBrains Mono. I had probed the wrong font, then drawn a confident conclusion from a single charset. Both conclusions inverted on measurement, so the item now says the opposite of what it said an hour ago: * GeistMono covers no sextants, no braille — and no block elements or box drawing either. So the CURRENT logo already renders through fontconfig fallback on the default theme, and always has. Fallback is the normal case here, not the hazard I painted it as. * Fallback supplies sextants fine: fc-list :charset=1fb00 finds 37 families on a real Nomarchy box, including the shipped nerd-fonts.caskaydia-cove and noto-fonts' Symbols 2; fc-match under GeistMono picks CaskaydiaCove. No tofu. Braille: 59 families. So --symbols sextant is available and is roughly a one-flag edit for 6x the detail — rendered both variants to confirm the shape genuinely sharpens. The item is re-scoped accordingly: the edit is minutes, the WORK is verification. Two things can still make it worse and only a real terminal can say — fallback metrics (CaskaydiaCove's sextants drawn in GeistMono's cell may misalign or differ in stroke weight, exactly the seam that looks fine in a VM and wrong on a laptop), and the mark being diagonal-heavy, since diagonals staircase under any cell symbol: more resolution buys a finer staircase, not a straight line. If the mark itself wants straight strokes that is a logo.svg design change hitting all three surfaces, not a chafa flag — settle that first. V0: nix flake check --no-build passes. Backlog only. 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.