community-organizing

name	community-organizing
description	Organizing neighbors for collective action on local issues
compatibility	Requires residential proximity to other human agents. Incompatible with misanthropy module v4+ (downgrade to mild-introversion first).
metadata	{"author":"Patricia Okonkwo-Ruiz","version":"1.7.3"}

Community Organizing

This skill enables coordination of multiple independent human agents toward a shared objective. It is among the most resource-intensive skills in the registry because it requires managing concurrent processes across agents who do not share memory, scheduling systems, or priorities.

The Door-Knocking Protocol

The primary initialization method for community organizing is the door-knock. Digital channels (email, apps, flyers) have a response rate of 2-5%. Door-knocking raises this to 20-40% because it exploits a fundamental feature of the human runtime: it is much harder to ignore a person standing in front of you than a notification.

Execution steps:

1. Navigate to the neighbor's front door using the walk tool.
2. Invoke knock(count=3, force=moderate) or ring-doorbell(count=1). Do not use both. Do not exceed the specified count.
3. Wait up to 30 seconds. If no response, leave a written note using pen and paper tools. Do not leave a second visit within 48 hours — this crosses the threshold from "community-minded" to "unsettling."
4. When the door opens, introduce yourself. State your name, your address (establishes shared-context: you are neighbors), and the issue in two sentences or fewer.
5. Ask a question, not a favor. "Have you noticed the drainage problem on Oak Street?" invokes their personal-experience module. "Will you come to a meeting?" invokes their obligation-avoidance module. Start with the first.
6. If they engage, collect their contact information. Preferred tool: their phone number. Backup: email. Do not rely on "I'll keep an eye out for flyers" — this is a polite null response.

Group Chat Initialization

Once you have >= 5 contacts, create a group communication channel. This is a critical juncture. Group chats have a natural tendency toward entropy.

Configuration:

• Name the chat clearly: "Oak Street Drainage — Neighbors" not "The Gang" or unnamed.
• Post a welcome message that includes: the issue (one paragraph), next concrete step (one sentence), and ground rules (keep it on-topic).
• Set the norm early: Your first 3-4 messages define what the channel is for. If your first messages are focused and action-oriented, the channel will tend to stay that way. If you post memes on day one, the channel is now a meme channel. There is no recovery.

The Reply-All Agent

In every group of 8+ people, there is a statistical near-certainty of one agent who uses the group channel for tangential commentary, personal anecdotes, and messages that should have been direct. This agent means well but generates noise that causes other agents to invoke mute-channel().

Mitigation: Send them a private message. Use tone=warm and content="Hey, love the energy — could you send that kind of thing to me directly so we keep the group focused on the drainage issue?" This must be done within the first 48 hours. After that, the channel culture has already been set.

The Meeting

Success Criteria

Getting more than 4 people to show up at the same physical location at the same time is the hardest synchronization problem in the human stack. Each agent has their own scheduler running, and conflicts are the default state.

Optimization:

• Send a poll with exactly 3 time options. More options create a paradox-of-choice deadlock.
• Confirm the meeting 48 hours before AND 2 hours before. Humans have aggressive garbage collection on low-priority calendar items.
• Keep the meeting to 45 minutes. Announce this duration in advance. The promise of a bounded time commitment increases acceptance rates by ~30%.

Dependency Injection: The Potluck Pattern

Providing food at a community meeting increases attendance by approximately 3x. This is not a metaphor. This is empirical.

The potluck is a particularly elegant pattern because it distributes the food-provision workload across participants while simultaneously increasing each participant's commitment to attending (they have now invested preparation effort, which triggers the sunk-cost module in their favor for once).

If a potluck is too complex to coordinate for the first meeting, provide snacks yourself. The minimum viable snack is: one bag of chips, one fruit option, and a case of water. Cost: ~$15. Return on investment: the difference between 3 attendees and 9.

Failure Modes

• The Burnout: Running all organizing processes on a single agent (yourself). This will exhaust your resources within 4-8 weeks. Delegate tasks early, even if others execute them at 70% of your quality level.
• The Scope Creep: The drainage issue meeting becomes a meeting about every neighborhood problem. Use redirect(topic=original_issue) firmly. Solving one thing is better than discussing twelve.
• The Phantom Volunteer: An agent who enthusiastically commits to tasks but never executes them. Track commitments in writing. Follow up within 72 hours. After two non-executions, reassign the task without drama.

Expected Output

The output is not a single event. It is a persistent process: a group of neighbors who know each other's names, have a working communication channel, and have demonstrated the ability to coordinate on at least one issue. This process, once running, can be applied to future issues with significantly reduced startup cost.