nx_deployjrnl_lib.nx

nx_deployjrnl_lib.nx -- THE ONE RULER for deploy history and ROLLBACK SURVIVABILITY. WHY THIS EXISTS. On 2026-08-25 verification established that nx_docportal_admin_daemon had been deployed at least TWICE, and that the second write EVICTED the pre-change binary from its .prev rollback slot. Attribution came back UNVERIFIED for a STRUCTURAL reason: the estate has no deploy journal. No instrument could answer "was a deploy performed, on what, and what did it destroy". The effect was readable from artifact mtimes; the CALL was not readable at all. WHAT THIS IS, STATED PLAINLY: a RECONSTRUCTION, not a source-of-truth record. This capability is NOT written by the deploy path (that path is a daemon and is out of scope). It infers deploys by comparing the artifacts a deploy leaves behind, between one scan and the next. What that costs in fidelity is enumerated at dj_transition below and printed on every status artifact -- A RECONSTRUCTION THAT DECLARES ITSELF IS WORTH FAR MORE THAN ONE THAT IMPLIES IT WAS WRITTEN AT THE SOURCE, so the method line travels with the data and is never separated from it. WHY A LIB AND NOT A FUNCTION IN THE ORGAN: the organ and its gate must classify identically, or the gate is testing something the organ does not do. Every judgement below is a PURE function of already-measured numbers, so the gate exercises the SHIPPING ruler rather than a paraphrase of it. There is exactly one copy, so the two cannot disagree. license_tier: ORIGINAL