Food system coordination
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.
- Current picture: needs, capacity, inventory, delivery windows
- Evidence trail: source, freshness, confidence, audit record
- Public view: aggregate dashboards, maps, exports, outcomes
- Human review: objections, approvals, overrides, follow-through
Active enterprises
Public-safe provider directory for producers, kitchens, food hubs, and buyer groups.
Open coordination cycles
Order and pickup cycles are coordination windows, not retail checkout.
Supply offers
Aggregate available food capacity with freshness, source, and handling constraints.
Food system coordination
Residents and auditors see public-safe supply, need, capacity, cycle, and outcome summaries. Partner-private evidence, household details, non-public coordinator comments, and exact restricted locations are omitted.
- Order and pickup cycles are coordination windows: cutoff time, packing/fulfillment window, pickup or delivery options, and handoff responsibility.
- Food safety, allergens, perishability, prep windows, and cold-chain needs must be reviewed by operators before allocations or partner orders are executed.
- If there are no providers, no active cycles, or no supply offers, the pilot may not be onboarded yet, the current cycle may be closed, or the available data may be private/restricted.
Backend-ready workflows exposed here
This page brings the Open Food Network-style provider/cycle/offer APIs and OpenBoxes/OpenLMIS-style cold-chain risk API into one public route, with protected next actions for partners and operators.
Open Food Network-style provider directory
- If no enterprises appear, no providers may be onboarded, the pilot may not be live, or provider records may be private/restricted.
Food hubs and handoff points
- If no hubs appear, no coordination hub is onboarded, the active hub is paused, or hub details are restricted for the current pilot.
Order and pickup cycles
- If no cycles appear, the current cycle may be closed, not opened yet, completed, cancelled, or restricted from public display.
Supply offers and safety constraints
- If no supply offers appear, no providers may be onboarded, the current cycle may be closed, offers may be sold out/expired, or data may be private.
Cold-chain public risk
The cold-chain dashboard highlights excursions, affected lots, quarantine, and public-safe risk while omitting exact private facility coordinates, logger IDs, corrective details, and evidence storage keys.
- No public cold-chain excursion signal is visible for this tenant.
What operators do next
- Partners report supply offers, OFN imports, inventory, needs, and cold-chain logs from protected workspaces.
- Admins create enterprises, hubs, cycles, pickup windows, and reason-required cycle transitions.
- Public users see only aggregate supply, cycle, and risk context; private evidence remains protected.