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)
Product / design docs (not a queue)
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.
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.