What it changed
- Shipped in one week, 100% of the code written with Claude Code under our specification and review.
- Field measurements ingested at scale into a data lake and PostgreSQL.
- A clean boundary that keeps a scientific partner's intellectual property on its side, and everyone's trust.
The situation
When something in the environment hits a growing region, producers need to know how exposed their crop was, and how likely it is to be damaged, before they spend money harvesting and processing it.
The analysis that turns field measurements into a risk score belongs to a scientific partner. Their model is their intellectual property, and they weren't going to hand it over.
What we built
- Ingestion at scale of the measurement payloads, into a data lake for analysis and a PostgreSQL database for the application. We've built this kind of pipeline many times (an example).
- A clean boundary for the science. We send the data to the scientific partner, their model computes the insight on their side, and they send back the results, which we store and present. The valuable analysis never runs on our systems. We're the data and application provider, they keep their IP, and each side can trust the arrangement.
- A web app that doubles as an admin panel, for the client's users and for managing them.
- Infrastructure in code with Pulumi, like every system we build.
How it was built
Entirely with Claude Code, and shipped in a week. That isn't a shortcut on quality: it's what agentic programming looks like after years of practice. We wrote the specification, set the architecture and the standards, and reviewed what the agent produced. The routine parts of the system, which we'd built by hand many times before, took hours instead of weeks.
Why it matters to you
Two lessons. When a partner's IP is the product, design the boundary first and the rest follows. And a well-specified system of this size no longer takes a quarter to deliver: it takes a week.