Public benefit app map
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
A public-benefit operating map
CivicSyn can coordinate the public-facing and partner-safe parts of the broader public-benefit app suite: benefits navigation, legal help, mutual aid, housing rights, worker rights, mobility, environmental health, procurement, public records, and more.
The boundary is deliberate: CivicSyn receives public, aggregate, partner-scoped, or explicitly referred signals. Private casework stays in the app built for that case unless a tenant-approved workflow says otherwise.
How to read the map
- Companion appA standalone app residents or operators can use directly.
- Source adapterPartner-safe operational data can feed CivicSyn workflows.
- Aggregate signalOnly trends or counts cross into public dashboards.
- Private referralPrivate casework stays protected and user/partner controlled.
One coordination language
Every public-benefit domain uses the same CivicSyn spine: need, capacity, resource, allocation, evidence-present status, decision, and outcome. That keeps benefits navigation, grants, records, mutual aid, food, mobility, environment, repair, tools, and freight understandable as one civic system.
Boundary-first design
Cards show whether a flow is public-only, aggregate-only, partner-confidential, private casework, or restricted. Public pages do not promise that CivicSyn performs private casework; they show how public-safe coordination connects to the right service owner.
One CivicSyn cohesion contract
- Every feature uses the same mental model: need, capacity, resource, allocation, evidence, decision, outcome.
- Public-benefit app domains appear as coordinated civic workflows, not unrelated mini-products.
- Public pages show enough detail to build trust without leaking protected operations.
- Protected pages show role-specific detail for partner, node coordinator, incident operator, admin, and auditor work.
- The same entity uses the same name and status language across dashboards, maps, open data, admin, and exports.
- Cross-domain journeys preserve tenant, node, resource, proposal, map, open-data, and public-records context.
- Companion tools are framed by task and data boundary rather than brand clutter.
- AI and agentic features use the same accountability model: draft, evidence, confidence, human review, outcome learning.
- Money and public-procurement features use one transparency model: source, amount, vendor/provider, policy flags, outcome, caveats.
- Emergency and sensitive workflows visibly separate public summaries from restricted operational detail.
Public service directory
Public service-directory pages distinguish public program information from private eligibility or casework.
Eligibility screener: navigation support, not final benefit determination.
What happens next after selecting a program or referral: resident sees the service owner, expected response path, privacy boundary, and support channel.
Program card checklist
- Agency
- Service area
- Eligibility factors
- Deadline
- Documents needed
- Contact channel
- Appeal path
What happens next after selecting a program or referral is shown before private casework begins.
Agency/operator workflow
Agency/operator workflow: queue status, stale referrals, missing documents, deadlines, handoff responsibility.
Denial or appeal flow: deadlines, evidence needs, support options, privacy boundary.
Unmet-need boundary
Private household details are never shown in public dashboards, exports, maps, or governance pages.
Aggregate unmet-need dashboards explain source limitations and avoid ranking people or neighborhoods as deficient.
Funding opportunity cards
- Funder
- Eligibility
- Deadline
- Match requirement
- Award size
- Reporting burden
- Public outcome expectation
Grant-fit screener: assumptions and confidence, not award likelihood.
Funding coordination workflow
Partner work plan: tasks, owner, due date, dependency, document status, submission readiness.
Award dashboard: requested, awarded, obligated, spent, reimbursed, reported funds.
Grant public outcomes
Public outcome views connect grant dollars to civic outcomes without exposing confidential application drafts.
Capacity supported: public, cooperative, nonprofit, or private-provider.
Grant review guardrails
Compliance/deadline warnings are visible before a funding risk becomes urgent.
Grant recommendations disclose policy assumptions, data gaps, and human approval status.
Mutual-aid requests and offers
Mutual-aid requests distinguish urgent, scheduled, recurring, fulfilled, partially fulfilled, cancelled, and private.
- Urgent
- Scheduled
- Recurring
- Fulfilled
- Partially fulfilled
- Cancelled
- Private
Offer cards show resource, location precision, time window, capacity, restrictions, safety notes, and verification status.
- Resource
- Location precision
- Time window
- Capacity
- Restrictions
- Safety notes
- Verification status
Volunteer handoff safety
Handoff flows protect recipient identity and exact address until the appropriate trusted step.
Volunteer dashboards show commitments, next action, route/safety caveats, no-show reporting, and support path.
Safety reporting is visible, low-friction, and does not penalize people for reporting unsafe conditions.
Mutual-aid matching
Matching explanations show fit, distance, time window, capacity, and reason for non-match.
- Fit
- Distance
- Time window
- Capacity
- Reason for non-match
Empty states invite partner onboarding, volunteer signup, and public-safe waitlist/need reporting.
Public impact boundary
Public impact dashboards aggregate help delivered without exposing vulnerable people or exact addresses.
CivicSyn treats mutual aid as safety-aware coordination: public dashboards can show fulfilled help, unmet capacity, and waitlist signals while private recipient details remain protected.
Environmental dashboards
Environmental dashboards distinguish sensor readings, resident reports, inspection data, partner capacity, and public-health indicators.
- Sensor readings
- Resident reports
- Inspection data
- Partner capacity
- Public-health indicators
Risk cards explain threshold, source, last update, geography, confidence, and recommended public action.
- Threshold
- Source
- Last update
- Geography
- Confidence
- Recommended public action
Environmental public guidance
Water and air views avoid medical claims and direct residents to official public-health guidance when needed.
Energy/resilience pages show resource availability, eligibility or referral path, facility capacity, outage context, and safety caveats.
Environmental maps and exports
Environmental maps show aggregation level and avoid exposing private homes or sensitive infrastructure locations.
Public exports include source, method, validation status, and limits of interpretation.
Environmental incident boundary
Incident mode clearly distinguishes routine environmental monitoring from emergency response.
Empty states explain whether sensors/partners are not onboarded, data is stale, or public release is restricted.
Shared assets and reservations
Shared-asset cards show item/tool type, availability, reservation status, condition, location precision, responsible partner, and safety requirements.
- Item/tool type
- Availability
- Reservation status
- Condition
- Location precision
- Responsible partner
- Safety requirements
Reservation flows explain hold duration, conflict risk, cancellation, audit reference, and next action.
Repair work and partner queues
Repair work orders show issue type, urgency, crew/material need, inspection status, resident-facing status, and privacy boundary.
Public repair dashboards aggregate demand and outcomes without exposing vulnerable households or exact private addresses.
Partner dashboards show what is assigned, blocked, missing material, awaiting inspection, or failed.
Freight and cooperative logistics
Freight/logistics views show capacity, vehicle type, route constraints, time window, labor/handling needs, and failure evidence.
Freight fairness metrics explain provider mix, local/co-op share, delivery outcomes, and data limitations.
Cross-domain repair logistics
Cross-domain flows connect shared assets, repair crews, freight, food, shelter, and incident needs without forcing users to understand internal app boundaries.
CivicSyn keeps the public-facing flow understandable even when the underlying work involves tools, repair crews, vehicles, kitchens, shelters, procurement, and incident rooms.
Domains covered
- access to justice1 coordination domain
- care2 coordination domains
- community1 coordination domain
- consumer protection1 coordination domain
- education1 coordination domain
- environment1 coordination domain
- funding1 coordination domain
- health1 coordination domain
- housing2 coordination domains
- human services1 coordination domain
- incident1 coordination domain
- infrastructure1 coordination domain
- labor1 coordination domain
- mobility2 coordination domains
- procurement1 coordination domain
- resilience1 coordination domain
- transparency1 coordination domain
Next pilot step
A tenant can activate a scoped domain, connect OSS companion systems or internal apps, set data-sharing boundaries, and publish only public-safe summaries.
Public-benefit app domains
housing · operational_sensitive
Housing repair crews and material logistics
Coordinate repair requests, crew capacity, material inventory, inspections, and public-safe status for housing stabilization work.
Resident problem: urgent habitability repair, weatherization, accessibility repair, post disaster damage repair need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate crew hour, inspection slot, repair material, vehicle hour, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: repair_request_to_crew_capacity_to_material_reservation
Public data boundary: operational sensitive. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
RateMyLandlord
aggregate signal · aggregate only · planned
Landlord and building pattern signals can inform public-safe housing risk dashboards without exposing tenant identities.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
RepairHub
source adapter · partner confidential · planned
Repair crews, materials, and work-order capacity can feed repair allocation planning.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
RentGuard
private case referral · private casework · planned
Tenant casework stays private; CivicSyn can use aggregate eviction and habitability demand signals.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
AccessMap
aggregate signal · aggregate only · planned
Accessibility barrier reports can prioritize repair and public works response.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
care · personal_data
Childcare capacity and subsidy coordination
Track childcare slot capacity, subsidy demand, provider eligibility, transportation needs, and public waitlist pressure without exposing child-level records.
Resident problem: infant slot need, after school care, emergency childcare, subsidy support need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate childcare slot, staff hour, transport slot, subsidy dollar, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: family_need_to_provider_slot_to_subsidy_review
Public data boundary: personal data. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
BenefitsNav
private case referral · private casework · planned
Family eligibility and subsidy work remains private; aggregate childcare subsidy pressure can inform planning.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
CareCoord
source adapter · partner confidential · planned
Care capacity and referral status can feed node-level coordination.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
GovNavigator
companion app · public only · planned
Program directories and public agency navigation can be shared as public-facing guidance.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
KidSafe
private case referral · restricted · planned
Child-safety workflows stay restricted; only aggregate service gaps should feed public dashboards.
Boundary owned: restricted. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
care · personal_data
Eldercare visit capacity and supply coordination
Coordinate eldercare visit capacity, wellness-check demand, mobility supports, medical supply handoffs, and caregiver availability with privacy-preserving aggregation.
Resident problem: wellness check, home visit, caregiver relief, mobility support need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate caregiver hour, wellness check slot, mobility supply, meal, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: aggregate_visit_need_to_caregiver_capacity_to_supply_handoff
Public data boundary: personal data. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
CareCoord
source adapter · partner confidential · planned
Care visit capacity and referral statuses can be summarized by node.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
AidNet
companion app · partner confidential · planned
Aid requests and volunteer capacity can feed privacy-preserving eldercare coordination.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
NeighborNet
aggregate signal · aggregate only · planned
Neighbor check-in capacity can inform wellness support planning.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
MealShare
source adapter · partner confidential · planned
Meal support capacity can link to eldercare and wellness-check needs.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
incident · restricted_incident_data
Emergency shelter and disaster relief
Coordinate shelter capacity, supplies, assessments, transportation, incident rooms, and after-action reporting during emergencies.
Resident problem: shelter need, evacuation support, supply shortage, meal need need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate shelter bed, meal, water, blanket, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: incident_assessment_to_shelter_capacity_to_resource_allocation
Public data boundary: restricted incident data. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
AidNet
source adapter · partner confidential · planned
Aid requests, volunteer capacity, and relief supplies can feed incident response rooms.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
MealShare
source adapter · partner confidential · planned
Emergency meal capacity can connect to shelter and relief allocations.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
CivicPulse
aggregate signal · public only · planned
Public sentiment and response feedback can inform after-action reporting.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
health · operational_sensitive
Medicine and health supply logistics
Coordinate program stock, requisitions, cold-chain logs, shipment status, clinic demand, and public-health indicators.
Resident problem: stockout risk, clinic supply request, cold chain exception, public health indicator gap need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate medicine, medical supply, cold chain slot, clinic staff hour, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: clinic_need_to_program_inventory_to_requisition_and_shipment
Public data boundary: operational sensitive. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
MedCompare
aggregate signal · aggregate only · planned
Health access and availability patterns can inform public-health logistics without sharing medical records.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
CareCoord
source adapter · partner confidential · planned
Care and clinic coordination signals can connect with supply-chain workflows.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
BenefitsNav
private case referral · private casework · planned
Coverage and benefit-navigation cases remain private; aggregate coverage gaps can inform support capacity.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
infrastructure · operational_sensitive
Public works requests and crew capacity
Coordinate public works requests, crew availability, equipment, material inventory, weather constraints, and resident-facing status updates.
Resident problem: street repair, tree blockage, storm drain issue, snow response need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate crew hour, equipment hour, repair material, traffic control slot, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: public_request_to_crew_capacity_to_work_order_outcome
Public data boundary: operational sensitive. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
RepairHub
source adapter · partner confidential · planned
Repair work orders and crew capacity can feed public works coordination.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
GovNavigator
companion app · public only · planned
Public agency directories help residents and partners find the right public works channel.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
RightToKnow
companion app · public only · planned
Records requests and disclosure logs can connect public works decisions to transparent evidence.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
CivicPulse
aggregate signal · public only · planned
Resident feedback can prioritize visible public works bottlenecks.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
mobility · operational_sensitive
Transit bottleneck reporting
Aggregate transit bottleneck reports, service disruptions, accessibility barriers, route capacity, and public-safe response status.
Resident problem: delay hotspot, accessibility barrier, missed connection, maintenance need need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate vehicle hour, operator hour, accessible trip slot, maintenance slot, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: resident_and_operator_signal_to_route_bottleneck_to_response_plan
Public data boundary: operational sensitive. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
TransitIQ
source adapter · public only · planned
Transit bottleneck signals can support public-safe mobility dashboards.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
AccessMap
source adapter · public only · planned
Accessibility barriers can be mapped and routed into public response workflows.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
FreightFair
aggregate signal · aggregate only · planned
Freight fairness and delivery constraints can inform local logistics capacity.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
resilience · operational_sensitive
Energy resilience resources
Coordinate backup power, cooling/heating centers, battery inventory, outage support, and resilience resources during normal and emergency operations.
Resident problem: outage support, cooling need, warming need, medical device power need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate battery, generator hour, cooling center slot, warming center slot, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: outage_or_heat_need_to_resilience_resource_to_public_safe_status
Public data boundary: operational sensitive. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
EnergyAudit
source adapter · partner confidential · planned
Energy burden and resilience assessments can inform resource allocation.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
CleanAir
aggregate signal · public only · planned
Air-quality and heat-risk signals can connect to resilience hub planning.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
WaterWatch
aggregate signal · public only · planned
Water-quality and outage signals can inform resilience support.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
procurement · partner_confidential
Cooperative vendor marketplace
Coordinate public/cooperative vendors, local capacity, labor standards, open-books procurement, anti-extraction policy, and public-money retention.
Resident problem: public procurement need, local vendor gap, coop capacity offer, labor standard review need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate vendor capacity, labor hour, service contract, local supply, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: public_need_to_vendor_capacity_to_procurement_and_outcome_record
Public data boundary: partner confidential. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
GovGrants
companion app · partner confidential · planned
Grant opportunities and award tracking can connect to public-money outcome reporting.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
FreightFair
source adapter · partner confidential · planned
Delivery and freight constraints can inform cooperative vendor feasibility.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
ToolLibrary
aggregate signal · aggregate only · planned
Shared tool and asset availability can support local provider capacity.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
access_to_justice · personal_data
Legal self-help and rights navigation
Coordinate legal issue triage, guided document bundles, hearing deadlines, rights referrals, public patterns, and support capacity while keeping attorney-client and case details private.
Resident problem: eviction response, benefits denial, debt dispute, workplace rights need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate document template, deadline reminder, legal referral slot, case note, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: legal_issue_to_guided_document_to_deadline_tracking
Public data boundary: personal data. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
LegalDocs
private case referral · private casework · planned
Guided legal documents stay in case workflows; public outputs are aggregate need and capacity signals.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
DisputeKit
private case referral · private casework · planned
Consumer, debt, and benefits dispute packets remain private unless the user chooses disclosure.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
DenialFighter
private case referral · private casework · planned
Denial and appeal workflows can feed aggregate policy-friction metrics.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
WorkRights
private case referral · private casework · planned
Worker rights cases stay private; aggregate issue patterns can guide outreach.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
RentGuard
private case referral · private casework · planned
Housing rights casework stays private while aggregate habitability and eviction pressure can be surfaced.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
IEP Tracker
private case referral · private casework · planned
Education accommodations and family records stay private; only aggregate deadline and support gaps are shared.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
transparency · public
Public records access and transparency
Coordinate public-records requests, agency directories, deadline tracking, response status, disclosure logs, and public-safe transparency dashboards.
Resident problem: records request, appeal deadline, agency nonresponse, procurement record need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate records request, deadline reminder, agency contact, disclosure record, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: records_request_to_deadline_to_disclosure_log
Public data boundary: public. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
RightToKnow
companion app · public only · planned
Records requests, deadlines, appeals, and disclosure logs can power public transparency workflows.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
CivicPulse
aggregate signal · public only · planned
Public comment and sentiment can guide records priorities and transparency review.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
GovNavigator
companion app · public only · planned
Agency directories and service explainers support public-records routing.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
community · partner_confidential
Mutual aid and neighborhood support
Coordinate neighbor support offers, verified needs, volunteer capacity, meal support, tool access, safety-aware routing, and public-safe community impact.
Resident problem: meal support, errand support, tool access, safe route support need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate volunteer hour, meal, tool, ride support, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: resident_need_to_neighbor_capacity_to_verified_handoff
Public data boundary: partner confidential. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
AidNet
source adapter · partner confidential · planned
Aid requests and offers can feed privacy-preserving community coordination.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
NeighborNet
aggregate signal · aggregate only · planned
Neighborhood support capacity can be summarized by node.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
MealShare
source adapter · partner confidential · planned
Meal support capacity can connect to local need and allocation workflows.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
ToolLibrary
aggregate signal · aggregate only · planned
Shared tools can become resource capacity for repair and resilience pilots.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
SkillSwap
aggregate signal · aggregate only · planned
Volunteer and skill capacity can support community response without exposing private member profiles.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
funding · partner_confidential
Public grants and community funding coordination
Coordinate grant opportunities, eligibility screening, application work plans, award status, procurement links, and public outcome reporting.
Resident problem: funding gap, application support, match requirement, award tracking need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate grant program, application slot, matching fund, technical assistance hour, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: funding_opportunity_to_partner_capacity_to_award_outcome
Public data boundary: partner confidential. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
GovGrants
companion app · partner confidential · planned
Grant search, eligibility, and award tracking can feed public funding transparency.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
GovNavigator
companion app · public only · planned
Agency and program directories help partners find public funding channels.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
CivicPulse
aggregate signal · public only · planned
Public priorities can guide participatory funding and grant-review workflows.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
housing · personal_data
Housing rights and habitability coordination
Coordinate tenant-rights referrals, habitability repair needs, landlord pattern signals, inspection capacity, and public-safe housing stabilization metrics.
Resident problem: eviction risk, habitability repair, accessibility repair, rent dispute need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate inspection slot, legal referral slot, repair material, crew hour, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: housing_issue_to_rights_referral_to_repair_or_enforcement_path
Public data boundary: personal data. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
RentGuard
private case referral · private casework · planned
Tenant cases stay private; aggregate housing-pressure metrics can guide intervention.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
RateMyLandlord
aggregate signal · aggregate only · planned
Landlord pattern signals can support public-safe accountability dashboards.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
RepairHub
source adapter · partner confidential · planned
Repair capacity can connect rights cases to stabilization work.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
LegalDocs
private case referral · private casework · planned
Guided notices and court documents remain private unless published by user choice.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
labor · personal_data
Worker rights and job-quality coordination
Coordinate worker-rights referrals, wage theft signals, unsafe workplace reports, job-quality transparency, training capacity, and public-safe enforcement patterns.
Resident problem: wage theft, unsafe workplace, misclassification, benefits gap need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate legal referral slot, training slot, case note, job quality signal, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: worker_issue_to_referral_capacity_to_public_pattern
Public data boundary: personal data. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
WorkRights
private case referral · private casework · planned
Worker-rights casework stays private while issue patterns can guide outreach and enforcement capacity.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
JobTruth
aggregate signal · aggregate only · planned
Job-quality pattern signals can support public accountability without naming private workers.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
LegalDocs
private case referral · private casework · planned
Employment document bundles and deadline reminders stay in private workflows.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
BenefitsNav
private case referral · private casework · planned
Benefit and safety-net linkages can support workers after job loss or wage theft.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
mobility · operational_sensitive
Mobility, accessibility, and safe routes
Coordinate transit bottlenecks, safe-route reports, accessibility barriers, freight and delivery constraints, and public-safe maps for essential trips.
Resident problem: accessibility barrier, unsafe route, delivery constraint, missed connection need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate accessible trip slot, safe route segment, vehicle hour, operator hour, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: route_signal_to_access_barrier_to_response_capacity
Public data boundary: operational sensitive. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
TransitIQ
source adapter · public only · planned
Transit performance and bottleneck signals can feed public maps.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
AccessMap
source adapter · public only · planned
Accessibility reports can power public-safe service-area and barrier maps.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
FreightFair
aggregate signal · aggregate only · planned
Freight and delivery constraints can inform essential-service logistics.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
environment · operational_sensitive
Environmental health and resilience signals
Coordinate air, water, energy, plant-health, and resilience signals with public-safe dashboards, response capacity, and open-data exports.
Resident problem: air quality concern, water quality concern, energy burden, heat risk need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate sensor signal, inspection slot, resilience resource, public export, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: environment_signal_to_public_health_context_to_response_capacity
Public data boundary: operational sensitive. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
CleanAir
aggregate signal · public only · planned
Air-quality reports can connect to resilience, public-health, and open-data dashboards.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
WaterWatch
aggregate signal · public only · planned
Water-quality signals can inform public health and emergency supply planning.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
EnergyAudit
source adapter · partner confidential · planned
Energy burden and audit data can feed resilience programs with privacy controls.
Boundary owned: partner confidential. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
GreenScore
aggregate signal · public only · planned
Sustainability and local environmental metrics can inform public dashboards.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
PlantDoc
aggregate signal · aggregate only · planned
Plant-health and urban agriculture signals can support food-security resilience.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
consumer_protection · personal_data
Consumer protection and household cost defense
Coordinate household-bill decoding, dispute kits, price-watch signals, account-freeze guidance, privacy requests, and public-safe market pattern reporting.
Resident problem: bill dispute, price gouging, debt collection, privacy request need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate document bundle, deadline reminder, price signal, privacy request, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: consumer_issue_to_document_or_dispute_workflow_to_pattern_signal
Public data boundary: personal data. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
BillDecode
private case referral · private casework · planned
Household bill reviews remain private while aggregate fee and billing patterns can be surfaced.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
DisputeKit
private case referral · private casework · planned
Dispute workflows stay private; aggregate issue categories can guide enforcement.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
FairPrice
aggregate signal · aggregate only · planned
Price fairness signals can identify market stress and public procurement risks.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
PriceWatch
aggregate signal · public only · planned
Public price-watch signals can support household cost dashboards.
Boundary owned: public only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
FreezeFlow
private case referral · private casework · planned
Account-freeze and credit-protection steps remain user-controlled and private.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
DataPurge
private case referral · private casework · planned
Data deletion and privacy requests remain user-controlled; aggregate friction can inform policy.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry
education · personal_data
Education rights and student-support coordination
Coordinate education-rights referrals, IEP and accommodation timelines, tutoring capacity, family document bundles, and aggregate student-support gaps.
Resident problem: iep timeline, accommodation request, tutoring need, benefits linkage need a clear public path without turning CivicSyn into private casework.
Partner workflow: partners coordinate advocacy slot, document bundle, deadline reminder, tutoring slot, service capacity, evidence-present status, allocations, and outcomes.
Pilot status: not yet activated for this tenant. Missing or restricted data is shown as a boundary, not hidden as a blank card.
Coordination model: student_support_need_to_advocacy_or_service_capacity_to_outcome_tracking
Public data boundary: personal data. CivicSyn coordinates public, aggregate, partner-safe, or referred signals; detailed private casework remains in the system built for that service.
-
IEP Tracker
private case referral · private casework · planned
IEP, accommodation, and student records stay private while aggregate deadline pressure can inform support capacity.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
StudyBuddy
aggregate signal · aggregate only · planned
Tutoring and learning-support capacity can feed public-safe student support planning.
Boundary owned: aggregate only. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
LegalDocs
private case referral · private casework · planned
Education-rights documents and deadlines stay private to the household.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
-
BenefitsNav
private case referral · private casework · planned
Student and family benefit linkages remain private while aggregate unmet-need signals inform support.
Boundary owned: private casework. Freshness/import status: planned; unavailable, stale, unauthorized, or not configured companion tools should be labeled before operators rely on them.
Public dashboard Partner onboarding Records path Pilot inquiry