nx_coindex_core.nx

nx_coindex_core.nx -- CONFLICT-FREE co-edited index (07-15 operator: "we can't have conflicting writes when we use you on parallel workstreams; we need SOTA orchestration everywhere"). The root cause of the MEMORY.md / board merge-dance = many sessions HAND-EDIT the same file bytes. The SOTA answer is append-and-derive (event-sourced / convergent): a session NEVER edits the shared index; it APPENDS its own entry (keyed by a slug) to a journal -- atomic under the proven flock floor (nx_framed_append / WMS R8, MEASURED exceed-git: concurrent lost 0/144 vs git 132/144) -- and the index is DERIVED by a reducer that keeps the LAST entry per slug (last-write-wins). No two sessions ever touch the same bytes, so there is nothing to conflict on, by construction. Pure append + reduce funcs here (gate-locked); a CLI wires it to MEMORY.md / the board. license_tier: ORIGINAL