Encode expertise for autonomous delivery.
Industrial firms generate the data — production telemetry, material genealogy, qualification handoffs, regulatory evidence — but it can’t move at software speed across organizational boundaries with attestation. The protocol layer doesn’t exist. Standard Engines is that layer: cross-OEM canonical schemas, cross-firm exchange on Multiplayer’s ZK substrate, tamper-evident provenance, codified operator knowledge, and cross-party interoperability runtimes. Every other North product rides this substrate.
The protocol layer industry never had
Mining majors run Komatsu fleets; mid-tiers run Cat or Sandvik; juniors run Epiroc. DCS vendors are DeltaV at one refiner, Experion at the next, PCS 7 or CENTUM somewhere else. PLM is Teamcenter for one prime, Windchill for the next. Steel Level-2 is Primetals or SMS or Danieli. The information exists in every vertical; the canonical wire format to move it across firms does not.
Standard Engines authors that layer. Cross-OEM canonical schemas with per-OEM adapters covering ~90% of installed base. Cross-firm exchange that rides Multiplayer’s zero-knowledge primitives — range proofs, set-membership, attestation flows — so operators can share without exposing formations, recipes, toolpaths, or configurations. Tamper-evident provenance from blast to OEM gate, scrap to coil, wellbore to corporate ledger. And canonical operator-knowledge encodings that turn senior-operator tacit knowledge into machine-readable, cross-firm-portable work standards.
Three protocol pillars
Cross-OEM schemas. Cross-firm ZK. Provenance + operator knowledge.
Standard Engines is five sub-components delivering one outcome — industrial data that moves at software speed across organizational boundaries with attestation. Three pillars carry the weight.
Cross-OEM canonical schemas
A neutral wire format that translates Komatsu / Cat / Sandvik / Epiroc fleet data; Fanuc / UR / ABB / KUKA cell automation; DeltaV / Experion / PCS 7 / CENTUM / 800xA / PlantPAx process control; Primetals / SMS / Danieli mill Level-2; Teamcenter / Windchill / 3DEXPERIENCE PLM. Aligned with OPC UA Companion Specs, GMG, Open-RMF, MASSRobotics — implementing them with the per-OEM coverage they currently lack.
Cross-firm exchange on ZK
Multiplayer’s zero-knowledge substrate makes the cross-org surface software-native. Operators share telemetry without exposing competitive specifics. Per-vertical instantiations: cross-firm geological exchange (mining), trader-operator data sharing (O&G), privacy-preserving grid substrate (power), cross-prime supplier registry (A&D), cross-customer requalification (chem), cross-mill metallurgy benchmarking (steel), competitive-leakage-free shop scheduling (contract mfg).
Provenance + operator-knowledge
Append-only, tamper-evident ledger of every production event. Material genealogy (chem), scrap-to-mill (steel), blast-to-OEM-gate (mining FEOC), wellbore-to-corporate (O&G), heat-genealogy (steel). Plus codified operator knowledge — SOPs, recipes, work standards, DFM rules — turned from tribal into canonical, machine-readable, and cross-firm portable. The skilled-trades workforce, encoded.
Standards in action
Cross-OEM. Cross-firm. Cryptographically private. Tamper-evident.
Inbound telemetry from a multi-vendor mining fleet canonicalizes, traverses ZK privacy primitives, and seals into the provenance ledger in under two seconds. Every operator that joins raises the floor for every other — competitive specifics stay protected at the privacy boundary.
Cross-OEM telemetry becomes sealed provenance in seconds
Capture from the OEM stack, canonicalize to a neutral schema, traverse the ZK substrate, and seal in the provenance ledger — without exposing competitive specifics.
Five components. One protocol layer.
The substrate every other North product rides on.
28 adapters covering ~90% of the installed base; LLM-driven semantic alignment across OEM nomenclature; versioned and backwards-compatible as OEM stacks evolve.
Range proofs, set-membership, attestation flows, privacy-preserving aggregation. Operators share statistical signal; competitive specifics stay sealed inside the privacy envelope.
Cryptographic hash chain with optional on-chain anchor for FEOC §45X and CBAM; replay + point-in-time reconstruction; signed at every hop from start to end of production.
Turn senior tacit knowledge (SOPs, recipes, DFM rules, runbooks) into canonical, transferable, machine-readable representations. The substrate AI policies compound on; the answer to the skilled-trades replacement-rate problem.
Author the protocols. Attest the flow.
The substrate every other North product runs on — cross-OEM, cross-firm, cryptographic privacy, tamper-evident provenance.