The build

What I'm actually building, and the plan I'm following. The centerpiece is a self-directed, 54-week robotics field manual, from zero to a coordinated rover-and-VTOL fleet, written and revised in the open.

The curriculum

Fifty-four weeks, thirteen months, one builder. Foundations, a two-stage rover (a small v1, then the 1.25 m adjustable-height v2), a legged Pupper, a trusted-stack drone, a long-endurance VTOL, contested-spectrum and GPS-denied navigation, and a sourcing doctrine that keeps the whole fleet trustworthy. See the week-by-week roadmap →

Current builds

Rover v2, a 1.25 m adjustable deck, month 7, in design. Long-endurance VTOL, month 11, queued. Fleet coordination, the Year 2 flagship: rovers as motherships that carry and deploy their own recon drones.

Sourcing doctrine

One line: a part gets the trusted-origin treatment only if it runs firmware and can touch a network or hold mission data. Flight controllers, GPS, radios, and compute go trusted; motors, ESCs, batteries, and lidar stay whatever's cheapest, because a dumb offline part can't phone home.