Launch a local pilot
CivicSyn is public/cooperative coordination infrastructure for essential goods and services. Local nodes coordinate demand, capacity, inventory, delivery, funding, and governance. The system recommends; people decide; every decision leaves evidence.
The first domain connects kitchens, food banks, delivery partners, agencies, co-ops, and public reviewers around transparent allocation decisions.
- D1: current operational truth
- R2: raw evidence and public exports
- Queues: ingestion, recommendations, audit
- Durable Objects: locks, incidents, workflows
Launch phase
Northern Virginia Food Coordination Pilot
Readiness checks
Public-safe launch checklist based on live registry and transparency data.
Active operations
Open needs plus active allocations currently visible to the coordination layer.
Pilot readiness checklist
- Active coordination nodes 2 / 1 · ready
- Approved partners 0 / 3 · needs work
- Active facilities 1 / 1 · ready
- Resource catalog entries 1 / 1 · ready
- Active data sources 0 / 1 · needs work
- Published dashboards 0 / 1 · needs work
- Published exports 2 / 1 · ready
- Public review proposals 0 / 1 · needs work
What a first pilot needs
- One regional tenant with clear governance and data-classification rules.
- Three to ten providers: kitchens, warehouses, shelters, clinics, food banks, delivery partners, or agencies.
- At least one public dashboard, one public export, and one public review path for recommendations.
- CivicSyn native auth, D1, R2, queues, and Durable Objects configured before production launch.
Current pilot shape
- Tenant type: pilot
- Region key: not configured
- Sector strategy: food_security_full_civic_stack
- Status: active
Start here
CivicSyn pilots should begin as accountable coordination infrastructure, not a black-box optimization project. The system can recommend; local operators, partners, and public reviewers decide.