nx_queue_load.nx

nx_queue_load.nx -- IM-Q1: the PROGRAM'S OWN COORDINATION DATA becomes first-class records on the sovereign store (operator 2026-06-11: "own our information management -- a tsv file is not nishi; bottom up hardware rung and each rung nishi"). The seg-store substrate is already hardware-up (rungs 1-9, beats FTS5); this rung puts the QUEUE on it: assignment_queue.tsv rows -> key "aq:"+<row-id>, value = canonical record {kind: queue-row, id, row}. SAME key, NEW VERSION on every change -- `nx_store_query hist aq:X-Q-003` is the row's full status time-travel, something the bare TSV can never answer. Idempotent: unchanged row = identical canonical bytes = dup_instore, never re-added. sponsor_decisions.tsv / planning_prefs.tsv / callouts.tsv lines -> content-CID line records (sd:/pp:/co: prefixes, nx_log_load pattern) -- the sponsor's decisions + the training corpus gain provenance lineage. The TSV files stay as the WRITE surface this rung (API stability); IM-Q2 (filed) moves writers store-first and derives the TSV as a render. argv[1]=store prefix override, argv[2]=queue path override (gates). Evidence: QUEUE-STORE row -> stdout + knowledge/status/infomgmt_store.log. license_tier: ORIGINAL