gateway

Files (1)

• SKILL.md

SKILL.md (first lines)

# Gateway

The core design law is read-only; learned taste lives in overlay files pointed
to by the store. This skill tells you what to read, in order.

## Protocol

1. Query the pointers:
   `python <plugin>/db/store.py sql "SELECT path, kind, promoted FROM design_guide_versions ORDER BY id"`
   (no db / no rows → core law only). Promoted rows live in the project's
   `docs/design/`; unpromoted ones in `workspace/overlays/` — read both.
2. Read in order: `skills/design-law/SKILL.md` first, then each overlay —
   later overlays override earlier ones; every overlay overrides core **except**
   the anti-style list and the token-centralization rule, which are inviolable.
3. Also load active overlay rules:
   `python <plugin>/db/store.py rules design` (rows with `source=overlay:*`).

## Rules

- Never edit core law files at runtime. New taste = new overlay file in
  `workspace/overlays/` + a `design_guide_versions` row (the learner agent's
  job, via `Atelier learn`).
- Conflicting overlays: newest wins; note the conflict to the user.
- Promotion to core is a deliberate human act (a future
  `Atelier promote`), never automatic.
Host integration: read [the runtime contract](../../references/runtime.md) for plugin/project paths, host command names and capabilities. Explicit user instructions and repository conventions take precedence over these defaults.

From INERATE/atelier, MIT.

More from INERATE/atelier