nx_sov.nx

nx_sov.nx -- THE STANDARD SOVEREIGN DATA CLI (operator 2026-07-16: "this happens a lot -- make writing nishi ecosystem formats THE STANDARD, integrated into our mcp/apis, interoperable with 3rd party"). Root cause of the recurring no-TSV violations: nx_sov_ledger is a LIBRARY (needs an organ authored) while `cat > x.tsv` is one command -- so sessions under pressure take the flat path. THIS organ makes the sovereign path the one-command path: put <prefix> <key> <value> write a string value (latest-wins) put-file <prefix> <key> <file> write a file's bytes as the value (binary-safe, <=1MiB) get <prefix> <key> print the latest value has <prefix> <key> exit 0 present / 1 absent import <prefix> <tsvfile> INTEROP IN: key<TAB>value rows -> sovereign store, and writes the __ids__ index (newline-joined keys) so nx_memory `index` / export can enumerate export <prefix> <outfile> INTEROP OUT: __ids__ index -> key<TAB>value TSV at the BOUNDARY (a DERIVED VIEW for 3rd parties, never the store) The MCP surface: nx_memory (sibling, S17) already serves READS (stores/get/history/index) over MCP; its put/tombstone write-cap increment will front THIS same store -- one substrate, CLI + MCP two doors. Store = seg_store via nx_sov_ledger (sov_put/sov_get/sov_has). license_tier: ORIGINAL