NERM is a tamper-evident audit log — append-only, SHA3-256 hash-chained, and you verify it by recomputing every seal yourself. No trust in me, no server, no network. Not a blockchain: single writer, verified by math, not peer-consensus. Don't take my word — break it: git clone … && python nerm_verify.py releases.jsonl → INTACT. Now open releases.jsonl, change one character in any block, run it again. It names the exact block that broke and refuses. Try to alter a block and keep it verifying — you can't without finding a SHA3-256 preimage. The verifier is ~90 lines, stdlib only, no dependencies. If you can make a tampered chain pass, I want to see it. Closed pieces are Python, built on top of this log — the operational product, not the trust primitive. A verifier can't check them, so they add nothing open. The part meant to be attacked is the part you already cloned.
This system is much more than just a chain this system currently is comprises of over 4,250 files ( expanding as i add more to the ecosystem ) locked into the master chain