← We The People Platform Download .docx

FEDERAL INFRASTRUCTURE FEE

Cost Recovery from Companies for Federally-Owned Broadband and Cellular Infrastructure

A Civic Infrastructure Companion Document

Jason Robertson

v1.3 · Created May 6, 2026 for v2.26 · Updated May 6, 2026 for v2.28.2 (v2.28 update note added: deferred questions now substantiated in item 79) · Updated May 6, 2026 for v2.30.25 (added Scam Call and Phishing Attack Reduction Through Infrastructure-Level Enforcement section) · Updated May 6, 2026 for v3.1.1 (Regulatory Architecture and Tribal Sovereignty sections added in response to v3.1.0 persona simulation findings)

Ohio · 2026

Why This Document Exists

If the federal government owns the broadband and cellular infrastructure that companies use for their commerce, the federal government can charge those companies a fee to use it. This is the same principle that operates turnpike tolls, airport landing fees, marine port fees, and water utility connection fees. The infrastructure is publicly owned, the users pay for what they use, and the fee revenue funds operations and maintenance and capital recovery. This document establishes the Federal Infrastructure Fee as the platform's commitment for cost recovery on the broadband and cellular infrastructure that items 51 and 77 commit to.

The document does three things. It quantifies the cost of deploying and maintaining the broadband and cellular infrastructure under federal ownership. It uses those costs to set the fee at a level that recovers them transparently. And it establishes the fee architecture as a turnpike-toll model rather than a tax: cost-recovery from infrastructure users, calibrated to actual costs, indexed to publicly-available inflation data, predictable for company budgeting, and adaptable to demand growth over time.

The document is offered as a companion to the Universal Broadband Access Substantiation, the Emergency Services Communications Modernization document, and the Federal Fiscal Impact Analysis. Each of these documents has commitments that this document's fee architecture funds.

The Architectural Premise: Federal Ownership of Infrastructure

The platform's previous broadband substantiation selected what it called Path A: federal subsidy of approximately thirty dollars per month per household to private internet service providers, who continued to own the underlying infrastructure. Path A produces free or near-free residential broadband through perpetual federal subsidy, but the federal government does not own the fiber. The substantiation explicitly considered and deferred Path B (federal ownership) as more expensive at the capital level.

The infrastructure fee architecture this document establishes requires Path B. The federal government must own the infrastructure to charge fees for using it. v2.26 therefore represents an architectural shift: from Path A subsidy to Path B federal ownership. The shift is justified because the long-run economics favor ownership over perpetual subsidy, because federal ownership consolidates emergency services infrastructure (per item 77) into a coherent system, and because the fee mechanism allows companies that benefit from the infrastructure to fund it rather than relying on perpetual taxpayer subsidy.

Path A Versus Path B Cost Comparison Over Thirty Years

Path A federal cost over thirty years: approximately two trillion dollars. Annual subsidy of forty-eight billion dollars in Year One, growing with inflation to approximately eighty-seven billion dollars by Year Thirty. Plus BEAD-equivalent capital subsidy of forty-two and one-half billion dollars (one-time). Plus federal regulatory overhead through USF (Universal Service Fund) and FCC of approximately twelve billion dollars over the period. Companies under Path A also pay USF contributions (approximately eight billion dollars per year) and state telecom taxes (approximately fifteen to twenty billion dollars per year aggregate). Path A grand total across federal and company contributions over thirty years: approximately three to three and one-fifth trillion dollars.

Path B federal cost over thirty years: approximately one and one-half trillion dollars in gross federal commitment. Capital deployment of approximately two hundred seventy billion dollars over the first seven years. Annual operations and maintenance of approximately thirteen and one-half billion dollars in Year One, growing with inflation to approximately twenty-one billion dollars by Year Thirty. Future capacity reserve of approximately six and three-quarters billion dollars per year, growing similarly. Capital recovery via thirty-year amortization at three percent real cost of capital: approximately fourteen billion dollars per year. Net of infrastructure fee revenue from companies of approximately one and one-third trillion dollars over thirty years, the federal NET commitment under Path B is approximately one hundred thirty billion dollars over the period — roughly one-fifteenth of Path A federal cost.

Path B grand total across federal and company contributions over thirty years: approximately one and one-half trillion dollars. This is approximately one and one-half to one and seven-tenths trillion dollars less expensive than Path A over the same period. The savings come from three sources: federal ownership eliminates the perpetual subsidy mechanism, federal economies of scale reduce duplicated buildout costs, and capital amortization treats infrastructure as a long-lived asset rather than as perpetual operating expense.

Companies under Path B pay an annual infrastructure fee aggregating to approximately thirty-four billion dollars in Year One, growing with inflation. Companies do not pay USF contributions (USF is replaced) or state telecom taxes (these are preempted and consolidated into the federal fee). The current company telecom-fee burden of approximately twenty-three to twenty-eight billion dollars per year is replaced by the unified federal fee of approximately thirty-four billion dollars. The net increase to companies (approximately six to eleven billion dollars per year) reflects that they receive substantially more infrastructure value under Path B (federal ownership of fiber, federal cellular gap coverage, federal cybersecurity standardization, free residential service that benefits their workforce) than under Path A.

Why the Architectural Shift is Coherent with Other Platform Commitments

Emergency Services Communications Modernization committed to federal ownership of cellular sites in coverage gaps and to consolidating state ESInet procurements into federal broadband transport. Both commitments require federal ownership of the underlying infrastructure. Item 51's Path A subsidy model was inconsistent with this: federal cellular sites are federally-owned, but the underlying broadband transport for which they connect was privately-owned under Path A. v2.26 resolves this incoherence by completing the federal ownership of the broadband and cellular infrastructure across both items 51 and 77.

Capital Deployment Cost Analysis

Federal capital deployment under Path B has three primary components: last-mile fiber to every premise, backbone and middle-mile fiber, and federal cellular sites in coverage gaps. Each is grounded in industry-standard deployment economics and current US infrastructure estimates.

Last-Mile Fiber to All Premises

The United States has approximately one hundred thirty-two million households, eight million business establishments, and roughly five million government and institutional locations, for a total of approximately one hundred forty-five million addressable premises. Per-premise fiber buildout cost varies significantly by population density: approximately eight hundred to fifteen hundred dollars per premise in urban areas; approximately twenty-five hundred to four thousand dollars in suburban areas; approximately six thousand to fifteen thousand dollars in rural and remote areas. The national weighted average is approximately two thousand to twenty-five hundred dollars per premise for complete buildout.

Total US fiber buildout cost at full coverage: approximately two hundred ninety to three hundred sixty billion dollars. Of this, approximately eighty to one hundred twenty billion dollars has already been deployed by private carriers in dense areas where the economics worked. The federal investment under Path B is for the remaining buildout (rural and underserved areas) plus the consolidation of existing private fiber into federal ownership (through purchase at fair value). The federal capital commitment for last-mile fiber is therefore approximately one hundred seventy to two hundred forty billion dollars, deployed over a seven to ten year window.

Backbone and Middle-Mile Fiber

Long-haul fiber networks, regional aggregation rings, and Internet exchange points form the infrastructure layer above last-mile that connects regional networks to the global Internet. Most of this currently exists as a mix of private (Lumen/CenturyLink, Zayo, Cogent, Level 3) and quasi-public (Internet2, state research and education networks) infrastructure. Federal consolidation of this layer requires approximately forty to eighty billion dollars depending on whether existing networks are purchased at fair value or whether parallel federal infrastructure is constructed.

Federal Cellular Sites in Coverage Gaps

The Emergency Services Communications Modernization document established the federal commitment to deploy cellular sites in coverage gaps, particularly on tribal lands, rural areas, and remote terrain where commercial cellular fails to provide adequate service. The first-order estimate there was approximately five thousand federal sites at three hundred thousand dollars per site, totaling one and one-half billion dollars. A more comprehensive estimate accounting for desired coverage targets is fifteen thousand to twenty-five thousand federal sites at two hundred thousand to four hundred thousand dollars per site, totaling three to ten billion dollars over the deployment window. This is for federal sites in gaps; existing commercial carrier sites (approximately four hundred thousand nationally) remain privately owned and lease federal fiber backhaul at regulated rates.

Total Federal Capital Base

Summing the three components: last-mile fiber at one hundred seventy to two hundred forty billion dollars, backbone and middle-mile at forty to eighty billion dollars, and federal cellular sites at three to ten billion dollars produces a total federal capital base of approximately two hundred thirteen to three hundred thirty billion dollars at full deployment. The midpoint is approximately two hundred seventy billion dollars.

Annual Operating and Maintenance Costs

Annual operations and maintenance costs are based on industry-standard percentages of capital base, calibrated to current US telecom infrastructure operating data. Each component is documented separately for transparency.

Fiber Operations and Maintenance

Industry standard for fiber maintenance is approximately three to five percent of capital base annually. This covers cable repairs from physical damage, electronics replacement on a ten to fifteen year cycle, network operations centers and customer support infrastructure, field crews and equipment, and routine system upgrades. Applied to a fiber capital base of approximately two hundred fifty billion dollars (last-mile plus backbone), annual fiber operations and maintenance is approximately seven and one-half to twelve and one-half billion dollars.

Cellular Operations and Maintenance

Cellular sites have higher maintenance costs as a percentage of capital because of more frequent technology refresh, more active electronics, antenna systems requiring physical maintenance, and integration with the dynamic carrier ecosystem. Industry standard is approximately ten to fifteen percent of capital base annually. Applied to a federal cellular capital base of approximately seven billion dollars, annual federal cellular site operations and maintenance is approximately seven hundred million to one and one-tenth billion dollars.

Backbone and Network Operations

Backbone fiber maintenance and network operations centers, including peering arrangements, Internet exchange point operations, and core network management, represents approximately two to three billion dollars per year at federal infrastructure scale.

Cybersecurity Operations

Per the Emergency Services Communications Modernization commitments, federal infrastructure carrying emergency services traffic implements cybersecurity standards from CISA, NIST, NENA, and CJIS frameworks. Cybersecurity operations including continuous monitoring, threat intelligence, incident response, software bill of materials tracking, and annual penetration testing represent approximately two hundred to four hundred million dollars per year.

Total Annual Operations and Maintenance

Summing the components: fiber operations and maintenance at seven and one-half to twelve and one-half billion dollars, cellular operations and maintenance at seven hundred million to one and one-tenth billion dollars, backbone operations at two to three billion dollars, and cybersecurity operations at two hundred to four hundred million dollars produces a total annual operations and maintenance budget of approximately ten and four-tenths to seventeen billion dollars. The midpoint is approximately thirteen and one-half billion dollars per year.

Future Capacity Reserve

Active electronic components in fiber and cellular networks have useful lives of approximately ten to fifteen years. Passive infrastructure (fiber strands, towers, conduit) lasts approximately thirty to fifty years. A blended future capacity reserve preserves the network's ability to handle growing demand and to refresh technology on schedule without requiring emergency capital appropriations.

Future capacity reserve at two and one-half percent of capital base annually, applied to a two hundred seventy billion dollar capital base, produces approximately six and three-quarters billion dollars per year. This funds equipment replacement on the active components' ten to fifteen year cycle, capacity expansion to handle growing data volumes, and modernization (fiber-to-the-home upgrades, six-G cellular when standardized, future spectrum deployments). The reserve grows with inflation and with capital base expansion.

Annual Revenue Requirement

The Federal Infrastructure Fee target is the sum of capital recovery, operations and maintenance, and future capacity reserve. Each component is calibrated to actual costs rather than to revenue targets, and each is independently auditable.

Capital Recovery via Thirty-Year Amortization

The federal capital base of approximately two hundred seventy billion dollars is amortized over thirty years at a three percent real cost of capital, producing annual capital recovery of approximately thirteen and seven-tenths billion dollars. This treats the infrastructure as a long-lived asset whose cost is recovered over its useful life rather than charging current users for the full capital cost. The thirty-year amortization period is conservative (passive infrastructure lasts longer); the three percent real cost of capital reflects the federal government's actual cost of borrowing for infrastructure investment.

Total Annual Revenue Requirement

Summing the three components: capital recovery at thirteen and seven-tenths billion dollars, operations and maintenance at thirteen and one-half billion dollars (midpoint), and future capacity reserve at six and three-quarters billion dollars produces a total annual revenue requirement of approximately thirty-four billion dollars. The range across cost-base scenarios is twenty-six to forty-six billion dollars per year. The fee target is set at thirty-four billion dollars in Year One, with annual adjustment via the inflation indexing formula described below.

The Four Fee Allocation Structures

The thirty-four billion dollar annual revenue requirement must be allocated across the companies that use the infrastructure. Four allocation structures were considered, each with distinct fairness profiles and administrative characteristics. All four are documented for transparency before the recommended structure is identified.

Structure A: Per-Employee Fee

A flat fee of approximately two hundred sixty dollars per private-sector employee per year applied uniformly across all companies. United States private-sector payroll employment is approximately one hundred thirty million according to the Bureau of Labor Statistics, producing the thirty-four billion dollar revenue target at this rate. Worked examples: a small business with eight employees pays approximately two thousand eighty dollars per year. A medium-sized firm with seventy-five employees pays approximately nineteen thousand five hundred dollars. A large enterprise with thirty-five hundred employees pays approximately nine hundred ten thousand dollars. A mega-cap with seventy-five thousand employees pays approximately nineteen and one-half million dollars.

Structure A is the simplest to administer and the easiest to enforce. It is regressive in the sense that small businesses pay the same per-employee rate as large enterprises, despite lower per-employee revenue and lower per-employee infrastructure use. It is fair on a use-proportional basis if infrastructure use scales with headcount, which is approximately true but not exactly true (data-intensive small companies use more infrastructure per employee than labor-intensive large companies). Gaming risk is low because employee counts are well-documented through payroll tax filings.

Structure B: Tiered by Company Size

A tiered structure that exempts small businesses (under fifty employees) entirely and applies graduated per-employee rates for larger firms. The tier structure: small businesses (under fifty employees) pay zero. Mid-sized businesses (fifty to five hundred employees) pay approximately two hundred dollars per employee per year. Large businesses (five hundred to five thousand employees) pay approximately three hundred dollars per employee per year. Very large businesses (over five thousand employees) pay approximately four hundred dollars per employee per year. Calibrated to produce the thirty-four billion dollar target.

Worked examples: the eight-employee small business pays zero. The seventy-five-employee medium-sized firm pays approximately fifteen thousand dollars. The thirty-five-hundred-employee large enterprise pays approximately one million fifty thousand dollars. The seventy-five-thousand-employee mega-cap pays approximately thirty million dollars. Structure B is more progressive than Structure A in protecting small businesses entirely. It is regressive in shifting cost from very-small to mid-sized businesses (the fifty-employee company pays substantially while the forty-nine-employee company next door pays zero). Gaming risk is medium (companies near the fifty-employee boundary may manipulate headcount).

Structure C: Revenue-Based

A flat percentage of company revenue, calibrated to produce the thirty-four billion dollar target. United States private-sector business revenue is approximately forty trillion dollars annually. A fee rate of approximately zero point zero eight five percent of revenue produces the target. Worked examples: a small business with one and one-half million dollars in revenue pays approximately twelve hundred seventy-five dollars per year. A medium business with twenty million dollars in revenue pays approximately seventeen thousand dollars. A mid-sized firm with eighty million dollars in revenue pays approximately sixty-eight thousand dollars. A large enterprise with one and two-tenths billion dollars in revenue pays approximately one million twenty thousand dollars. A mega-cap with fifty billion dollars in revenue pays approximately forty-two and one-half million dollars.

Structure C is the most revenue-proportional and aligns fee with economic capacity to pay. It is the simplest to administer because revenue is reported through existing federal tax filings. Its primary weakness is gaming risk: revenue recognition is more manipulable than headcount or location count, and large companies have substantial flexibility in attributing revenue across subsidiaries and jurisdictions. The revenue-based approach also disadvantages low-margin industries (grocery retail, contract manufacturing) relative to high-margin industries (software, pharmaceuticals) without that disparity having a clear infrastructure-use justification.

Structure D: Hybrid (Recommended)

The recommended structure combines components for fairness across company types and industries. Three components: a base location fee of approximately six hundred dollars per year per business location (covers small fixed-cost businesses fairly without exempting them from the system); a per-employee component of approximately one hundred seventy-five dollars per employee per year, exempting the first twenty-five employees (protects small businesses while ensuring use-proportional contribution from larger firms); a revenue surcharge of approximately zero point zero three five percent on revenue above fifty million dollars per year (captures the largest companies whose infrastructure use scales with revenue more than headcount, particularly cloud services and digital platforms).

Worked examples: the eight-employee small business with one and one-half million dollars in revenue and one location pays approximately six hundred dollars (location fee only — no employee fee due to twenty-five employee exemption, no revenue surcharge due to fifty million dollar threshold). The seventy-five-employee medium business with twenty million dollars in revenue and two locations pays approximately ten thousand dollars (twelve hundred for locations plus eighty-seven hundred fifty for fifty employees above the exemption, no revenue surcharge). The mid-sized firm with three hundred fifty employees, eighty million dollars in revenue, and five locations pays approximately sixty-five thousand dollars (three thousand for locations plus fifty-six thousand eight hundred seventy-five for three hundred twenty-five employees plus ten thousand five hundred for the revenue surcharge above fifty million).

Continuing the worked examples: the large enterprise with thirty-five hundred employees, one and two-tenths billion dollars in revenue, and twenty-five locations pays approximately one million seventeen thousand dollars (fifteen thousand for locations plus six hundred eight thousand seven hundred fifty for thirty-four hundred seventy-five employees plus four hundred two thousand five hundred for the revenue surcharge). The mega-cap with seventy-five thousand employees, fifty billion dollars in revenue, and five hundred locations pays approximately thirty-one million dollars (three hundred thousand for locations plus thirteen million one hundred fifteen thousand six hundred twenty-five for seventy-four thousand nine hundred seventy-five employees plus seventeen million four hundred ninety-eight thousand for the revenue surcharge above fifty million).

Structure D is recommended because it combines the fairness benefits of the other structures while mitigating their individual weaknesses. The location component prevents very small businesses from paying nothing (which Structure B does) while keeping their burden minimal. The employee component anchors the fee in real economic activity (which Structure C does not, given revenue gaming risk). The revenue surcharge captures the largest companies whose infrastructure use does scale with revenue (cloud services, content providers) more than with headcount. The first-twenty-five-employee exemption protects small business growth without creating a hard cliff. Gaming risk is low because each component uses well-documented base data (locations from Secretary of State filings, employees from payroll tax filings, revenue from federal tax filings).

Adjusted Hybrid for Industry Exemptions

The exemption framework described in Section 9 below removes public-purpose entities from the fee base, reducing the revenue capacity by approximately fifteen percent. To preserve the thirty-four billion dollar target, the recommended hybrid structure is adjusted: base location fee at six hundred dollars per year (was five hundred), per-employee component at one hundred seventy-five dollars per year exempting first twenty-five employees (was one hundred fifty), revenue surcharge at zero point zero three five percent on revenue above fifty million dollars per year (was zero point zero three percent). The adjusted structure produces the same total revenue from a smaller base of commercial payers.

Inflation Indexing — A Transparent Formula

The fee value adjusts annually using a formula that combines three publicly-available Bureau of Labor Statistics indices, weighted to reflect the actual cost structure of broadband and cellular infrastructure. The formula is published and the index data is freely available, making the annual adjustment fully predictable and verifiable.

The Formula

The annual adjustment factor is the weighted average of three components: fifty percent weight on the BLS (Bureau of Labor Statistics) Producer Price Index for Wired Telecommunications Carriers (NAICS 5171); thirty percent weight on the BLS Employment Cost Index for telecommunications technicians; twenty percent weight on the BLS Producer Price Index for Telecommunications Equipment Manufacturing (NAICS 3342). The weighting reflects that physical operations and overhead represent approximately half of infrastructure costs, labor represents approximately thirty percent, and equipment refresh represents approximately twenty percent.

The previous year's fee multiplied by one plus the weighted average inflation produces the next year's fee. For example, if the wired telecom PPI rose two percent year over year, the telecom technician ECI rose three percent, and the telecom equipment PPI fell one percent, the weighted adjustment would be one and seven-tenths percent (zero point five times two plus zero point three times three plus zero point two times negative one). The next year's fee would be the current fee multiplied by one point zero one seven.

Why This Formula

Each component reflects a real cost driver. PPI for wired telecom captures the cost of physical operations including cable maintenance, conduit repair, and facility overhead. ECI for telecom technicians captures the labor cost of operating the network — the largest single category of operating expense. PPI for telecom equipment captures the cost of electronic components that must be replaced on the technology refresh cycle. The blend approximates how actual infrastructure costs change over time.

Historical data: telecom equipment has actually declined in real terms over the past two decades (Moore's Law applied to networking equipment), while telecom labor has risen approximately one to two percent per year above general inflation. The PPI for wired telecom has risen approximately at the rate of general inflation. The blended formula therefore tends to produce annual adjustments slightly below general consumer price inflation, reflecting that infrastructure costs are partially offset by technology improvements.

Predictability for Company Budget Planning

Companies can extrapolate the fee three to five years forward using current BLS data. The Federal Reserve's general inflation projections combined with historical telecom-specific premiums produce reasonable forward estimates. The federal infrastructure operator publishes a three-year forward projection of the fee annually, based on current data, that companies can use directly in budget planning. The projection is not binding — the actual fee depends on actual index data — but provides a baseline that is rarely off by more than one percent in the projection year.

Industry Exemptions for Public-Purpose Entities

Charging fees to other federal-funded or public-purpose entities for using federal infrastructure creates administrative drag without economic substance. Money flows from federal-supported entities to the federal infrastructure operator, with the federal-supported entities ultimately needing more federal support to cover the fees. The fee framework therefore exempts public-purpose entities while requiring their for-profit equivalents to pay.

Exempt Entities

The following entity categories are exempt from the Federal Infrastructure Fee: public hospitals and qualified non-profit hospitals (hospitals with 501(c)(3) status providing substantial uncompensated care, defined as care provided to indigent patients exceeding the value of community benefit obligations under existing IRS (Internal Revenue Service) rules); public schools (K through 12 districts) and accredited non-profit educational institutions (501(c)(3) colleges and universities); public libraries; public safety entities including PSAPs, fire departments, police departments, and emergency medical services agencies; tribal nation governments and tribally-operated entities (consistent with the Trust Responsibility framework established in the Emergency Services Communications Modernization document); public housing authorities; public transit agencies; and federal, state, and local government agencies of any function. Native American tribal nations have the option to participate in the fee framework as commercial entities for tribally-owned businesses or to remain entirely exempt for tribal-government functions; the choice belongs to each tribal authority.

Non-Exempt For-Profit Equivalents

For-profit equivalents in each exempt category remain subject to the fee. For-profit hospital chains (HCA Healthcare, Tenet Healthcare, Community Health Systems) pay the fee based on their employees and revenue. For-profit educational institutions, including for-profit colleges and for-profit charter management organizations, pay the fee. Private security companies pay the fee. Investor-owned utilities pay the fee through their normal ratemaking processes. Private prisons pay the fee. The principle is that the exemption applies to public-purpose mission, not to industry sector. A non-profit hospital is exempt; a for-profit hospital in the same town is not.

Revenue Capacity Impact

Public-purpose entities account for approximately twelve to eighteen percent of US payroll employment, depending on the boundary definition. Exempting them from the fee base reduces revenue capacity by approximately fifteen percent. The Hybrid Structure D rates have been adjusted upward by approximately fifteen percent (per Section 7's adjusted hybrid) to preserve the thirty-four billion dollar revenue target from the smaller base of commercial payers. The economic incidence shifts somewhat onto commercial entities, but the shift is modest given the large total payer base.

Replacing USF and State Telecom Taxes — Consolidation Benefits

The Federal Infrastructure Fee replaces the Universal Service Fund (USF) and consolidates the patchwork of state telecom taxes into a single federal mechanism. The replacement is revenue-neutral overall: the new fee target of approximately thirty-four billion dollars replaces approximately twenty-three to twenty-eight billion dollars in current company telecom-fee burden, with the difference reflecting the substantially expanded infrastructure value provided under federal ownership. The consolidation produces operational benefits beyond the substantive infrastructure shift.

Current Patchwork Costs

USAC, the Universal Service Administrative Company, operates the USF system at approximately two hundred million dollars per year in administrative cost. State public utility commissions collectively spend approximately one hundred to two hundred million dollars per year on telecom regulation, much of it overlapping with federal regulation. Federal-state coordination on telecom matters, including audit reconciliation and dispute resolution, costs approximately fifty to one hundred million dollars per year. Telecom companies maintain compliance teams to handle fifty-one or more separate regulatory regimes, with industry-wide compliance costs estimated at one to three percent of revenue, or approximately two to six billion dollars per year in aggregate.

Consolidation Savings

Eliminating USAC administration saves approximately two hundred million dollars per year. Reducing state-level telecom regulation saves approximately one hundred to two hundred million dollars per year (state regulators continue to handle non-telecom utility matters). Eliminating federal-state coordination overhead saves approximately fifty to one hundred million dollars per year. Reducing company compliance burden saves approximately one and one-half to four and one-half billion dollars per year. Total consolidation efficiency savings: approximately one and four-fifths to five billion dollars per year. The midpoint is approximately three billion dollars per year in operational efficiency.

Stability and Predictability Gains

Beyond direct cost savings, consolidation produces stability gains that companies have been advocating for over many years. Single predictable formula instead of fifty-one or more varying regimes that change with each legislative session. Single inflation index instead of state-by-state methodology variations. Single audit by the federal infrastructure operator instead of multiple state and federal audits with different criteria. Single enforcement venue instead of multi-jurisdictional disputes. Forward visibility for budgeting, since the federal formula is published and predictable, while state telecom taxes change frequently and unpredictably. Major telecom carriers (AT&T, Verizon, Comcast) have advocated for federal preemption of state telecom taxes for years precisely because the patchwork creates compliance overhead and budget unpredictability that genuinely harms their operations.

Pass-Through Prevention Mechanisms

Companies will pass infrastructure fees to consumers absent regulation. The Federal Infrastructure Fee framework includes regulatory mechanisms to prevent or constrain pass-through, with honest acknowledgment that complete prevention is difficult and that some economic incidence will fall on consumers.

Pass-Through Prevention Architecture

The platform commits to four mechanisms designed to constrain pass-through. First, transparency requirements: companies above a certain size threshold must disclose, on consumer-facing materials and in regulatory filings, the per-customer or per-transaction amount they attribute to the Federal Infrastructure Fee. The disclosure makes pass-through visible to consumers and creates competitive pressure against excessive pass-through. Second, FTC oversight: pass-through is treated as a form of consumer protection issue subject to FTC review for unfair or deceptive practices. Companies that pass through amounts substantially exceeding their actual fee burden face FTC action. Third, market structure remedies: in industries with effective competition, market dynamics constrain pass-through (companies that pass through less than competitors capture market share). The platform's commitments to broadband universality and consumer choice (per items 51 and the Civic Infrastructure pillar generally) preserve competition where it exists. Fourth, regulated industries continue to face existing rate review processes that already constrain pass-through (utilities through PUC review, healthcare through Medicare and Medicaid ratemaking, etc.).

Honest Acknowledgment of Limits

Complete pass-through prevention is not achievable. Economic theory predicts that fees on intermediate inputs like infrastructure ultimately fall partly on consumers, partly on workers, and partly on shareholders, with the proportions depending on demand elasticity and competitive structure. The platform's commitment is to constrain pass-through where constraint is feasible (transparency, antitrust enforcement, market competition), to prevent fraudulent or deceptive pass-through (FTC oversight), and to be honest with consumers about the economic mechanism rather than pretending consumers bear no part of the cost.

Estimated economic incidence under typical conditions: approximately fifty to seventy percent of the fee falls on company shareholders and retained earnings (the company's ability to set prices is constrained by competition), approximately fifteen to thirty percent falls on consumers through pass-through, and approximately five to fifteen percent falls on workers through compensation moderation. These percentages vary substantially by industry and competitive structure.

Demand Adaptation — Adjusting with Use Over Time

Infrastructure demand grows over time as data volumes increase, as new applications emerge, and as the population grows. The fee framework includes two mechanisms that adjust the fee structure with demand growth, ensuring that capacity is funded before it becomes inadequate.

Capacity Utilization Trigger

The federal infrastructure operator publishes quarterly utilization metrics including peak-hour bandwidth utilization on aggregate fiber, cellular site loading factors, backbone congestion measurements, and regional capacity headroom. When sustained utilization exceeds seventy percent on a regional basis, capital expansion is automatically triggered for that region, funded from the future capacity reserve. The reserve is replenished from the next year's fee adjustment. This produces a closed-loop system where demand growth pulls capacity expansion through the reserve mechanism without requiring legislative appropriations or emergency funding.

Volumetric Component for Very Large Users

Companies whose data flow exceeds one hundred terabytes per month across federal infrastructure pay an additional volumetric fee on the marginal data flow above the threshold. Calibrated at approximately fifty cents to one dollar per gigabyte above the threshold. The volumetric component captures revenue from the entities whose use grows fastest (large content providers, cloud services, streaming companies) and ensures that demand-driven cost growth is funded by the demand drivers. The threshold protects the vast majority of companies (those with normal commercial data flows) from incurring volumetric fees; it applies primarily to the largest digital platforms whose data volumes substantially drive infrastructure capacity requirements.

The Turnpike Toll Model and Other Regulatory Analogies

The Federal Infrastructure Fee is a use fee for public infrastructure, not a tax on companies. This distinction matters for legal defensibility, political framing, and regulatory consistency. The fee operates within a well-established regulatory tradition that includes turnpike tolls, airport landing fees, marine port fees, water utility connection fees, and spectrum auction proceeds. Each of these mechanisms recovers costs from infrastructure users; the Federal Infrastructure Fee is a continuation of that tradition, not a novel charge.

Turnpike Tolls as the Closest Analogy

Turnpike tolls share the structural pattern with the Federal Infrastructure Fee. Public infrastructure (the highway). Public ownership (state DOT or independent toll authority). Operating authority is a public or quasi-public entity. Users pay based on use (per axle, per mile, per crossing). Tolls fund operations and maintenance and capital recovery. Rates are inflation-indexed. Differential rates apply by user type (cars versus trucks, commercial versus personal). Public exemptions exist (emergency vehicles, sometimes transit, sometimes residents). Independent oversight constrains rate-setting (state legislature, Department of Transportation review). Transparent rate-setting is required (public hearings, published cost data).

Each element of this pattern maps directly onto the Federal Infrastructure Fee. Public infrastructure (federal broadband and cellular). Federal ownership. Federal infrastructure operator. Companies pay based on use (employees, locations, revenue). Fees fund operations and capital recovery. Rates are inflation-indexed via the published BLS formula. Differential rates apply by company size (the hybrid structure). Public exemptions apply to public-purpose entities. Independent oversight (FCC, GAO (Government Accountability Office), Congress, public comment periods). Transparent rate-setting through annual cost reports.

Other Regulatory Analogies

Airport landing fees provide another example: airlines pay public airport authorities (operated as quasi-independent entities) for using public airport infrastructure. Rates are calibrated to cost recovery and differentiated by aircraft size (use-proportional). FAA oversees the framework. Marine port fees follow the same pattern: shipping companies pay public port authorities for using public port infrastructure. Spectrum auction proceeds: companies pay the federal government for the right to use public spectrum, with FCC oversight. Water utility connection fees and impact fees: developers pay public water utilities for infrastructure capacity. Each of these is well-established in regulatory law and has survived legal challenge because the fees are use fees for public infrastructure, not general revenue.

Legal Defensibility

Use fees survive legal challenges including Commerce Clause challenges and Tax Clause challenges because of three structural features: demonstrated nexus to infrastructure provided (not general revenue); reasonable relation to actual costs (not arbitrary); and non-discrimination against interstate commerce. The Federal Infrastructure Fee meets all three. The cost-recovery formula demonstrates nexus. The published cost analysis demonstrates reasonable relation. The uniform federal application avoids interstate commerce discrimination.

Fraud Surface Area and Identity Theft Reduction

The current patchwork of broadband subsidy programs (USF Lifeline, Affordable Connectivity Program, state low-income subsidies) is a documented fraud vector. Consolidating these programs into the federal ownership architecture eliminates several fraud surfaces and reduces identity theft exposure for low-income households. This is a substantive benefit of the architectural shift independent of the cost-recovery and infrastructure benefits.

Documented Fraud in Current Subsidy Programs

FCC enforcement actions against USF Lifeline carriers have documented fraud at scale. The Sandwich Isles Communications case settled for thirty million dollars. Total Call Mobile settled for over forty million dollars. Multiple smaller carriers have faced enforcement actions for similar patterns: phantom subscribers (subscribers who do not exist), duplicate enrollments (same subscriber enrolled with multiple carriers simultaneously), and service-quality fraud (carriers claiming subsidies for service that does not actually function). Aggregate documented USF Lifeline fraud is approximately fifty to two hundred million dollars per year, with substantial year-to-year variation. The Affordable Connectivity Program, while better-administered than Lifeline, has documented enrollment of deceased persons, duplicate household enrollments, and ineligible enrollments. State subsidy programs add comparable amounts. Cross-program fraud (subscribers fraudulently enrolled in USF Lifeline plus state subsidies plus ACP simultaneously) has been documented but is harder to quantify.

Why the Patchwork Creates Fraud Opportunities

The current model is subsidy laundering through carriers. Federal and state money flows from government to carriers to households (or to fraudulent claims of households). Each carrier maintains its own personally identifiable information (Personally Identifiable Information (PII)) repository for verification. Each program has its own enrollment and verification process with different standards. Each state operates independently. Fraudsters exploit the gaps between programs: different verification standards across carriers, different eligibility criteria across programs, different audit cycles across jurisdictions. The carrier-level subsidy mechanism creates strong financial incentives for carriers to enroll subscribers who may not be eligible or who may not exist, since carriers receive the subsidy payment regardless of the subscriber's actual situation.

How Path B Eliminates These Fraud Surfaces

The fundamental shift under Path B is that there is no household-level subsidy eligibility check. Free basic broadband is universal. There is no enrollment process to defraud, no eligibility verification to game, and no PII collection from households for service delivery. The subsidy-laundering mechanism that creates carrier-level fraud disappears entirely because there is no carrier-administered subsidy. The federal infrastructure operator delivers service to every premise as a baseline; companies pay infrastructure fees to the federal operator using EIN-based business records that are already public through Secretary of State filings, IRS records, and employment tax filings.

Specific fraud surfaces eliminated: carrier-level USF fraud (no carrier-administered subsidy mechanism); duplicate enrollment fraud (no enrollment); cross-program fraud (one consolidated framework); service-quality fraud (universal service rather than subsidized service); state subsidy fraud (state programs replaced by federal infrastructure). Estimated direct fraud reduction: approximately two hundred to five hundred million dollars per year.

Identity Theft Protection

Beyond direct fraud reduction, Path B reduces identity theft surface area by eliminating categories of PII collection. The current system requires low-income households to provide Social Security numbers, household income documentation, and addresses to multiple carriers and programs in order to receive subsidized broadband. Each carrier and program maintains its own PII repository, each of which is a target for breach. Multiple Lifeline carrier data breaches over the past decade have affected hundreds of thousands of records. The National Verifier system introduced approximately five years ago consolidated some verification but did not eliminate the carrier-level PII collection.

Under Path B, low-income households do not provide PII to receive broadband service. The service is universal at the basic tier. There is no income verification, no Social Security number collection, no household-level enrollment process. The infrastructure fee is collected from companies using EIN-based records that are already public; no consumer PII is involved. This eliminates one of the documented identity theft vectors and complements the platform's broader Identity Theft Reduction commitments documented in the Civic Technology Pillar materials and the Federal Identity Infrastructure component of the Civic Technology pillar.

Estimated identity theft reduction is harder to quantify than direct subsidy fraud, but is real. The platform's Identity Theft Reduction document estimates that consolidating federal PII repositories reduces expected loss from approximately one hundred dollars per household per year to approximately fifteen dollars. Path B contributes to this reduction by eliminating one of the categories where PII is currently collected.

Scam Call and Phishing Attack Reduction Through Infrastructure-Level Enforcement

Federal ownership and operation of telecommunications infrastructure enables uniform enforcement of existing anti-spoofing, caller authentication, and domain authentication standards that today are inconsistently applied across the patchwork of private carriers. This produces meaningful reduction in scam call volume and phishing attack reach at the infrastructure layer. The reduction is partial rather than complete: infrastructure-level enforcement addresses spoofing, authentication failures, and known-bad-source blocking, but cannot solve attacks that use legitimate channels, sophisticated content evasion, or foreign-origin routing that bypasses US infrastructure. Endpoint security, user education, and content-level analysis remain necessary complementary protections that fall outside the platform's infrastructure scope.

What Infrastructure-Level Enforcement Provides

Mandatory STIR/SHAKEN caller authentication enforcement. STIR/SHAKEN is the industry-standard protocol for cryptographically authenticating caller identity at network handoff. Today its implementation varies widely across carriers, with some smaller carriers exempt or partially compliant, and calls failing authentication often pass through with only a 'spam likely' label rather than being rejected. Federal infrastructure operation enables uniform enforcement: calls failing authentication can be rejected at network level, eliminating the largest source of caller ID spoofing. This addresses the underlying technical condition that enables most automated scam calling operations.

Mandatory email authentication enforcement. The DMARC, SPF, and DKIM email authentication standards have existed for over a decade but are inconsistently enforced across email infrastructure. Federal email infrastructure standards could mandate authentication for all outbound mail from US infrastructure and reject or quarantine inbound mail failing authentication, reducing spoofed sender phishing emails substantially.

SMS (Short Message Service) source verification. Text message spoofing is currently trivial and widely exploited for phishing (often called smishing) and scam delivery. Federal cellular infrastructure operation enables sender authentication for text messages similar to STIR/SHAKEN for voice calls, removing the lowest-friction channel for spoofed-sender attacks.

DNS-level threat blocking. Federal DNS infrastructure can implement blocking of known phishing domains and command-and-control servers based on established threat intelligence feeds. This catches a meaningful fraction of phishing attempts at the moment users click malicious links, before browser-level or endpoint-level protections are needed. Civil liberties safeguards are essential here and are described in a subsection below.

Coordinated threat intelligence sharing. Today, threat intelligence sharing between carriers is fragmented and slow; new attack patterns often spread for hours or days before all carriers respond. Federal infrastructure operation enables real-time threat intelligence sharing across the entire network, reducing the window during which novel attacks can spread.

Foreign-origin caller and sender flagging. Calls and messages originating outside US infrastructure can be flagged as such, allowing recipients to apply heightened scrutiny. This does not block legitimate international communication but reduces the effectiveness of foreign scam operations that rely on appearing to be domestic callers.

What Infrastructure-Level Enforcement Cannot Do

Sophisticated phishing using legitimate-looking but newly-registered domains. Authentication standards verify that a sender has authorized use of a specific domain; they cannot determine whether the domain itself is intended for fraud. A newly-registered domain like 'amaz0n-security.com' passes authentication checks for itself but is still designed to deceive users. Detection of this attack class requires content analysis and behavioral analysis at the endpoint, not infrastructure-level enforcement.

Phone scams from compromised legitimate numbers. When a scammer takes over a legitimate phone number through SIM swap or account compromise, calls from that number authenticate correctly and pass infrastructure-level checks. Detection requires behavioral analysis (this number suddenly calling thousands of unfamiliar recipients) which is endpoint or service-provider territory, not infrastructure.

Social engineering attacks via legitimate channels. The most damaging scams often come from authenticated, legitimate channels: a real bank calling the customer (after the scammer convinced the bank to act), a real shipping company sending a delivery notification (which the scammer manipulated). Infrastructure cannot distinguish these from genuinely legitimate communications.

Endpoint malware compromise. If a user installs malware that captures their credentials or session tokens, no infrastructure-level protection can prevent the resulting account compromise. Endpoint security software, operating system security updates, and user education remain necessary.

Foreign-origin attacks routed around US infrastructure. Attacks delivered via international-only routes that bypass US infrastructure controls. Border filtering helps but cannot be complete without breaking legitimate international communication.

Content-level deepfake detection. Voice cloning and video deepfakes used in scams are content problems, not authentication problems. The call may authenticate correctly as coming from a legitimate caller, but the voice may be cloned. Detection requires content analysis tools that operate outside the infrastructure layer.

Civil Liberties Safeguards

Infrastructure-level enforcement of authentication standards is constitutionally distinct from content-based restriction of communications. STIR/SHAKEN enforcement, DMARC enforcement, and SMS sender verification verify metadata (who is the sender) without examining content (what the sender is saying). DNS-level threat blocking comes closer to content restriction and requires explicit civil liberties safeguards: transparent block lists with public notification of additions; an appeals process for blocked domains; court oversight for any expansion beyond known-bad-actor lists maintained by independent threat intelligence organizations; no content scanning of communications without warrants; no monitoring of communication contents under any circumstances; independent oversight structure mirroring the structure described in the Transparency and Oversight Commitments section. The platform's general principle is restraint: infrastructure-level protections should be limited to metadata-level authentication and explicit known-bad-actor lists, not expanded to behavioral inference or content interpretation.

Expected Impact

Specific quantitative impact estimates require empirical analysis that depends on baseline rates of authentication compliance, user behavior patterns, and attacker adaptation, all of which are areas of active research. Qualitative expectations: caller ID spoofing reduction would be substantial (likely the largest category of impact, given that most robocall scams depend on spoofed caller ID); phishing email reduction would be meaningful from US-based senders (DMARC enforcement is well-understood) but limited for foreign-originated phishing; SMS spoofing essentially eliminated for US-origin messages; novel attack pattern response time improved through coordinated threat intelligence; sophisticated targeted attacks largely unaffected (these don't depend on the spoofing techniques infrastructure-level enforcement addresses). The platform's claim is infrastructure-layer reduction in attack volume and effectiveness, not elimination of scams or phishing.

Relationship to Other Platform Commitments

Universal Healthcare benefits from reduced healthcare-related scam volume (Medicare fraud calls, fake prescription discount cards, fake insurance enrollment) which currently target seniors disproportionately. Wage Floors As tax architecture's economic protections are complemented by reduced financial fraud exposure, which falls disproportionately on lower-income households. The general principle of infrastructure as a public good extends naturally to security as a public good: the same logic that makes federal ownership of physical infrastructure coherent (natural monopoly characteristics, network effects, public-purpose operation) makes federal coordination of authentication enforcement coherent.

Transparency and Oversight Commitments

For the fee framework to be defensible, the cost data underneath it must be public and verifiable. The platform commits to specific transparency mechanisms that make the fee calculation auditable by companies, by Congress, and by the public.

Annual Published Cost Report

The federal infrastructure operator publishes an annual cost report documenting actual capital deployed during the year, actual operations and maintenance spending by category, actual reserve levels and reserve drawdowns, actual demand metrics and capacity utilization, and the resulting fee calculation for the next year. The report is published by April first each year for the following fiscal year, giving companies eight months of advance visibility for budget planning. The report is independently audited by GAO and by an external accounting firm contracted under standard federal audit procedures. Audit results are published with the report.

Public Formula and Forward Projections

The fee formula, including the BLS index weights, the location and per-employee and revenue-surcharge components, the exemption framework, and the demand-adjustment mechanisms, is published in regulation and accessible through the federal infrastructure operator's website. A three-year forward projection of the fee, based on current data and current trends, is published annually. The projection is not binding (actual fees depend on actual data) but provides a baseline that companies can use directly in budget planning. Historical accuracy of the forward projection (how often the projected fee in Year One matches the actual fee in Year One) is published as part of the annual report, providing companies with ongoing data on projection reliability.

Public Comment Period for Adjustments

Before each annual fee adjustment takes effect, a thirty-day public comment period accepts comments from companies, industry associations, public-purpose entities, consumer advocacy groups, and members of the public. Comments must be addressed in writing by the federal infrastructure operator before the adjustment takes effect. Significant comments that identify errors in the cost data or formula application result in adjustment of the fee. This is the standard administrative procedure that the FCC and similar federal agencies use for rate-setting; the Federal Infrastructure Fee adopts it directly.

Independent Oversight Structure

GAO conducts annual audits of federal infrastructure operations. The FCC has hearing and petition authority on fee disputes, providing companies and other stakeholders with a venue to challenge fee calculations or methodology. Congress retains oversight authority through the appropriations and authorization processes for the federal infrastructure operator. The Inspector General of the operator's parent department conducts ongoing compliance and integrity reviews. This multi-layered oversight structure parallels how other federal infrastructure operators (the FAA, the Federal Aviation Administration; the Federal Communications Commission for spectrum management; the Bureau of Reclamation for water infrastructure) are overseen.

Relationship to Other Platform Commitments

The Federal Infrastructure Fee is integrated with several other platform commitments. The integration affects both the platform's fiscal architecture and several existing analytical documents that need updating to reflect the v2.26 architectural shift.

Federal Fiscal Impact Analysis Update

The FFIA currently lists Universal Broadband as a Civic Infrastructure component costing approximately thirty billion dollars per year at mature steady state under Path A subsidy model. Under Path B with the infrastructure fee in place, the broadband line becomes net of the fee revenue. Federal gross cost is approximately thirty-four billion dollars per year (capital recovery plus O&M plus reserve). Infrastructure fee revenue is approximately thirty-four billion dollars per year. Net federal cost is approximately zero, with small variation depending on actual demand and capacity expansion. The broadband pillar becomes essentially cost-recovering from companies that benefit from the infrastructure rather than perpetually subsidized by federal taxpayers. This is a substantive improvement to the platform's fiscal architecture.

Universal Broadband Access Substantiation Revision

Item 51 was originally substantiated for Path A. The v2.26 architectural shift requires revision of item 51 to reflect Path B. The revision should include: explicit statement of the Path A to Path B shift and its rationale; description of the federal ownership model; reference to the Federal Infrastructure Fee as the funding mechanism; updated cost numbers reflecting capital deployment versus subsidy; and reliability and service-level commitments appropriate to public infrastructure (consistent with item 77's emergency services requirements). The revision is deferred to a future patch release.

Emergency Services Communications Coherence

Item 77 committed to federal ownership of cellular sites in coverage gaps and to consolidation of state ESInet procurements. v2.26 completes the federal ownership architecture by extending it to broadband fiber. The combined commitment is a coherent federal infrastructure ownership model across both broadband and cellular, with consistent operating principles, consistent cost recovery, and consistent oversight. Item 77's commitments are unchanged; v2.26 makes them more coherent with the broader broadband architecture.

Open Issues Registry Update

Several questions identified in item 77's open questions section are partially addressed by v2.26: the cost recovery model for federal cellular site leases is now specified (the Federal Infrastructure Fee replaces the lease rate question with a system-wide fee). The reliability SLA specification question identified for item 51 remains open and should be resolved when item 51 is revised. New open questions are introduced by v2.26 and are documented in Section 18 below.

Regulatory Architecture: FIF Within the Existing Federal-State Landscape

The Federal Infrastructure Fee operates within an existing regulatory landscape that includes the Federal Communications Commission, state public utility commissions, and the existing Universal Service Fund contribution mechanism. This section specifies how FIF relates to each, responding to a question that telecommunications industry professionals would identify as a critical structural concern: is FIF additive to existing mechanisms, replacing them, or functionally separate?

Relationship to FCC Regulatory Authority

FIF is established by federal statute and administered by the Federal Infrastructure Operator established alongside it; the operator's regulatory relationship to the FCC is one of coordination rather than subordination. The FCC retains its existing authority over spectrum allocation, common carrier regulation, broadcast licensing, and the other matters within Title II and Title III of the Communications Act. The Federal Infrastructure Operator's authority is over the federal infrastructure assets it owns, the FIF revenue collected, and the infrastructure deployment programs the fee funds. Coordination mechanisms include joint rulemaking on shared concerns (such as build-out requirements that affect spectrum users), joint advisory structures, and shared technical standards bodies. The architectural intent is that FCC and Federal Infrastructure Operator authorities are complementary rather than overlapping; clarification of edge cases would be addressed through inter-agency Memoranda of Understanding during implementation.

Relationship to State Public Utility Commission Jurisdiction

State public utility commissions retain their existing authority over intrastate telecommunications matters, including state-level service quality standards, intrastate rate regulation where applicable, and consumer protection matters under state statute. FIF preempts state telecommunications taxes and fees that the consolidation analysis addresses (see the Replacing USF and State Telecom Taxes section), but does not preempt state regulatory authority over service quality or consumer protection. Where state PUC jurisdiction and federal infrastructure authority intersect (for example, state-level service quality standards for federal infrastructure deployed in the state), the architectural treatment is parallel jurisdiction with the federal level providing infrastructure and the state level providing service-quality oversight. The preemption boundary specifically targets revenue extraction (telecom taxes) rather than regulatory authority over service delivery.

Relationship to the Existing Universal Service Fund

FIF is intended to replace the existing Universal Service Fund contribution mechanism rather than supplement it. The consolidation logic is documented in the Replacing USF and State Telecom Taxes section: the existing USF surcharge on long-distance and inter-state telecommunications revenue is consolidated into FIF along with state-level telecom taxes, producing a single federal mechanism rather than the current patchwork. The transition specifically eliminates the USF contribution requirement on telecommunications carriers; the federal universal service objectives that USF currently funds (high-cost support, low-income support, schools and libraries support, rural health care support) are absorbed into the federal infrastructure deployment programs that FIF funds. Carriers therefore see FIF as their replacement for USF contributions rather than as an additional obligation. The transition mechanism is documented in the Federal Infrastructure Fee Transition Mechanics document.

Why This Section Matters

Without explicit treatment of how FIF interacts with existing regulatory mechanisms, an industry reader cannot evaluate the fee's actual financial impact. The persona-based audit that surfaced this as a finding identified that the question is the first one a carrier's regulatory affairs team would raise; without an answer, the persona would defer engagement rather than evaluate substantively. This section answers the question explicitly so that engagement can begin from a shared understanding of the architectural intent. Specific edge cases, regulatory rulemaking sequence, and inter-agency MOU language are implementation matters that would be developed through the legislative and rulemaking processes; the architectural intent is the platform's contribution.

Tribal Sovereignty and Government-to-Government Consultation

Federal infrastructure proposals that touch tribal lands or tribal telecommunications must engage tribal governments through formal government-to-government consultation rather than through standard stakeholder processes. This is not a procedural nicety; it is a constitutional requirement reflecting tribal sovereignty as recognized under federal Indian law and reinforced by Executive Order 13175 and Department of the Interior consultation policies. The Federal Infrastructure Fee architecture and its associated infrastructure deployment programs interact with tribal sovereignty in several specific ways that warrant explicit treatment in this document.

Government-to-Government Consultation Requirements

Implementation of FIF and the federal infrastructure deployment programs requires formal consultation with tribal nations whose lands, jurisdictions, or telecommunications enterprises are affected. Consultation occurs at the level of tribal governments rather than at the level of individual tribal members or community organizations, and is conducted on a government-to-government basis consistent with the federal trust responsibility. Specific consultation triggers include: federal infrastructure deployment on tribal lands, federal infrastructure deployment on lands adjacent to tribal lands where tribal interests may be affected, exemption determinations for tribal telecommunications enterprises, and any rulemaking that affects tribal regulatory authority over telecommunications on tribal lands. The platform's position is that consultation is a precondition for implementation rather than a procedural step within implementation.

Tribal Telecommunications Enterprises and the Public-Purpose Exemption

Tribal-government-owned telecommunications enterprises and tribal-enterprise telecommunications providers qualify for the public-purpose exemption from FIF assessment under the same criteria that apply to other public-purpose entities, with explicit recognition that tribal sovereignty supports a presumption of qualification rather than a case-by-case evaluation. Tribal nations have established their own telecommunications infrastructure and providers as exercises of tribal sovereignty over essential services; the platform's exemption architecture should not impose federal evaluation criteria that second-guess tribal determinations. Specific exemption boundary questions for tribal entities are themselves subject to consultation rather than unilateral federal determination.

Federal Infrastructure on Tribal Lands

Federal infrastructure deployment on tribal lands operates under a different consent framework than federal infrastructure deployment on non-tribal federal lands. Tribal nations have authority over infrastructure on tribal lands subject to tribal regulatory frameworks and the federal trust relationship. The platform's position is that federal infrastructure deployed on tribal lands does so with tribal consent and within tribal regulatory frameworks, not as an exercise of federal authority over tribal sovereignty. This includes emergency communications infrastructure (covered in greater depth in the Emergency Services Communications Modernization document), backbone fiber, federal cellular sites, and other federal infrastructure categories. Where tribal nations decline federal infrastructure deployment, the platform's response is to develop alternative service approaches in cooperation with the tribal nation rather than to override tribal authority.

Why This Section Matters

The persona-based audit surfaced that the platform's primary FIF document treated tribal nation lands as an exception parameter rather than as a sovereignty matter requiring explicit treatment. Item 79's responses-to-interlocutors section addresses the tribal nation lands question, but tribal infrastructure officers reading this primary document expected to find sovereignty language without needing to navigate to a separate document. This section provides that language explicitly. The platform's broader position on tribal consultation, treaty obligations, and trust responsibility is developed across multiple documents; this section establishes the FIF-specific implementation-relevant elements within the primary FIF document so that tribal officers can evaluate the platform without cross-document navigation.

Pass-Through Prevention Enforcement Architecture

This section addresses a pass-through-prevention-mechanisms finding from the v3.1.0 telecom-industry persona simulation. The Pass-Through Prevention Mechanisms section earlier in this document describes the architectural intent (FIF should not be passed through to consumers as a separate line item or rate increase) but does not specify the enforcement mechanism. Industry professionals evaluating the platform would reasonably observe that pass-through prevention without enforcement teeth is the kind of policy language that does not survive industry pricing pressure. This section specifies the enforcement architecture explicitly.

Statutory enforcement language

The enabling statute that establishes FIF would include explicit anti-pass-through language analogous to provisions in existing regulated-industry statutes that prevent surcharge-style cost recovery. Specifically: the statute would prohibit carriers from (a) labeling consumer charges as FIF or related federal-fee items; (b) increasing consumer rates by amounts attributable to FIF during defined transition windows; (c) implementing rate increases during the transition window without filing rationale that documents the increase as not arising from FIF. The statutory language is the enforcement foundation; absent statutory authority, regulatory-only enforcement faces predictable industry challenges.

FCC rule-making authority

The Federal Communications Commission would receive rule-making authority under the FIF statute to establish pass-through prevention rules. Rule scope would include (a) reporting requirements: carriers above a size threshold report rate structure changes during defined windows with FIF-impact attestations; (b) audit authority: the FCC may audit carrier pricing decisions during transition windows; (c) enforcement actions: carriers found to have passed through FIF in violation of the rule face penalties scaled to the violation, with willful violations carrying enhanced penalties. The rule-making cadence would follow standard FCC notice-and-comment rule-making procedures, with specific public comment periods tied to transition-phase milestones.

State public utility commission complementary authority

State public utility commissions retain their existing authority over intrastate consumer protection and rate-reasonableness matters. The federal pass-through prevention architecture is complementary to state PUC authority rather than preemptive: state PUCs may pursue enforcement actions for state-level consumer-protection violations even where the same conduct triggers federal enforcement. The architectural intent is parallel jurisdiction with information-sharing mechanisms between FCC and state PUCs rather than competition between them.

Why this matters for industry engagement

The persona finding identified that pass-through prevention without enforcement teeth is not credible. The enforcement architecture above shows the platform's position is that pass-through prevention is statutorily authorized, regulatorily operationalized through FCC rule-making, and complemented by state-level authority. Industry counsel evaluating the platform can identify the enforcement teeth and evaluate the platform's claims accordingly. Specific rule-making language, penalty schedules, and inter-agency coordination mechanisms are implementation matters that would be developed through standard rule-making processes; the architectural intent is the platform's contribution.

Exemption Eligibility Decision Aid for Small Businesses

This section addresses an exemption-eligibility-unclear finding from the v3.1.0 small-business-owner persona simulation. The Industry Exemptions for Public-Purpose Entities section earlier in this document describes exemption categories but does not provide a decision tree or eligibility checklist that a small business owner could quickly use. This section provides that decision aid.

Quick eligibility checklist

A small business owner can quickly evaluate FIF eligibility using the following checklist: (1) Is your business a federal contractor with telecommunications in scope? Likely subject to FIF on telecommunications services consumed (not exempt). (2) Is your business a public-purpose entity (nonprofit hospital, public school district, library, public-broadcasting entity, tribal government enterprise)? Likely exempt. (3) Is your business under the small-business size threshold (under 100 employees, under 10 million dollars annual revenue, in non-telecommunications primary sector)? Subject to the small-business reduced-fee schedule rather than the standard fee. (4) Is your business in the telecommunications sector itself (carrier, ISP, tower owner, etc.)? Subject to FIF as a primary fee payer; pass-through prevention applies.

Decision tree for borderline cases

Borderline cases follow a decision tree. First question: is the business public-purpose by formal designation (501c3 nonprofit, public-entity charter, tribal government)? If yes, exemption applies. If no, proceed to second question: is the business in the telecommunications sector by primary NAICS code? If yes, primary-payer status applies. If no, proceed to third question: is the business under the small-business size threshold? If yes, reduced-fee schedule applies. If no, standard fee schedule applies. The decision tree is designed to be navigable in under five minutes by a business owner reading their own books, without requiring legal review.

Worked example: a small consulting firm

Consider a small management-consulting firm with 12 employees and 1.8 million dollars annual revenue, primarily serving private-sector clients. Decision tree: (1) Public-purpose by formal designation? No (private LLC). (2) Telecommunications sector by primary NAICS code? No (NAICS 5416, Management Consulting Services). (3) Under small-business size threshold? Yes (under 100 employees, under 10 million dollars revenue). Result: reduced-fee schedule applies. Specific fee amount derives from the firm's total telecommunications-services consumption multiplied by the reduced-fee rate (specified in the FIF rate table); for the example firm with typical office telecommunications consumption, the annual FIF would be in the low hundreds of dollars.

When to seek further guidance

Most small businesses can resolve their FIF status using the checklist and decision tree above. Cases that warrant seeking further guidance from a business-tax or regulatory advisor include: (a) multi-entity ownership structures where the exemption-eligible status of one entity may or may not propagate to others; (b) businesses whose primary NAICS code is in a non-telecommunications sector but whose actual operations include significant telecommunications-related activity; (c) businesses operating across multiple states or jurisdictions where state-PUC interaction questions may arise; (d) businesses participating in telecommunications-related public-private partnerships where exemption status may depend on contract structure. These cases require attention beyond the decision tree.

What This Document Does Not Address

Several topics related to the Federal Infrastructure Fee are intentionally outside this document's scope. Each is acknowledged for transparency.

State Telecom Tax Preemption Mechanism

The legal mechanism by which state telecom taxes are preempted by federal action is outside this document's scope. Federal preemption of state taxation requires either explicit congressional preemption language (which has political costs) or constitutional doctrines like the dormant Commerce Clause and the Federal Relations Clause (which require litigation). The platform's commitment is that the consolidated federal fee replaces state telecom taxes; the legal architecture for accomplishing this is for legislative drafters and constitutional scholars to specify.

Specific Industry Pass-Through Caps

Industry-specific pass-through caps (for example, a cap of fifty percent on pass-through for residential broadband retail providers) are not specified in this document. The pass-through prevention mechanisms in Section 11 establish the framework but do not specify industry-specific implementation. This is appropriate for regulatory rulemaking rather than for the fee architecture document.

Specific Spectrum Allocation for Federal Cellular

Federal cellular sites in coverage gaps require spectrum to operate. Whether they use FirstNet's existing Band 14, leased spectrum from commercial carriers, federal spectrum allocations not currently in commercial use, or some combination is not specified in this document (this is an open question in the Emergency Services Communications Modernization document, also identified in the Open Issues Registry).

Detailed Privately-Owned Fiber Acquisition Mechanism

The mechanism by which existing privately-owned fiber is acquired into federal ownership (eminent domain with fair value compensation, voluntary purchase at fair value, parallel construction with private fiber decommissioning, or some combination) is not specified. This is a substantial implementation question that requires its own analytical work and likely requires legislation.

International Companies and Cross-Border Fee Application

International companies that operate in the United States are subject to the fee on their US operations (US payroll, US locations, US-attributable revenue) but the specific treatment of multinational companies, transfer pricing implications, and cross-border data flows are not specified. Existing federal frameworks for international tax (the IRS's transfer pricing rules, the Tax Cuts and Jobs Act's GILTI provisions) provide partial templates but specific application to the infrastructure fee is open.

Open Questions

Several questions in this document's analysis are not fully resolved and are documented transparently following the platform's Provenance discipline. These questions should be added to the Open Issues Registry as research items.

Privately-Owned Fiber Acquisition Mechanism

The federal capital base estimate of approximately two hundred seventy billion dollars assumes federal acquisition of approximately one hundred billion dollars of existing privately-owned fiber at fair value. The acquisition mechanism is not specified and the fair value estimation is uncertain. Resolution requires (a) legal analysis of acquisition options including eminent domain, voluntary purchase, parallel construction with decommissioning, and hybrid approaches, (b) economic analysis of fair value methodology, and (c) likely legislation. The acquisition mechanism could substantially change the capital cost (for instance, eminent domain at depreciated book value would reduce capital cost; voluntary purchase at replacement cost would increase it).

Pass-Through Incidence Empirical Estimation

The pass-through incidence estimates in Section 11 (fifty to seventy percent on shareholders, fifteen to thirty percent on consumers, five to fifteen percent on workers) are based on general economic theory rather than industry-specific empirical analysis. Resolution requires industry-by-industry analysis using elasticity data and historical incidence studies of similar fees. This work would benefit from external economist consultation.

Forward Projection Accuracy Validation

The transparency framework commits to publishing three-year forward projections of the fee and to tracking historical accuracy. The actual accuracy of forward projections under the BLS-blended formula has not been empirically validated against historical data. Resolution requires backtesting the formula against twenty years of historical BLS index data to establish typical projection error bands.

Industry Exemption Boundary Definitions

The exemption framework (Section 9) identifies categories of public-purpose entities but specific boundary definitions are open. The definition of 'qualified non-profit hospital' uses uncompensated care thresholds; the specific threshold needs operational specification. Similarly for non-profit educational institutions and other categories. Resolution requires regulatory rulemaking with input from the affected sectors.

Sovereign Fund Capital Recovery Treatment

The capital recovery component of the fee assumes federal borrowing at three percent real cost of capital. Whether the federal capital deployment is funded through Treasury borrowing, through Sovereign Fund disbursements (when the Fund matures), or through some combination affects the cost of capital assumption and therefore the fee target. The platform's broader Sovereign Fund architecture (per the Combined Reform Model) supports Sovereign Fund disbursements as a funding source for federal capital, which would reduce the cost of capital and the resulting fee. Resolution requires integration with the Sovereign Fund's mature-state disbursement framework.

Federal Infrastructure Operator Governance Structure

The federal infrastructure operator is referenced throughout this document as a single entity, but its specific governance structure (executive branch agency, independent agency, government corporation, public-private partnership) is not specified. Each option has different implications for political accountability, operational independence, and regulatory authority. Resolution requires governance design analysis comparable to what was done for the Sovereign Fund Governance Design document.

Closing

The Federal Infrastructure Fee establishes a mechanism for the federal government to recover the costs of building and operating broadband and cellular infrastructure from the companies that use it. The mechanism is grounded in well-established regulatory tradition (turnpike tolls, airport landing fees, marine port fees) rather than introducing a novel charge. The fee is calibrated to actual costs through a transparent formula, indexed to publicly-available inflation data, predictable for company budget planning, and adaptable to demand growth over time. The fee replaces existing federal USF and state telecom taxes, consolidating a fragmented patchwork into a single coherent framework with substantial efficiency benefits for both companies and the federal government.

The architectural shift from Path A subsidy to Path B federal ownership produces approximately one and one-half to one and seven-tenths trillion dollars in cost savings over thirty years compared to the previous architecture. The savings come from federal ownership eliminating the perpetual subsidy mechanism, federal economies of scale reducing duplicated buildout costs, and capital amortization treating infrastructure as a long-lived asset. The infrastructure fee allows companies that benefit from the infrastructure to fund it directly, transforming the broadband pillar from a perpetually-subsidized federal commitment into a cost-recovering federal asset.

The fee framework includes substantial transparency commitments: annual published cost reports, GAO and external audit, three-year forward projections, public comment periods on adjustments, and independent oversight by FCC, GAO, Congress, and Inspector General. These commitments make the fee defensible legally, politically, and economically. Companies have the visibility they need for budget planning. Consumers have transparency into how the fee affects their costs. Public-purpose entities have explicit exemptions that reflect their non-commercial mission.

Several questions remain open and are documented in Section 18 above. The privately-owned fiber acquisition mechanism is the largest open question and could materially affect the capital cost estimate. Pass-through incidence estimation, forward projection accuracy, industry exemption boundary definitions, Sovereign Fund capital treatment, and federal infrastructure operator governance all require further analytical work. This document is offered as a substantive starting point for the platform's commitment to Federal Infrastructure Fee architecture, with the open questions documented honestly rather than obscured.

Small-Business Calculator Quick-Start Path

This section addresses a calculator-decision-fatigue finding from the v3.1.0 small-business-owner persona simulation. The platform's interactive calculator (in 06_Presentation_Materials) provides comprehensive business-side modeling but presents many input fields without clear guidance on which inputs matter most for small businesses specifically. A small business owner with limited time would benefit from a quick-start path with sensible defaults for inputs unlikely to materially change the result. This section documents that quick-start path; a future iteration may add the quick-start path directly to the calculator interface.

Inputs that materially affect small-business results

The three inputs that materially affect small-business FIF results are: (1) primary NAICS code (determines whether the business is in the telecommunications sector versus a non-telecommunications sector); (2) employee count (determines small-business threshold qualification); (3) annual telecommunications-services consumption in dollars (determines fee base for non-exempt businesses). All other inputs in the calculator can be left at default values without materially changing results for typical small businesses; the calculator's other inputs are designed for larger or more complex business structures.

Recommended default values for non-material inputs

For inputs that do not materially change small-business results, recommended defaults are: state-level telecom-tax exposure (the calculator default; this affects net savings calculation but not FIF amount itself); multi-jurisdiction operations flag (no, for single-state small businesses); contractor-status flag (no, for businesses not in telecommunications-related federal contracting); transition-period flag (default; the small business sees the same FIF amount in steady state regardless of transition phase, with small variations during transition windows that average out).

Quick-start workflow

A small business owner can complete a quick FIF estimate in under five minutes using the following workflow: (1) open the calculator and select the business-side mode; (2) enter your primary NAICS code or select your industry from the dropdown; (3) enter your employee count; (4) enter your annual telecommunications consumption in dollars (this is the line item on your annual telecom-services bills, summed across phone, internet, mobile, and any other telecom services); (5) leave all other fields at default values; (6) the calculator returns an estimated annual FIF amount along with the small-business-threshold qualification status. Steps 2 through 4 are the only inputs that materially affect the result; the other fields are for businesses with more complex structures.

When the quick-start path is not appropriate

The quick-start path produces accurate estimates for typical small businesses but not for all small businesses. The quick-start path is not appropriate for: (a) businesses operating across multiple states where state-level telecom-tax structures vary significantly; (b) businesses with multi-entity ownership where exemption status may propagate or not propagate across entities; (c) businesses transitioning between size thresholds during the year (start-of-year size determines small-business threshold for that year; businesses growing through the threshold may want full-detail modeling); (d) businesses with telecommunications-related federal contracts. These cases warrant using the calculator's full input set rather than the quick-start path.

v2.28 update note. The deferred questions about cellular site lease rate setting, fiber acquisition mechanism, and pass-through prevention specifics are now substantiated in Federal Infrastructure Fee Transition Mechanics. Item 79 documents the cost-recovery rate-setting methodology with worked example, the voluntary buyout with declining transition premium plus eminent domain backstop, and the three-mechanism pass-through prevention architecture (FCC line-item prohibition, comparative rate transparency, antitrust enforcement). Item 79 also documents the regulatory authority allocation (FCC primary, NTIA for property management, Treasury for fee collection, DOJ for antitrust) and the 10-year transition timeline. Item 79 introduces three additional open questions documented within itself (competitive carrier transition impact, private investment incentives during transition, tribal nation lands handling).