FMR archive · NEP and HGAB project schedules

Disclaimer. This site is updated as additional source documents are ingested and reviewed. Its records and calculations are preliminary and open to correction. Additional documents, stakeholder input, and independent review can surface missing information, errors, or context and improve accuracy over time; they may support more complete calculations but do not by themselves verify a record. Inviting people to examine the underlying sources and share corrections is part of the purpose of this work. These are preliminary, document-based observations, not allegations or findings that any person, office, contractor or other entity acted unlawfully. A flag, unmatched record, repeated amount or title, price or location outlier, or missing document is a prompt for review; it does not establish intent, responsibility, benefit, overpayment, duplicate scope or wrongdoing. Names and geographic or district associations indicate possible coverage only, not sponsorship, authorship, control, receipt or personal involvement. Source documents, data completeness, parsing, matching, categories, timing and boundaries may affect results. Verify cited primary records and seek relevant context before drawing or publishing conclusions.

DA locally-funded FMR annex · FY2027

964HGAB project allocations

₱19.6281Baudited project-ledger total

NEP proposal704 projects · ₱16B

Net allocation adjustment+₱3.6281B

Printed STA length evidence3 / 964 projects

Coordinate review2 HGAB · 0 NEP rows

Same FMR annex text in locally named 2nd/3rd copies; not authentication of the entire bill. Allocations are proposals, not payments.

Corrected FMR coverage and source integrity

The previous parser recovered 795 rows carrying ₱14.035375B. The corrected ledger contains 964 project rows carrying ₱19.6281B: 169 more recovered occurrences and ₱5.592725B of additional extracted allocations. This is a parser correction, not a new budget-stage increase. The NEP annex contains 704 projects carrying ₱16B. Our bounded comparison independently found matching FMR annex text on PDF pages 667–726 after removing InDesign production-footer timestamps; all other content was retained.

Latitude/longitude normalization is not construction-length extraction. Straight-line distances cannot establish measured road alignment or paid scope. The cost-per-meter page now includes separately labeled approximate rates using endpoint chord distances, with coordinate review flags withheld. Only printed STA endpoints support the three stated-length rate rows below.

Full project ledger, NEP counterparts and provenance JSON · Annex equivalence audit · Historical FMR repeat comparisons · Cost per meter · stated-length screens and coordinate-based approximations

Stage matching and normalization methodology

One-to-one full normalized title plus printed-region join; normalized coordinate arrays (six decimal digits) strengthen segment evidence but never define road length. Free occurrences selected by coordinate agreement, then amount difference. Already-paired titles remain ambiguous. Fuzzy titles ≥90% with qualified town/province and no explicit location/direction/tranche conflict withhold an insertion claim; they do not establish retention. Missing counterparts are review candidates, not certified insertions/removals. Imported coordinate repairs and anomalies retain all original flags.

Coordinates are endpoints, not measured road alignment length. Separately labeled approximate allocation-per-meter tables use endpoint chord distances; they do not supply stated road-length denominators or verified price-screening flags.
The NEP standalone PDF is not available locally for independent cell extraction; imported source hash and audit provenance retained.
Regional equality and title agreement do not certify funded engineering scope. No attribution to authors or beneficiaries.
The annex text equivalence check excludes production-footer timestamps only and does not authenticate either full bill.

Coordinate flags do not remove monetary allocations. One project with several coordinate segments is counted once in the monetary ledger. Imported row IDs locate records in a document; they never assert cross-document project identity.