What to click, and what to look for.

Keep this page open beside the demo. Every step below is one thing to do and one thing to notice.

Act 1 · One pothole, start to end 5 minutes

Follow one real report from a resident's words to a fixed road.

1. Open the Command Centre and sign in as Aishah. You land on the Worklist — a full morning of work, in the order it should be done, not the order it arrived.
2. Open the pothole case at the top. Her own words are kept in Malay, exactly as she wrote them. Nobody rewrote the resident.
3. Look at "4 reports". Four neighbours reported the same pothole. They are joined into one job — but all four are still there, whole, underneath. Nothing was deleted.
4. Look at the routing. The system names a person and says why: who is nearest, who is free. It proposes. The officer confirms.
5. Look at the Record on the right. Every step so far, in order. Lines can only be added, never edited away.
6. Open the Field App and sign in as Faizal. The same job is now on the crew's phone.
7. Tap the job, change the status, then Close job. A job is closed with a photo and a remark, not a tick box. That is the proof the council keeps.
8. Go back to the case in the Command Centre. The Record grew. Faizal's words and his photo are on it.

Act 2 · A storm 2 minutes

One report is easy. A rainy morning across the whole city is the real job.

1. Look at the whole Worklist. 20 reports and sensor alarms came in that morning. 4 real problems came out. 4 were refused — spam, or another council's street.
2. Open Review. Proposals waiting for a person: "these two look like the same flood — medium confidence." You can accept it, keep them apart, or mark it not real.
3. Notice what it does not do. It never merges on its own. Every group waited for a human yes.

Act 3 · Look inside the box 3 minutes

The honest half: what the machine did, what a person decided, and what a council can change without us.

1. On a case, open Under the hood. The case played back step by step. Where nothing was recorded, it says so instead of filling in a guess.
2. Read the Record in full. 16 entries for this one case. A council can put this in front of an auditor.
3. Sign in again as Ops, then open Administration → Event types & routing. It asks for the password once more (demo) before it lets you in — settings change the council for everyone, so it confirms who you are twice.
4. Read the routing rules. The kinds of problem this council handles, and which department gets each one. Adding the next council is settings, not new code.
5. Administration → Change history. Who changed which setting, and what it was before. Even the settings have a paper trail.
6. Add a report manually. A phone call or a walk-in goes into the same queue. Nothing here needs the resident to own a smartphone.