Projects.

The problem

Keeping irrigation control local when the network is unavailable.

Architecture & approach

Shared Rust domain code evaluates local rules and controls irrigation. The edge stores events in SQLite. An optional durable outbox syncs event history to PostgreSQL.

Engineering challenges

Safety checks, command reconciliation and device simulation keep control independent of the cloud. ESP32 firmware is implemented, but testing on physical hardware is still pending.

Technology stack

The problem

Using raw MAVLink telemetry to explain what went wrong and show the evidence.

Architecture & approach

Records telemetry locally and converts mission events to a common format. It checks YAML assertions and creates failure reports with links to the evidence.

Engineering challenges

The vehicle interface is read-only and sends no flight commands. Browser and desktop apps share a local backend. Deterministic demo runs make testing repeatable.

Technology stack

The problem

Showing how parts of a Rust workspace relate to each other without uploading source code.

Architecture & approach

Uses Cargo metadata and rustdoc JSON to build an interactive graph of crates, modules, types and traits. It runs locally or exports a self-contained static site.

Engineering challenges

Shows typed relationships between code elements. It can use a nightly Rust toolchain to extract documentation. Static exports do not include source code, and the tool supports different workspace layouts.

Technology stack

The problem

Applying trade rules and rewards for verified services in a deterministic distributed system.

Architecture & approach

The Rust workspace has separate layers for protocol types, deterministic domain rules, redb state and a CometBFT consensus adapter. The documented design also includes a worker network and a PostgreSQL read model.

Engineering challenges

The domain code does not depend on I/O or consensus infrastructure. Automated checks verify dependency direction and determinism. Balances and rewards use integer arithmetic.

Technology stack

The problem

Sending vessel events to clients based on location and adding vessel metadata.

Architecture & approach

Rust services receive AIS data and use an H3 spatial index to route events. Updates are sent over WebSocket. A separate worker builds a versioned Redis vessel catalog. A Kotlin Android app shows vessels using MapLibre and OpenSeaMap.

Engineering challenges

Clients subscribe to selected cells and receive events for those areas. Catalog versions can switch atomically or roll back. The aggregation and persistence crates are still placeholders.

Technology stack

The problem

Simulating cargo-vessel handling in a narrow river fairway, including delayed controls, currents and estimated depth.

Architecture & approach

Unity Rigidbody physics models point buoyancy, water resistance, gradual propulsion and rudder response. A bridge-style interface shows river radar, predicted paths and navigation marks.

Engineering challenges

The prototype models motion relative to the water, estimated water depth and vessel instruments. It includes runtime checks and Unity tests. It has not been validated for professional training or real-world navigation.

Technology stack