Facebook Groups as Coordination Layers
Regular group members see normal Facebook content. Responders see structured workflows — needs tagged by NUMO state, urgency, and type. The coordination layer is invisible infrastructure running on top of existing community behavior.
Community Posts Normally
Members post in their Facebook Group as usual. No new apps, no onboarding. The group remains a familiar social space.
OIQ Tags in Background
The coordination layer reads public posts and applies NUMO state, urgency, and need-type tags — structured signal extracted from natural language.
Responders See Structure
Trained responders access the coordination dashboard. They see the same posts filtered, prioritized, and tracked. Fulfillment is logged without disrupting the group.
Facebook Group activity — structured by NUMO state, invisible to regular members
Elderly neighbor at 4th & Maple needs evacuation assistance. She cannot walk without help and has two cats. Anyone near NW side?
Westside shelter has capacity for 40 more people. Blankets, cots, and meals available. Pets welcome in designated area.
Insulin needed urgently — power outage means refrigeration lost. Looking for anyone who can donate or find a pharmacy that's open.
Need 10 volunteers to help with food distribution at Lincoln Park starting 2pm. Bring gloves if you have them.
Running low on canned goods and baby formula. Accepting donations at 220 Grove St until 6pm today.
Why Facebook Groups?
Communities already coordinate in Facebook Groups. Thousands of neighborhood mutual aid networks, emergency response teams, and local support circles live there. The barrier to entry is zero — people already know how to use it.
Instead of asking communities to adopt new tools, OIQ adds a coordination layer on top of what already exists. The group stays a group. The infrastructure becomes invisible.
NUMO state tagging maps each post to one of ten discrete states in the Cauldron kernel — giving responders a shared language for need severity, resource availability, and resolution status.
RUBIC boundary discipline ensures every action is reversible and logged. No post is acted on without a record. No fulfillment is marked without accountability.