Skip to content

Bush

Every Filipino has pointed at a potholed road or a flood drain that was never finished — and known, without proof, that something was wrong.

Core trick

Runs rule-based anomaly flags on procurement records, then has an LLM argue the strongest innocent explanation before issuing a verdict per contract.

Tags

Description

Every Filipino has pointed at a potholed road or a flood drain that was never finished — and known, without proof, that something was wrong. Proving it has always required a lawyer, a journalist, or months of reading government documents nobody has time to read. Bantay reads the entire Philippine government's infrastructure procurement dataset — 248,220 contracts, ₱6.4 trillion committed — and flags four kinds of anomaly: ghost projects marked 100% complete, contractors winning over 40% of a region's work in a single category, contractors whose licenses have been revoked, and timelines that do not survive arithmetic. For 216 contracts in our Rizal pilot, Claude Opus 4.7 takes over as the analyst. It writes a verdict on each — but first it argues against itself, drafting the strongest non-anomalous explanation a contractor's lawyer could mount, then checking whether the data actually supports it. About one in eight contracts gets downgraded by this self-correction. The rule engine cites four laws; Opus cites six to eight per contract — specific sections of the Philippine procurement law, state audit circulars, and board resolutions — in plain language a citizen can act on. Filipinos already have voice. Bantay gives them the receipts.

The linked repo returns 404, so it was deleted or made private.

Team