// 04 · report

Report an Incident

Neighborhood-level environmental incidents. Every submission is validated, stored in the workspace, and never auto-forwarded to authorities.

validation · zod · 422 on bad input

01 //

Reporting guidelines

what makes a good report

· Be specific: “drain backing up since 6 am”, not “drain issue”.
· Mark approximate location (area level is fine).
· Set severity to match visible impact, and confidence to your certainty.
· Mark test reports as simulated so operators can filter them.

DON’T

· No personal contact details, phone numbers or identities.
· No health diagnoses or medical claims — environmental conditions only.
· No private residential addresses.
· Don’t expect automatic escalation: nothing is auto-filed anywhere.

LIFECYCLE

reported → reviewed → assigned → resolved
(or rejected, with a mandatory reason)

Every transition is validated by the API (409 on impossible jumps) and visible on the Incidents page.

02 //

Where reports go

honest data flow

Stored:this workspace's active backend (local demo DB or DynamoDB in AWS mode), with evidence type, confidence, timestamps and demo flag. It feeds the G (waste) dimension and the rule engine — transparently.

Not stored / not sent: government complaint channels (e.g. Delhi Jal Board) — no approved live integration exists, and the app never claims one was filed. Photo evidence: no S3 workflow configured in demo mode, so uploads are disabled.

03 //

Recent reports

latest 6 · scrollable

No reports yet.

decoding…