nx_gtm_svc.nx

nx_gtm_svc.nx -- GO-TO-MARKET SERVICE FACADE. One agentic tool over the whole supplement/drug go-to-market stack: it composes the eight GTM library modules and exposes them as verb-dispatched JSON endpoints, inheriting the wire format, error shape and self-description from nx_service. THIS IS WHAT "MCP / API / AGENTIC / WORKFLOW READY" MEANS CONCRETELY. MCP-ready: a single fork-exec organ with a stable name + argv verb contract, registerable in tool_allowlist.conf and via /api/tools/register (fixed-arg pinning not needed -- the verb IS the first arg, and every handler is read-only). API-ready: pure stdout JSON with a versioned envelope + CORS-safe structured errors, drivable behind an HTTP route. agentic-ready: the `describe` verb emits this facade's own verb catalog with arg shapes -- an agent discovers what it can call, the service-level analog of MCP tools/list. workflow-ready: every verb is a PURE function of its arguments and returns a self-contained JSON object, so a pipeline can fan a list of ingredients through `ingredient.class` and feed the survivors into `formula.assess` with no shared state. scalable: stateless; a call is a fork-exec; concurrency is free. USAGE: nx_gtm_svc <verb> [args...] describe ingredient.info <id> formula.assess <retail_cents> <margin_permil> <servings> <fmt 1|2> claims.classify <sentence...> (joins remaining argv) jurisdiction.path <market> <ingredient> channel.best <ingredient> pathway.programme <prior 0|1|2> ethics.rank <jurisdiction> supply.effective <base> <spend_k> The heavy lifting stays in the libraries; this file is dispatch + shape. It adds NO new domain logic -- every number comes from a gated module -- so the facade cannot drift from the science it exposes. genealogy_id: supplement_gtm + service_infrastructure