nx_doc_annotate.nx

nx_doc_annotate.nx -- LEGAL RUNG D4: the sovereign annotation / markup overlay. module: nishi-core.legal.doc_annotate capability: LEGAL_DOC_ANNOTATE The "sticky-notes / markup / feedback / lists" half of the DocuSign-better document experience. A FORMAT-AGNOSTIC overlay: it never parses the document, it anchors annotations to a {doc_id, version, page} so it sits ON TOP of any format (PDF / DOCX / our own doc format) without depending on it. Each annotation is a note, threaded comment, redline (strike + propose), highlight, checklist item, or signature-field placement, carried through an open -> resolved/accepted/rejected/done review lifecycle with author attribution and a resolver audit. The s-class safety invariant (the analog of D0/D5's never-void): once a document's envelope is COMPLETED (signed), its overlay is IMMUTABLE -- you cannot add or re-status an annotation on a signed agreement. The caller passes `frozen` = (the doc's envelope is completed); add / resolve REFUSE when frozen. Plus: review history is additive (Rule 13 -- rejected redlines are retained, never deleted), annotations are pinned to the version they were made on (a version bump does not silently move them), and a REQUIRED checklist gates the envelope send (compose with D2: a portal checks nx_ann_checklist_complete before nx_env_send). Representation: caller-allocated flat i64 record arrays (mirrors nx_doc_vault / nx_doc_envelope; no internal allocation). Pure logic core -> self-contained gate. Composes (at the gate): nx_doc_envelope (D2 frozen=COMPLETED + checklist-gates- send), nx_doc_vault (D1 versions). Distinct from nx_doc_envelope because: that is the signing lifecycle; this is the in-document review/markup overlay around it. license_tier: ORIGINAL lineage_id: nishi_doc_annotate_d4