The Platform
Architecture for mobilizing.
The systems every chapter runs on its worst week, not just its best.
Most chapters don't lack will. They lack load-bearing systems. Advocacy lives or dies on whether the infrastructure exists before the moment demands it: the playbook, the data, the coordination channel, the person whose job it is to hold them.
Here is what that looks like built.
The national playbook chapters are running this year. I co-authored it and I manage its activation: chapter readiness mapping, capacity tiers so a 15-member chapter and a 150-member chapter each have a real standard, and reporting systems that turn activity into institutional memory instead of lost history.
A federal advocacy pipeline. I completed the movement's congressional advocacy program: federal policy training that produced working deliverables, and a model for putting trained advocates in front of their own delegations.
A two-surface legislative intelligence platform. A public tracker any member can read, and a permissioned console where a coalition sets positions, tracks hearings, and coordinates testimony, built for the 2027 state session and designed to be replicated in any state.
None of this waited for a title. The commitment is simple: stand this architecture up where it doesn't exist, with dedicated advocacy capacity, regional coordination, and a playbook every chapter can run, so mobilization stops depending on whoever happens to be heroic.
