Karachi's civic problems, fixed by the people who live with them.

Karachi faces millions of small civic problems every day — potholes, broken streetlights, overflowing drains, garbage piling up on sidewalks. Most never get fixed because no one has a way to track whether a complaint actually led to action.

Complaints disappear into helplines and social media posts. There is no public record connecting the problem to the repair. Citizens have no visibility into what happens after they report, and contractors have no easy way to find work that the community already agrees needs doing.

Vaelkor Civic closes that loop — from report to repair, all in public view.

A platform that holds money and photographs has to be right, not just demonstrable. The state machine, the funding arithmetic, the role gates and the claim approval path are covered by an automated suite that runs on every change.

The tests are written against a real Convex backend harness rather than mocks, so the lifecycle, the storage and the authorisation rules are exercised as deployed. The funding tier rules are a pure function with an exhaustive matrix test; the funding gate is tested from both directions, through pledges and through approved claims.

We would rather show you the test count than ask you to trust the demo.

Filing a report takes about 30 seconds on a smartphone. You take a photo of the fault, select a category (road, drainage, garbage, streetlight), and the app captures your location automatically. No account is required to read the ledger, but you need one to submit a report.

Once submitted, the case appears on the public ledger and map. Other users in the area can confirm they see the same problem. After 3 confirmations, the case is verified and a repair fund is opened. Anyone can then contribute toward the estimated cost. When the fund reaches its goal, the case becomes available for contractors to claim.

When a case is verified it is assigned a repair goal automatically. We deliberately use two tiers, not a table of nine: a table of near-identical numbers is a number nobody can hold in their head, and a pledger told "PKR 7,300" has no way to judge whether that is fair. The rule that picks the tier is one sentence, and it is printed on the case.

Drainage and any high-severity case asks for PKR 10,000. Everything else asks for PKR 5,000. Severity is a floor, not a ceiling — a high-severity pothole is not made cheap by being reported as one. An administrator can still adjust a single goal inside a hard ceiling, and the reason is recorded in the audit log.

A pledge is a commitment, not a payment. The platform never moves money. At this stage the ledger records intent, and a passing inspection records that the work was verified as complete.

A case becomes available to contractors once pledges reach 80% of its repair goal. This ensures there is real backing before any work is assigned.

Contractors browse the ledger or map for cases near their area of operation. When they claim a case, they become the sole person authorized to upload before, during, and after photographs. Once the work is done, they submit the evidence and the case moves to an administrator for inspection.

The administrator compares the before and after evidence against a standard checklist. A pass closes the case and records the resolution. A fail returns the case to the contractor with a note explaining what is still outstanding.