Jump to a section
Start Before The Model Exists
The first question is not “How should this model respond?” It is “What problem are we solving, who defined it, and should an AI system be used here at all?”
Affected workers, communities, and domain experts can reveal mistaken goals before they become datasets and code.
Power Appears Across The Lifecycle
Problem
Define the purpose, limits, and people affected.
Data
Choose sources, permissions, languages, exclusions, and stewardship.
Evaluation
Decide which failures matter and who gets to test them.
Deployment
Set conditions, monitoring, pause authority, and appeal.
Consultation Is Not The Same As Influence
A listening session can be useful, but it is not shared power if the institution may ignore every contribution without explanation. Participants should know what is open to change and how decisions respond to what they heard.
The test is simple: can participation alter the system, or does it only decorate the launch?
Build Community Capacity
- Support community-owned datasets and language resources.
- Fund independent testing and public-interest research.
- Give affected people access to explanations, incident reporting, and appeal.
- Publish known limits and changes made after public input.
- Include people who can say no, slow down, or require a different design.
Cognitive Liberty Is The Standard
AI should expand people’s ability to think, learn, create, and participate—not quietly narrow their options or present machine output as unchallengeable authority.
The Architecture of Defiance places human judgment, pluralism, and contestability around the model.

