Source and OSS provenance
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
Public-benefit source posture
CivicSyn is built with civic commons obligations in mind.
Plain-language source summary: this page explains what CivicSyn reuses, what obligations come with those references, and where public notices live without exposing private operational details.
CivicSyn accepts reciprocal/source-availability obligations for approved AGPL, GPL, EPL, and civic/cooperative OSS references. Reference assets are copied through a provenance tool, notices are preserved, and CivicSyn-native implementations are built on Cloudflare Workers, D1, R2, Queues, and Durable Objects.
Reference bundle
Copied reference assets live under workers/products/app-099-civicsyn/reference with checksums and source commits recorded in COPY_PROVENANCE.json.
Approved families
CKAN, Decidim, CONSUL, FIWARE, OpenFisca, OpenLMIS, OpenFoodNetwork, PostGIS, CoopCycle, Metabase, and OpenBoxes are approved for obligation-aware CivicSyn use.
Boundary
This is not a surveillance or black-box optimization system. Public users get source/provenance transparency; private operational evidence remains protected.