Why this happened
Public decisions should show the reason, status, expected outcome, and what evidence categories were considered.
public decisions
Public visitors should see reasons, outcomes, corrections, and appeals. Signed-in reviewers can open the full decision workspace on this same path.
normal user journey
public record boundary
service-portal guidance
CivicSyn should answer the practical questions first: what this page does, what status means, what deadline or process might apply, and how to correct or appeal a public record.
Public decisions should show the reason, status, expected outcome, and what evidence categories were considered.
Public visitors can read, correct, or appeal. Signed-in reviewers use separate workspace controls.
A decision or request status is ready to explain.
The public record states why the path was chosen.
Execution, delay, complaint, or completion status updates the record.
People can Submit correction or File appeal when the record is wrong.
Open related decisions, requests, spending, outcomes, and appeals.
Search public recordmarketplace-style workflow
CivicSyn borrows the good parts of marketplace browsing, request boards, settings panels, and notification preferences, then adapts them for public-safe essential-service journeys.
examples, not promises
These examples explain the journey shape. Actual local status comes from published public records or an authorized workspace.
Why a delivery was rerouted, why a repair was prioritized, or why spend changed.