Build · One engineering system

Full stack means the evidence has nowhere to hide.

We build across software, sensing, embedded systems, electronics, mechanical design, and integration, then let each test shape the next build.

Read the public build log
Public build log

The work, dated and stated plainly.

We publish the direction of the work without turning internal records into public claims.

  1. July 2026

    Outdoor operation

    Our first sensing prototype was fielded outdoors in July 2026. It now operates unattended on our bench.

  2. August 2026

    Prototype testing

    Physical prototypes exist and have been tested.

  3. September 2026

    A shared world model

    Sipsa-built machines share one world model on the bench; the site tasks a machine, and the machine reports back.

  4. September 2026

    An irrigation decision

    An irrigation-control prototype made a watering decision on its own chip on the bench, without a physical valve.

  5. October 2026

    Preparing controller tests

    Irrigation controllers are on the bench for planned plug-in testing. Physical validation remains next.

Full-stack engineering

Build, test, and learn as one loop.

The system, its implementation, and the evidence behind it develop together.

  1. Systems architecture

    Design the relationships between sensing, decisions, interfaces, and physical behavior.

  2. Perception

    Develop signal processing and models as part of the wider system.

  3. Embedded systems

    Shape dependable software around constrained physical environments.

  4. Physical integration

    Bring compute, sensing, power, and form together as one design problem.

  5. Evaluation

    Use structured evaluation to guide engineering decisions across the stack.