nx_notice.nx

nx_notice.nx -- W-TD-2: THE NOTICE LEDGER. The state half of the safe-harbour posture. nx_takedown decides WHAT SHOULD HAPPEN to a notice; it is pure and holds nothing. That made it a document rather than a control (debt 1785893553): the operator's posture -- "like google or bing or ai companies i use what is available till its requested to be removed, and i inherit that different set of requirements" -- only exists if the REQUEST can be received, TIMED, and ANSWERED with evidence. ★★★★★AN INSTRUMENT THAT NOTHING IS REQUIRED TO CONSULT IS A REPORT, NOT A CONTROL (the estate's own publishing-house law, applied here). WHAT COMPLIANCE ACTUALLY REQUIRES OF THE RECORD, and why each is mechanical here: * EXPEDITIOUS RESPONSE is a claim about TIME, so the clock must start at receipt and be queryable -- `overdue` answers "what am I late on" without anyone remembering to look. * The record must be ANSWERABLE LATER, so it is APPEND-ONLY (rule 13, history is sacred). Acting on a notice APPENDS an action row referencing the id; it never edits the original. ⇒ a ledger you can rewrite is not evidence of anything, and rewriting it to look compliant is the failure mode that turns a paperwork problem into a credibility problem. * 512(i) repeat-infringer policy needs a COUNT, which needs persistence. * QUARANTINE (nx_realperson's RP_QUARANTINE, for a SUSPECTED-minor call that may have misread a lawful adult) must WITHHOLD WITHOUT DESTROYING -- so it renames into a quarantine prefix and records the move. Never unlink: the misread performer's evidence has to survive. ⚠NOT LEGAL ADVICE. This is bookkeeping built to the shape of the regime, so a human can answer quickly and prove what they did. verbs: file <class> <locator> <complainant> <w><l><c><g><s> -- record a notice; prints its id act <id> <action> [note] -- append what was done (never edits) list [n] -- recent rows overdue <now_epoch> -- notices past their statutory clock strikes <target> -- 512(i) count for a target license_tier: ORIGINAL expect_exit: 0 module: nishi-core.hosting.notice