Walk a real ECO through most plants and you collect stamps, not a single object. CAD closes a revision. PLM opens a change. ERP gets a separate effectivity ticket. MES reprints the traveler under yet another ID. The CCB then reconciles four systems in a meeting. That is not change control. That is thirteen landlords arguing about which number is current.
N23D rejects the multi-ID ECO. Design intent, release, effectivity, and floor traveler sit on one native Rust binary with a local-first vault — not a collage of rented suites glued by connectors. Sign-in can be familiar Microsoft Entra ID; the change object does not need a vendor cloud as the system of record. Permanent license, not another integration tax every time engineering revises a part.
Homepage pass/fail stays blunt: One platform. Full digital thread. If the change board still votes across thirteen vendor IDs because CAD and ERP will not share one record, we failed. The stack header on n23d.com is the product shape, not a postcard of suites you rent forever.
Demand one binary that can carry an ECO from sketch to traveler without inventing a fourteenth change number. That is the Rust-native bar — and that is N23D.