Software Systems
Native runtimes, simulation tools, instrument control, and the interfaces around them.
Explicit contracts. Typed state. Failure paths kept visible.
Engineering Workshop · Zürich
We Design and Build Tools for Engineering Work.
The work spans native Rust runtimes, bench instruments, embedded interfaces, and the technical record required to maintain them.
101214
Observed Condition
MEASURE
Designed Method
DECOMPOSEBUILDTEST
Verified Record
OWN
Fig. 1 · Judgement remains visible from the first observation to the maintained result.
Working Range
Software, Hardware, and the Record Between Them
Each product keeps a narrow job. Shared infrastructure stays explicit and inspectable.
Hardware Instruments
Bench equipment, embedded interfaces, and focused fixtures for measurement and control.
Documented boundaries. Replaceable parts. Results that can be checked.
Technical Record
Architecture notes, project specifications, and operational evidence kept beside the work.
Methods and limits stated. The difficult parts stay in the record.
Selected Work
Products in Working Order
Dokime
A desktop test orchestrator that turns suites into repeatable executions, then keeps the telemetry, prompts, artifacts, and reports that prove what happened.
Meti
A Rust toolkit for exploring electromechanical designs across operating points, simulator runs, magnetics, standards, and the trade-offs hiding between them.
Axon
An experimental circuit workbench in Rust, combining a SPICE-inspired solver with schematics, execution state, waveform storage, plugins, and several ways to drive it.
Read SpecificationWhat Was Hard
The Boundary Is Part of the Work.
A useful instrument is more than the mechanism at its center. State, failure, calibration, interfaces, and evidence need an owner.
We keep those boundaries visible in code, drawings, and project notes. That makes the trade-offs reviewable before they become maintenance problems.
Read the Engineering Notes