Native macOS · Systems engineering
Motion Control, Rebuilt
I architected and rebuilt a legacy stage-rigging application that could no longer run on modern macOS, pairing AI-assisted workflows with manual verification. The result is an 11-module Swift 6 and SwiftUI architecture with a built-in drive simulator and 1,400 reference cases checking numeric behavior against the original C implementation.
The problem
The original 32-bit application could no longer run on modern macOS. Its behavior had to be understood from the source before a credible replacement could be designed.
How I approached it
I designed the 11-module target architecture, set product and safety decisions, tested builds by hand, and used independent reviews to challenge generated code and documentation. An audited specification anchors the rebuild; the original C code acts as a reference for numeric behavior.
Inside the build
- Rebuilt a legacy 32-bit C/Objective-C stage-rigging application in Swift 6 and SwiftUI across 11 modular packages with strict concurrency, verifying deterministic motion-engine behavior against 1,400 C reference test cases.
- Compared unit conversion, target clamping, and speed behavior against 1,400 generated legacy reference cases.
- Used strict concurrency and regression tests to address stale input, stop handling, and shutdown races.
- Built a simulator-only demo whose packaging checks refuse hardware-control symbols.
The result
Produced a simulator-only macOS demo with a modular motion engine, SwiftUI console, and regression coverage for reproduced concurrency failures. The app’s module boundaries keep hardware access out of the demo binary.
Where it stands
Verified in simulation and loop-back only. The software has not driven real hardware, is not safety-certified, and requires bench validation before hardware motion can be enabled. Client identity is omitted.