Kite-mapping as infrastructure

Satellites image the world on a schedule nobody local controls, at a resolution nobody local can fund, filtered by platforms nobody local can audit. Kite-mapping inverts the economics: a $40 kite, a digital camera, and a Sunday afternoon produces imagery more useful to a specific watershed than anything in orbit. That's not DIY nostalgia; it's a working example of infrastructure built at the scale of the problem.

The Public Lab community has shown the pattern scales. A high-school team can produce orthomosaic maps of a coastline. A coalition of neighbors can image a refinery edge. A restoration group can track a wetland's recovery month over month. None of it depends on permission from above — it depends on the kite, the camera, and the willingness to walk the shoreline.

What this lets stakeholders do: hold the instruments. Once the instruments are local, the data cadence is local, the analytical priorities are local, and the narrative that comes out of the imagery is accountable to the community that produced it. The platform stack sits on top of community infrastructure, not the other way around.

What's still open: where is the Totem Protocol seam that lets kite-mapping outputs flow into agent-driven monitoring loops without losing the community's authorship?