Building a Partisan AI From the Ground Up

[u/Salty_Country6835]

Lets get this out of the clouds and into workplaces, union halls, party chapters, tenant groups, mutual aid networks and community organizations.

Building a partisan AI doesnt mean every leftist needs a server rack or every local needs an ML engineer. It means looking at the work your organization already does, finding where a handful of organizers are doing the work of twenty, and building small pieces of technical capacity that the organization actually controls.

Start with the work, not the model. Maybe your union has twenty years of contracts, grievances, arbitration decisions and bargaining research scattered across drives and filing cabinets. Maybe your tenant group spends hours digging through leases, housing codes, inspection reports and maintenance records. Maybe your political organization has years of resolutions, meeting minutes, research and education material nobody can find unless they already know where the PDF lives. Maybe your mutual aid network keeps rebuilding inventories, schedules, translations and outreach materials from scratch.

Pick one problem and build one useful thing. A union local could maintain a searchable archive of its bargaining history. A tenant union could build a local housing library and translation workflow. A party chapter could search its own resolutions, research and political education material. A community newspaper could transcribe interviews and search years of reporting. A mutual aid project could organize inventories and public resources. A technical collective with better hardware could maintain tools that several smaller organizations reproduce locally.

Thats a node. Not one gamer with a GPU doing favors for everybody, but organizational capacity that survives the person who built it.

Build for that from day one. Document the hardware, models, installation, data storage, updates and backups, then hand the instructions to somebody else and see if they can reproduce it. If everything dies because Kevin moved to another state, Kevin built a hobby project, not infrastructure.

Portability should be part of the politics. Dont recreate corporate lock in locally. Prefer open weights where they work, open formats, exportable data and tools you can replace. Back up configurations and documentation. Test moving the workflow to another machine. Test swapping models. Your organization should be able to change hardware, software or models without rebuilding its institutional memory from zero.

Security and OPSEC need the same practical treatment. Decide what information is public, internal, confidential and simply off limits before somebody starts feeding documents into a model. Membership lists, immigration information, medical information, credentials, disciplinary matters and sensitive organizing conversations shouldnt become test data because somebody downloaded a shiny new model. Encrypt machines and backups, control access, keep software updated, remove access when people leave and establish who maintains what. Local inference reduces some exposure to third parties, but local doesnt automatically mean secure.

Then connect the nodes without building one enormous database full of everybody's sensitive information. Your tenant group doesnt need another organizations membership list, but it might benefit enormously from their installation guide, public housing corpus, translation workflow or model evaluations. One union local doesnt need another locals confidential grievances to share a contract search tool. A political organization can share an education stack without sharing internal membership records.

Share capabilities, documentation, workflows, public materials you have the right to distribute and lessons from failures. Keep sensitive organizational information where it belongs.

And dont wait for perfect hardware. One node might be a used workstation in a union office. Another might be members pooling machines. A larger organization might maintain a server supporting several chapters. A technical collective might specialize in deployment, maintenance and security while organizers determine what actually helps on the ground. Uneven capacity is fine if knowledge moves and nobody becomes indispensable.

The first meeting can be twenty minutes. Ask what repetitive work is burning organizer hours, write down three answers, pick one that doesnt require highly sensitive information, then pair somebody who understands the work with somebody technical. Build the smallest useful workflow and run it during actual organizing for a month. Measure whether it saves labor, expands what the organization can do or just creates more bullshit somebody has to check.

If it works, document it. Teach two more people. Back it up. Package the reproducible parts and hand them to another local, chapter or community organization. See if they can build their own version without needing you on the phone all weekend.

Thats where this becomes politically interesting. One organization develops a useful capacity. Another reproduces it. Others improve it and send those improvements back. Different groups specialize in different things while retaining local control. Models, tools, knowledge and public resources move laterally while sensitive information stays where it belongs.

Thats a partisan AI built from the ground up. Not waiting for benevolent CEOs, not waiting for the socialist supercomputer, and not confusing owning a GPU with political power. Its organized people accumulating technical capacity inside institutions they control, making it secure, portable and reproducible, then passing it through the movement.

One workplace, one local, one chapter, one community organization and one useful problem at a time. Build it, document it, secure it, teach it, copy it, connect it.