Karachi’s streets, fixed by the community.
Karachi’s streets need fixing. Report a fault, get it confirmed by neighbours, and see it completed with before-and-after photos. Every step is recorded for transparency. Whether it’s a broken streetlight, a clogged drain, or a pothole, we make sure it gets fixed.
No account needed to read the ledger. Reporting takes a photo and a location.
The chain of custody
- 01ReportedA citizen documented the problem
- 02VerifiedEnough independent confirmations to act
- 03AssignedAn executor accepted the work order
- 04In progressWork is underway on site
- 05ClosedCompletion proved and inspected
Karachi, Pakistan · 15 million citizens
From the ledger
Who does what
Report a fault with a photo, confirm reports from other people, add more evidence later, post to the Civic Network.
Cannot Accept work orders or close a case.
Accept open work orders, file before and after photographs, submit completion for review.
Cannot Confirm reports or decide an inspection.
Compare before and after evidence against a checklist, then pass or fail each case.
Cannot Accept work or file execution evidence.
Why a case can be trusted
- A report needs a photographNo image, no case. The first photograph is part of the record, not an attachment to it.Rule 1.
- Three people confirm before work is orderedA case becomes actionable at 3 independent confirmations, and one person can only confirm once.Rule 2.
- Confirmations freeze once work startsThe moment a work order exists the count locks, so a popular case cannot be inflated into urgency.Rule 3.
- Only the assigned contractor can file proofBefore and after evidence is rejected from anyone who does not hold that specific work order.Rule 4.
- Nothing closes without an inspectorCompletion moves a case to inspection, never to closed. An inspector records the decision, and cannot file the work evidence they are judging.Rule 5.
Civic Network
The Civic Network is the public accountability layer of VAELKOR CIVIC. Citizens post what they see — problems, updates, observations — and neighbours confirm they are affected too. Every post is public, every confirmation counts once per person, and posts linked to cases show live status, work orders, and before/after evidence.
Report → Post → Community → Verification → Work Order → Progress → Resolution.
This is not a social network. It is a civic operating system with a social layer — built for infrastructure, not engagement.
What the network does
- Post civic issues, updates, or observations
- Attach photos as evidence
- Link posts to existing ledger cases
- Confirm “I’m affected too” — one per person
- Comment with local knowledge
- See live case status, work orders, and proof
- Browse Civic Pulse for community-wide analytics
The repair fund
A fund goal is written in the same transaction that opens the work order — not before it, and never editable by the person who wants the money. The tier comes from the fault: drainage, or anything filed as high severity, asks for PKR 10000; everything else asks for PKR 5000.
Anyone can put in between PKR 1 and PKR 500 by bank transfer, Easypaisa, or JazzCash. A pledge is not a contribution: the money is transferred, the receipt is filed, and an administrator credits it. Claims against a fund are approved by an administrator too, and a rejected claim leaves the total untouched.
The point is not charity. It is that a repair nobody funds is a repair nobody does, and a fund with no claim process is a donation box.
A funded case, live
Your location
Reporting a fault necessarily involves a place. It does not necessarily involve your address, and it never involves handing your phone’s raw position to a server.
Your raw GPS reading stays in a browser variable and is never uploaded.
The pin stored on a case is randomly shifted by up to 250 m, so it points at the fault, not at your door.
“Cases near me” searches from a point shifted by up to 1500 m. The distances you see are still measured from your real position, on your device.
The fair objections
- Isn’t this just a feed for potholes?
- A post is not a case and carries no status of its own. A case exists only with a photograph attached, and it becomes actionable at three confirmations from three different people. Everything else on the network is conversation; only the ledger is a record.
- What stops one person manufacturing urgency?
- One confirmation per person per case, and the count freezes the moment a work order exists. A popular case cannot keep collecting signatures after the work has already been ordered, so there is nothing left to inflate.
- A contractor can just declare a repair finished.
- Completion can only move a case to inspection. An administrator passes or fails it against a checklist, and cannot inspect their own work. A pass additionally requires before and after photographs filed by the contractor who holds that work order — so the person being judged cannot supply the proof that judges them.
- What if the repair is bad and they keep re-sending it?
- A failed inspection sends the case back to the contractor rather than closing it, and the loop is bounded at three attempts. After that the case stops cycling and needs an administrator, which is the point at which a human being is unavoidable.
- Why would any government actually open this?
- Because the ledger costs them nothing to publish and settles an argument they currently lose. Case numbers are permanent and nothing is deleted from the record, so a department that ignores a case cannot make it disappear — it can only be visibly late.
Start
Read the ledger without an account. File a report when you see something wrong — it takes a photo.