Why we are treating Hack for the Futures as more than a hackathon
A shorter first-person social version focused on why prototype-building, foresight, and climate governance need to stay in the same frame.
I keep coming back to one point: Hack for the Futures should not be understood as just a one-day hackathon.
What excites me is the architecture around it. We have a builder sprint during London Climate Action Week, practical AI and climate prototypes, future scenarios tied to each build, continuation support through GYC AI Labs, and a visible policy pathway connected to The New Alignment and the UK T20 conversation.
That combination matters because too much climate work still breaks in the middle. We either get great ideas with no delivery capacity, or strong policy language with very little that can actually be tested, shipped, and improved.
The New Alignment publicly describes itself as a hub for policy advice to the G20, convened by the UCL Institute for Global Prosperity ahead of the UK's 2027 G20 Presidency. For me, that raises the real question: how do youth-built tools and foresight outputs become useful to institutions that are shaping climate and economic policy right now?
My view is that technical capacity is part of climate capacity. If young teams can build faster, deploy more confidently, and keep iterating after the event, they are not just participating in the climate conversation. They are expanding what climate action can actually do.
That is the bet behind GYC AI Labs. And that is why Hack for the Futures matters to me: it is a bridge between prototype-building, foresight, and policy translation, with enough continuation behind it to become more than a moment.