Case study

Dark Sky

A generative-AI vendor had delivered survey overlays with geometry that wasn't there — a transmission line in the wrong place, a pole inventory that didn't match the ground. We rebuilt the pipeline so that every placed feature and every number traces to real survey data, and proved it with guards that fail the build if a model ever touches the output.

Industries:Aerial survey · Geospatial · EnergyEntities:Platform + client-facing deliverablesEngagement:Fixed-fee build · delivered and handed over
The situation

The client's prior deliverable had been produced with generative image models. It looked convincing and was wrong: a transmission line had moved from its surveyed position, and a pole inventory was miscounted. For work that feeds engineering and siting decisions, plausible-looking output is worse than no output — it carries the authority of a survey without the accountability of one. They needed overlays and viability studies their own customers could stake a decision on.

What we did
  • Built a deterministic CAD-to-overlay pipeline: survey CAD and classified point-cloud/GIS data placed on a georeferenced orthomosaic, where every point, line, and polygon lands where the data says it lands
  • Enforced the guarantee in code — a static analysis guard and a runtime import guard that fail on every test run if generative model code enters the overlay path at all
  • Constrained the study writer so it can smooth prose but cannot introduce a single number the statistics layer didn't compute, checked by a digit-level diff on every text surface
  • Exposed the platform three ways — Python library, console tools, and an agent-callable server — so it fits existing workflows instead of replacing them
  • Delivered a written scope-and-limits document stating precisely what the no-AI guarantee does and does not cover
  • Transferred ownership at handover, with the client holding the code outright
The outcome

The client can now put a number in front of their own customer and say where it came from. The determinism claim isn't a promise in a sales deck — it's a test that fails the build, which means it survives staff turnover and future changes. Ownership transferred on day one of the agreement, so the platform is theirs, not rented.

0
Generative-model code paths in the overlay
440+
Automated tests at handover
Day one
Client ownership of the code
Fixed
Price agreed before work started

Derek Hansen, Dark Sky, has agreed to speak with serious prospects. End-customer details remain under NDA.

Have a similar setup?

Multi-entity, multi-stack, vendor sprawl, and a leadership team that wants the same view of the business.

Start the conversation