How CivicSyn works
Every domain CivicSyn coordinates — food, repairs, care, energy, transit — runs the same public loop: partners report what is real, the system compares options in the open, people decide with reasons, work gets executed and acknowledged, and the record stays public. Food security is the flagship: the same loop, pointed at keeping shelves stocked.
A worked example from the food domain, end to end.
- SENSE — market price observations put the basket index at 115
- PLAN — a release rule flags rice: index 15% over baseline
- DECIDE — the regional board approves with a written reason
- EXECUTE — reserve stock draws down; shelves restock
- REVIEW — the release, reason, and outcome are public record
1. Report
Partners report needs, capacity, inventory, delivery windows, incidents, and procurement context. Raw evidence stays restricted unless it is safely summarized.
2. Recommend
A deterministic scoring engine compares urgency, distance, perishability, equity, public/co-op/local preference, cost, data quality, and delivery feasibility.
3. Govern
Approvers and public reviewers can accept, reject, object, appeal, or override with reasons. Every final decision has an audit trail.
The same loop runs the reserve
In the food domain, the loop is not an abstraction — it is buffer stocks, floor prices, and releases. Sensing is price observations and coverage positions. Planning is release rules and rotation plans. Deciding is a board approval with a required reason. Executing is a ledger draw that restocks shelves. Reviewing is the public release record.
For residents
Residents see public-safe dashboards, proposal explanations, votes, objections, public records, and after-action summaries without exposing private household or facility details.
For providers
Food banks, kitchens, co-ops, warehouses, clinics, schools, and delivery partners report what they can safely offer and acknowledge assigned allocation work.
For agencies
Agencies can review public-money flows, procurement constraints, incident response, policy simulations, and allocation outcomes before making approvals.
For coordinators
Coordinators get node dashboards, decision-support briefings, DLQ/import replay, recommendation runs, and audit search so operations stay legible.
For auditors
Auditors review decision records, evidence-present markers, procurement context, role-scoped actions, and before/after summaries without needing private case details on public pages.
For public reviewers
Reviewers inspect proposals, objections, votes, appeal status, recommendation explanations, and implementation outcomes so public review is more than a comment box.