National Mesh Project — decentralized resilient mesh network infrastructure for the Philippines. Research, advocacy, BOM, legal framework (Konektadong Pinoy Act / RA 12234), and interactive simulation pages.
Find a file
Justin Aquino 6374b60936 Focus on the required report set: 34 required statutory reports
The site had drifted into auditing the instance rather than stating what it delivers. The
ad-hoc reports are not the story — the required set is.

- Headline is now "34 required statutory reports, all present and enabled", replacing the
  "38 reports in the app" framing. The 34 are the books, registers, audit trails and
  listings a Revenue District Office asks to see.
- The supporting-reports card is removed; one line notes the app carries a few supporting
  reports beyond the required set.
- The ad-hoc commentary is gone: no more "64 further reports created ad hoc", no
  "TEST …" or "(Updated)" wording on a public page. That remains a real housekeeping item
  on the instance, but it does not belong on the marketing surface.
- BIR Form 0619-E returns to the tax-registers group, so the page's own groups sum to
  exactly 34 again (6 + 7 + 6 + 6 + 9).
- 38 -> 34 across Overview, ESCO, News, Software & Policy cards, partner and learning.

Verified live: "34 required statutory reports" present, zero ">38<", zero "ad hoc"/"TEST".
2026-10-24 23:42:35 +08:00
backlog
fabricators
img Correct the verified counts; partner since 2024; host the Frappe community 2026-10-24 23:34:56 +08:00
260517-1439-darkmesh-project.md
AGENTS.md
cgg-task-board.html
city-mesh.html
deploy.sh Correct the verified counts; partner since 2024; host the Frappe community 2026-10-24 23:34:56 +08:00
erpnext-carbon-ledger.html Restructure the ERPNext section: five tabs, News feed, Carbon Ledger page 2026-10-24 23:28:34 +08:00
erpnext-esco.html Focus on the required report set: 34 required statutory reports 2026-10-24 23:42:35 +08:00
erpnext-learning.html Focus on the required report set: 34 required statutory reports 2026-10-24 23:42:35 +08:00
erpnext-localization.html Focus on the required report set: 34 required statutory reports 2026-10-24 23:42:35 +08:00
erpnext-partner.html Focus on the required report set: 34 required statutory reports 2026-10-24 23:42:35 +08:00
erpnext.html Focus on the required report set: 34 required statutory reports 2026-10-24 23:42:35 +08:00
fabricators.html
freecad.html Automated backup commit 2026-09-13 18:01 PST 2026-09-13 18:01:15 +08:00
green-tech-security.html Automated backup commit 2026-09-17 18:00 PST 2026-09-17 18:00:57 +08:00
index.html Focus on the required report set: 34 required statutory reports 2026-10-24 23:42:35 +08:00
interns.html
justin-aquinoCV.html
national-mesh.html
RA-12234-Konektadong-Pinoy-Act.txt
README.md
sbc.html
SOURCES.md
sovereign-tech.html Automated backup commit 2026-09-17 18:00 PST 2026-09-17 18:00:57 +08:00
underground-explainer.html pages: payback restored to standing — the return is real, it lands on the country's books 2026-08-31 04:56:55 +08:00
underground-utility-infrastructure.html pages: payback restored to standing — the return is real, it lands on the country's books 2026-08-31 04:56:55 +08:00
unified-tasks.html
updates.html Focus on the required report set: 34 required statutory reports 2026-10-24 23:42:35 +08:00

National Mesh Project

Status: Research & Advocacy Archive
Last updated: 2026-05-17


What This Is

A research compilation on decentralized, resilient mesh network infrastructure — drawn from real-world deployments worldwide. This repository exists to document what is possible and what stands in the way of building internet resilience in the Philippines.

The detailed implementation plans, bill of materials, and costing models have been moved to backlog/ after legal and regulatory assessment.


Why This Matters

The internet is not as resilient as it appears. Recent history proves it:

  • Iran, Jan 2026 — Total internet blackout. All VPNs, Tor, and Psiphon failed. Only peer-to-peer mesh and satellite worked. (ArXiv 2603.28753v1)
  • Bangladesh — Repeated blackouts during political unrest.
  • Tonga — Complete isolation after a single undersea cable break.
  • Ukraine — Communication void before Starlink intervention.
  • Typhoon Odette, Philippines — Islands silenced for weeks. No cell, no internet.

The Philippine archipelago is uniquely vulnerable: a handful of submarine cables, centralized ISP towers, and a regulator (NTC) that protects incumbent monopolies rather than public resilience.


What Works Elsewhere

Project Scale Proof
Guifi.net (Catalonia) 40,000+ nodes, millions in annual turnover ACM SIGCOMM 2016; Computer Networks 2015
Freifunk (Germany) 775+ nodes in Paderborn alone; city-scale BATMAN-adv CMS-Labs simulation study
Westminster, MD $23M municipal dark fiber, leased to Ting ISP IFC Municipal Broadband Report
Wilson, NC $33M municipal fiber, paid off by 2025, $10/mo for public housing NLC Digital Equity Playbook
Meshtastic, Mindanao 9.3km links through bamboo forest post-Typhoon Odette Field deployment reports
Project N.O.M.A.D. One-command offline server: Wikipedia, AI, maps, education Crosstalk Solutions; Apache 2.0

These are not experiments. They are proven infrastructure.


Why This Is Blocked in the Philippines

Regulatory Capture

The National Telecommunications Commission (NTC) functions as a gatekeeper for incumbent ISPs — PLDT, Globe, Converge — not as a public-interest regulator. Any framework that threatens their pricing power or market share faces procedural death.

Industry lawyers have made it clear: cheaper internet options will be litigated, delayed, and regulated out of existence. The incumbents have no interest in a resilient "Island Mode" that operates without their paid gateways.

Corruption as Friction

From right-of-way permits to spectrum allocation, every step of infrastructure deployment in the Philippines is a rent-seeking opportunity. A project that eliminates centralized gatekeepers is a project that eliminates those rents. The incentive to kill it is structural, not personal.

Spectrum Policy

LoRa operates at 920–925 MHz in the Philippines. Mesh backhaul at 5 GHz requires regulatory forbearance that the NTC has no incentive to grant. Emergency "open spectrum" provisions — common in disaster-response frameworks abroad — do not exist here.


What Survives

Despite the blockers, pieces of this vision are being built anyway — just not at LGU/national scale:

  • Meshtastic deployments by ham radio groups and barangay disaster teams (no NTC approval needed for unlicensed ISM-band LoRa)
  • Community Wi-Fi in remote barangays, often funded by OFW remittances, operating quietly under the radar
  • Off-grid solar + local servers at schools and churches, running Kiwix or Project NOMAD, with no ISP dependency
  • Fediverse instances (Mastodon, PeerTube) self-hosted by tech collectives, independent of Facebook/Google narrative control

These are not "National Mesh." They are survival infrastructure built by people who know the state will not save them.


Research Archive

Document Contents
SOURCES.md 150+ sources: academic papers, case studies, protocol docs, hardware references, shutdown analyses
AGENTS.md Workspace guide for AI assistants working on this project
RA-12234-Konektadong-Pinoy-Act.txt Full text of RA 12234 — the Konektadong Pinoy Act enabling community mesh networks
backlog/National-Mesh.html Interactive simulation, detailed BOM, costing models — archived
backlog/Notes on National Mesh.txt Technical development log — archived
city-mesh.html City Mesh Dark Fiber Initiative — interactive simulation, BOM
national-mesh.html National Mesh Federation — inter-LGU peering, cluster strategy

Original Submission

Deployment: sites.comfac.net is served by PC03's gemini-static-host from /home/user/static-sites (root-owned). Pushing to git is the backup, not the publish — run deploy.sh to rsync the site to PC03 (needs remote sudo to the root-owned webroot). See the script header. Any newly added page must also be deployed here.


This is not a call to action. It is a record of what was tried, what was learned, and what was blocked.