Docs: operator naming convention + native-el language faculty direction

lang/AGENTS.md

@@ -123,9 +123,22 @@ exec("EL_HTTP_TIMEOUT_MS=300000 " + SOME_BIN + " " + args + " 2>&1")
 
 ---
 
+## Operator naming convention (for cognitive `.el` modules)
+
+When you write `.el` that names a **cognitive faculty / operator** (the language
+faculty, appreciation, interoception, the summon loop under `elp/`), name it for
+its **functional human equivalent** — the faculty a mind would name — **not** its
+linear-algebra operation. Put the math characterization in the `@impl`
+doc-comment, never in the operator's public name (e.g. public `discern`/`contrast`
+⟵ `@impl subtract (a−b)`; public `summon`/`recall` ⟵ `@impl LOCAL nearest-region
++ bounded spreading activation`). Full table + rationale in
+`foundation/el/AGENTS.md` § *Operator naming convention*. This does **not** apply
+to plain library/compiler code (a `sort` is a `sort`).
+
 ## Rules
 
 - New library functions → write in El
 - New OS/hardware primitives → write in C and register in `codegen.el` arity table
 - Never edit `dist/platform/elc` directly — always rebuild from source
 - Never modify `el_seed.c` to add functionality that El can express
+- Cognitive-faculty `.el` → name for the mind, algebra in `@impl` (see above)