What happened
According to the Lowy Institute, a citizen-built dashboard called Nemesis, developed by Indonesian AI engineer Abil Sudarman, scanned publicly available procurement plans and flagged multiple items that prompted viral public outrage. Lowy Institute reports the dashboard highlighted a billiard table budgeted at Rp400 million, an aquarium at Rp100 million, ornamental plants totalling Rp1 billion, and a Range Rover purchase exceeding Rp8 billion. Lowy Institute further reports Nemesis flagged a Rp22 billion cleaning services contract for the Al Jabbar Grand Mosque in West Java, and that West Java Governor Dedi Mulyadi responded by publishing the detailed contract data, which showed the amount covered management of a sprawling complex rather than routine cleaning. Lowy Institute notes Nemesis draws on the national procurement database of roughly three million rows annually and that the tool currently accesses procurement plans, not realised expenditure data. Lowy Institute reports the developer acknowledged the project is still in early stages and has limited access to contextual or realisation records.
Editorial analysis - technical context
Industry context: Civic procurement scanners like Nemesis typically rely on title-based heuristics and pattern detection over large, public procurement feeds, which makes them effective at surfacing anomalies quickly but also vulnerable to false positives when metadata and context are sparse. For practitioners, this pattern highlights recurring data engineering challenges: inconsistent item descriptions, missing line-item semantics, lack of links to invoices or delivery records, and complex entity resolution across agencies. Natural language heuristics tuned to spot large numbers in titles can produce many high-visibility alerts that require manual triage.
Context and significance
Industry context: The Nemesis episode illustrates the trade-off between rapid civic oversight and the need for richer provenance and reconciliation pipelines. Observers of similar projects note that public impact grows faster than backend data maturity, creating reputation and governance risks for civic tech efforts. For data scientists and engineers, the main takeaway is that signal-to-noise in civic datasets is as much a product-design problem as an algorithm problem, especially when outputs circulate on social media and prompt official responses.
What to watch
For practitioners: indicators to follow include whether Nemesis or other civic scanners gain access to contract realisation records or invoice-level data, whether governments publish machine-readable context fields for large contracts, and how civic projects implement feedback loops to reduce false positives. Observers should also watch for policy or procurement-data governance changes that mandate richer metadata or API access, because those shifts materially affect the value and reliability of automated procurement monitoring.
Key Points
- 1Citizen scanners can surface procurement waste quickly, but title-based heuristics often generate high-profile false positives without richer contract metadata.
- 2Public procurement feeds commonly lack invoice linkage and realisation data, making automated anomaly detection brittle and prone to misinterpretation.
- 3For practitioners, investment in data provenance, reconciliation pipelines, and human-in-the-loop triage reduces false alarms and improves civic-tech credibility.
Scoring Rationale
Relevant to ML and data-practitioners because it highlights practical data-quality and NLP challenges in civic applications. The story is notable for governance implications rather than technical novelty.
Sources
Public references used for this report.
Practice interview problems based on real data
1,625 SQL & Python problems across 15 industry datasets — the exact type of data you work with.
Try 250 free problems
