Most stacks invent a new ID every time work crosses a system boundary — CAD file number, PLM item, ERP material, MES lot, QMS NCR. The “digital thread” becomes a mapping table someone has to keep honest. When CAD, PLM, and ERP disagree about which object they mean, the shop floor ships the wrong revision and the invoice still looks fine.
N23D keeps one part identity from sketch through invoice. The same object that starts in CAD is the item PLM revises, the material ERP costs, and the lot MES and QMS inspect — no sync job rewriting keys overnight. One native Rust binary. Local-first vault. Entra signs people in; it does not host your parts. Permanent license.
Thirteen rented suites fail this test the moment two IDs for the same part diverge. One platform. Full digital thread. If your CAD file, PLM item, and ERP material only match after a batch job, you never owned the identity.