Clean Room Engineering Policy
Dry Machina is developed strictly under a clean-room software engineering methodology. The goal of this process is to ensure complete mathematical correctness, independent reproducibility, and total license hygiene.
1. Specification-First Architecture
All toolpath compilers, intermediate representation (IR) dialects (dry.intent/1, dry.motion/1, dry.tool/1, dry.machine/1), and emitter passes are written from formal mathematical definitions and public machine specifications rather than reverse-engineered code.
2. Independent Conformance Vector Testing
To verify behavioral correctness without code contamination, we maintain a standalone conformance oracle suite (conformance/vectors/). These vectors contain strictly numerical inputs and expected physical toolpath outputs validated by standalone verification scripts (tools/validate_vectors.py) running independently of the core compiler.
3. Zero GPL / Tainted Code Policy
The released Rust compiler crate (crates/core/), CLI binaries, WASM bindings, and TypeScript/Python SDKs are written completely from scratch and are 100% free of GPL-licensed dependencies or copyleft code, guaranteeing unencumbered enterprise and commercial deployment.
4. Formal Mathematical Proofs & Invariant Checks
Critical motion planning algorithms (such as 7-phase S-curve profiles, Euler-Rodrigues quaternion rotations, and RTCP kinematics) are verified against analytical mathematical proofs and property-based test fuzzers.