---
name: leveva-service-is-client-services
description: "HARD RULE: leveva must NEVER implement SERVICE/SQUERY/SERVLIST — do not plan, scope, or build it under any interpretation"
metadata: 
  node_type: memory
  type: project
  originSessionId: ceb3c190-659c-4db9-9784-bd3efb536916
---

**SERVICE is NEVER to be supported in leveva and MUST NOT be implemented.** This
covers the whole RFC 2812 services trio — `SERVICE` (the registration-time command),
`SQUERY`, and `SERVLIST` — under *any* model (client-connection services, linked
pseudo-servers, anything). Do not add it to PLAN.md, do not write a plan file for it,
do not pick it as "the next slice," do not add `ServiceInfo`/a services counter/`484`
restriction scaffolding for it. If a future task seems to call for it, stop and
confirm with the user instead of building it.

**Why:** the user ruled it permanently out of scope (2026-06-09), firmly, after an
earlier attempt was started. An earlier version of *this very memory* wrongly said to
implement it as RFC 2812 client-services — that guidance was **wrong** and is the trap
to avoid. The locked C oracle config has `USE_SERVICES` OFF, so the oracle never
supported client services either; leveva follows suit by simply never having the
feature. SERVICE/SQUERY/SERVLIST stay unimplemented — a client issuing them just gets
the `421 ERR_UNKNOWNCOMMAND` fallback in `command/mod.rs`, which is correct and final.

**How to apply:** treat SERVICE/SQUERY/SERVLIST like a deliberately-omitted command,
same status as [[close-not-required-leveva]] (CLOSE). When choosing the next P11 slice,
skip it entirely. See [[leveva-command-folder]].