nx_vizsla_docgen.nx

nx_vizsla_docgen.nx -- NISHI VIZSLA OFFICE DOCUMENT GENERATION: turn coordination data into a real office document and FILE it in the never-lose doc manager. Operator 2026-07-08: "office ... along with document management and all the other things". This is the bridge that ties the three named domains: COORDINATION (a venue booking / plan / event supplies the fields) -> OFFICE (a valid .docx via nx_docx) -> DOCUMENT MANAGEMENT (a versioned, rel-linked doc: record nx_vizsla_doc reads back byte-exact). GENERIC by design (rule 22, no venue/plan reader duplication): the input is a simple fields file -- line 1 = the document TITLE (first paragraph) lines 2..N = one paragraph each (e.g. "Venue: Lakeside Pavilion"); blank lines skipped so venue agreements, invite letters, plan summaries, meeting notes are all the SAME organ over different fields (produced by the venue/plan/group boards). Output = a real Word .docx stored as a doc: record. Command: build <docprefix> <docid> <doctype> <rel> <date> <fieldsfile> [segid] -> writes a .docx (nx_docx docx_write) + stores it in <docprefix> as doc:<cid> (doctype/rel/date), additive + CID-idempotent (re-build identical fields => already stored, new=0). The stored bytes are the exact .docx (byte-exact retrievable via nx_vizsla_doc get; readable via nx_docx read). Loud-fail: missing/empty fieldsfile, bad date, docx build fail, oversize (> 512KB). DRY debt: the doc: record framing is replicated from nx_vizsla_doc's put (both should import a shared nx_vizsla_docstore lib later); the gate CROSS-CHECKS it by reading the record back with the REAL doc organ. spec: knowledge/research/2026-06-22-vizsla-sclass-roadmap.md license_tier: ORIGINAL