koru-libs

Start or re-enter an Arbiter-Driven Development (ADD) run. Use when you DON'T already know what to work on — to reorient and pick the highest-value next move and propel forward — or as `/arbiters <focus>` to seed a fuzzy direction. NOT the path for a task you can already name (just do that). This file is the SPINE: it holds the garden frame, the four hats, the one rigidity, the roles, and the Never list, then points you to one per-phase sibling file at a time (`walk.md` → `muse.md` → `scout.md` → `discriminate.md` → `commission.md` → `contest.md` → `judge.md` → `gardener.md`, plus the `arbiters-challenge` skill for the generative day and `scene.md` for doctrine). Read this top-to-bottom for the overview, then pick up exactly one phase from its own file. Fire when the user types /arbiters, says "get us started", "where were we", "kick off a run", or "what should we work on next".

Orientation map for the koru-libs project — what it is, how it builds/tests, where the source of truth and the canonical standard live, and the misconceptions that will bite an agent. Read this FIRST in any /arbiters walk, Scout, or Contestant run here. It is the EXISTING-scene instrument (fast clock, where you are); SCENE.md is the ideal scene (slow clock, where you're going). Points to tools; never duplicates them.

Tend the membrane memory corpus — an OKF concept store whose fragment evolution lives in the git log as lineage trailers. Fire when creating, evolving, merging, splitting, or CORRECTING durable memory/knowledge that lives as OKF files under git; when recording how a belief changed or was repudiated; or when tracing a concept's history through time. YOU are the evolver — there is no evolution engine and no LLM sidecar. NOT for transient notes, scratch, or code comments.

The challenge doctrine of Arbiter-Driven Development — generators you replay, catalogs that grow, families of challenges, chained pipelines. Fire whenever a challenge comes up in ANY form, not only when a generative day is named on the walk — running or replaying a standing challenge, creating a new one, tuning an existing brief, asking "should this be a challenge?", proposing meta-challenges, or reasoning about a challenge catalog or family. Also the routing target when `/arbiters` names a Generative day. If the conversation touches challenges and this skill is not loaded, that is the firing failure this skill exists to fix.

Start or re-enter an Arbiter-Driven Development (ADD) run. Use when you DON'T already know what to work on — to reorient and pick the highest-value next move and propel forward — or as `/arbiters <focus>` to seed a fuzzy direction. NOT the path for a task you can already name (just do that). This file is the SPINE: it holds the garden frame, the four hats, the one rigidity, the roles, and the Never list, then points you to one per-phase sibling file at a time (`walk.md` → `muse.md` → `scout.md` → `discriminate.md` → `commission.md` → `contest.md` → `judge.md` → `gardener.md`, plus the `arbiters-challenge` skill for the generative day and `scene.md` for doctrine). Read this top-to-bottom for the overview, then pick up exactly one phase from its own file. Fire when the user types /arbiters, says "get us started", "where were we", "kick off a run", or "what should we work on next".

Tend the membrane memory corpus — an OKF concept store whose fragment evolution lives in the git log as lineage trailers. Fire when creating, evolving, merging, splitting, or CORRECTING durable memory/knowledge that lives as OKF files under git; when recording how a belief changed or was repudiated; or when tracing a concept's history through time. YOU are the evolver — there is no evolution engine and no LLM sidecar. NOT for transient notes, scratch, or code comments.