nx_service.nx

nx_service.nx -- SERVICE BASE rung. The shared harness every domain organ inherits to become an MCP tool + HTTP-drivable API endpoint: a JSON response-builder object, a versioned envelope, structured errors, and a verb dispatcher. This is the base class of the whole lab-science / go-to-market service family -- write it once, and every facade over the existing library modules is a thin skin on top. WHY A BASE AND NOT A COPY PER SERVICE. Seventeen library organs already exist as pure functions. Turning each into a standalone tool by hand would duplicate the envelope, the escaping, the error shape and the dispatch seventeen times -- the exact copy-paste this codebase forbids. Instead a facade composes: it owns a verb table and handlers, and delegates all of the wire format to NxJson + the nsvc_* envelope here. Rule 15 (DRY through a shared library), rule 6 (OOP: NxJson is an object with methods), rule 12 (structured errors at the boundary), rule 19 (a VERSIONED contract). AGENTIC + WORKFLOW READY BY CONSTRUCTION. Every reply is machine-readable JSON with a stable envelope, every handler is a PURE stateless function of its arguments, and every facade exposes a `describe` verb that emits its own verb catalog -- the service-level analog of MCP tools/list, so an agent can discover a facade's capabilities without a human in the loop. Stateless + structured + self-describing is exactly what a pipeline stage or an LLM tool call consumes. SCALES BY BEING STATELESS. No handler holds state between calls; the whole object is a per-request scratch buffer. N concurrent callers are N independent invocations, so horizontal scale is free -- fork more workers. TRUNCATION IS MARKED, NEVER SILENT. The response buffer is bounded; an overflow sets ov=1 and the envelope reports "truncated":true rather than emitting invalid JSON. A parser must never receive a lie. genealogy_id: service_infrastructure + nishi_sovereign_api