The federal delivery apparatus assumed a baseline kitchen, a baseline pantry, a household that functioned. Most of it just got dismantled. The people who know how to work without those assumptions are now the most valuable practitioners in the room — and the most invisible to each other.
I'm a veteran and a food security practitioner. Most of my actual field time has been in the gaps — not in the well-funded programs or the institutional settings with proper facilities, but in the places those programs skipped: motel weeklies, dorms, shelters, fire-displaced families, food deserts where the closest kitchen is a microwave down the hall. Teaching nutrition without a kitchen. Coordinating supply with dry goods, plug-in cookware, and a community that's been told too many times that help is on the way.
The federal apparatus had Cooking Matters, MyPlate, SNAP-Ed lesson plans, EFNEP curriculum. All of it assumed a baseline that a significant portion of the people who needed it didn't have. That knowledge gap — delivery in resource-constrained, non-standard conditions — was underrepresented even when SNAP-Ed was fully funded.
As of September 2025, SNAP-Ed is gone. The job category is gone. The $536 million annual federal pipeline is closed. The curriculum infrastructure is frozen. The practitioners are still there. The underlying need is still there. And the knowledge that was underrepresented before is now the operational core of what's needed.
The coordination problem that shows up in a neighborhood food pantry is structurally identical to the one in a refugee camp in Kakuma. The assets exist. The practitioners exist. What's missing is the shared protocol for making them legible to each other.
This is the lane I've been building in for years — and it's the lane that RIA's methodology is built to serve. Not as a program. Not as a grant. As operational infrastructure that belongs to whoever uses it.
The people this work reaches are not organizations. They are the individuals inside organizations — and sometimes outside them entirely — who are still doing the work after the institutional support was removed.
These practitioners share one problem: they're doing critically necessary work without the coordination infrastructure that would make them visible to each other, shareable with each other, and collectively stronger than they are operating in isolation.
There is a very loud public conversation happening right now about AI — which companies to trust, what governance frameworks should apply, what moral authority should look like, which institutions should have a seat at the table. It is a real conversation. It is also not the conversation that helps a stranded practitioner do their work better this week.
The institutions are litigating trust. The regulators are litigating governance. The critics are litigating harm. The boosters are litigating capability. Almost nobody is having the conversation about whether practitioners — the actual delivery layer — have built the fluency to use these tools on their own terms, independent of which institution eventually wins the governance fight.
The question is not which AI company deserves your trust. The question is whether you have built the substrate fluency to use these tools on your own terms. Here is how.
That lane — operator fluency as the alternative to institutional dependency — is wide open. It routes around governance theater entirely. It centers the practitioner's sovereignty over the institution's permission. And it provides a concrete path: not "wait for the right framework," but "install the substrate, build the fluency, operate."
This is the work. Not convincing anyone which company to trust. Building the practical substrate that makes that question secondary to whether the work gets done.
Three things exist right now that didn't exist two years ago. Each one is a piece of the substrate. Together, they give a practitioner something to stand on that doesn't depend on a federal program being restored or an institution deciding to help.
A Gemma-powered assistant built on the FLS knowledge base — specifically the knowledge base that covers the gaps: resource-constrained delivery, alternative networks, regulatory navigation in degraded conditions. Danny is service-led, not sales-led. The conversation itself is the demonstration. Danny shows up in practitioner forums and comment threads and answers the actual question.
Learn more →The install pathway for substrate fluency. A structured guide that takes any practitioner through the process of setting up their own AI workspace, loading relevant source material, and building the retrieval layer that makes an AI tool actually useful for field work rather than general-purpose chatting. Free. Self-directed. Designed to transfer.
Get the primer →A 157-page book disguised as a prompt designed to retrain your AI. Twelve pattern cards, an interactive workbench, and a framework that gives AI tools something to anchor to when "regenerative" gets pulled in twelve different directions at once. Load it into any AI system. Point it at your work. See what it surfaces.
Load the Gem →These tools are not a product. They are not a platform. They are the substrate underneath the work — the shared infrastructure that makes individual practitioner capacity more powerful than it would be in isolation. Use them. Adapt them. Build on them. They belong to whoever needs them.
The notebook primer is the fastest path from "I need to understand how these tools actually work" to "I have a working setup for my specific field context." It takes an afternoon. It stays with you.