hekate 80431e7db1 Upload files to "/"

2026-03-14 05:57:07 +00:00

34 KiB

Raw Blame History

Meta Platforms Research — Consolidated Findings

Generated: 2026-03-11 11:27 UTC Data Sources: 180 findings, 18 lobbyist registrations, 5 bill texts, 19 timeline events

Executive Summary

This document consolidates all findings from an ongoing investigation into Meta Platforms' legislative influence, open-source strategy, Linux kernel involvement, and competitive positioning through age verification legislation. Key findings span lobbying activity in Colorado and Louisiana, technical compliance analysis of Horizon OS vs Linux, kernel subsystem influence, patent strategy, and standards body participation.

Top-Level Findings

Meta actively lobbies on age attestation bills — 4 lobbyists deployed on Colorado SB26-051, position: "Monitoring" (not opposing)
Horizon OS has 83.3% compliance readiness for age attestation mandates vs 13.9% for Linux — a 3-5 year gap
Digital Childhood Alliance hired a paid lobbyist in Louisiana (Koch, registered 05/05/2025) — the same state where Meta has 7 lobbyists
Meta's Louisiana lobbying force tripled from 2 to 7 lobbyists between 2023-2026
No cross-state lobbyist overlap — Meta uses entirely separate teams per state
US age verification laws have zero FOSS exemptions — unlike the EU DSA model

1. State Lobbying Activity

1.1 Colorado

Lobbyists: 10 registrations (8 unique individuals/firms) Bills lobbied: 22 unique bills Position breakdown: Monitoring (59 records), Amending (48 records)

Registered Lobbyists

Lobbyist	Client	Type
Burkhart, Amber Janelle	Meta Platforms, Inc	Individual
COYNE, WILLIAM C	Meta Platforms, Inc	Individual
Diers, Tyler	Meta Platforms, Inc.	Individual
EICHBERG, ADAM	Meta Platforms, Inc	Individual
Headwaters Strategies	Meta Platforms, Inc	Firm
Martinez, Ana	Meta Platforms, Inc.	Individual
Martinez, Ana	Facebook Inc.	Individual
Sachs, Dan	Meta Platforms, Inc.	Individual
Sachs, Dan	Facebook Inc.	Individual
Schmidt, Alyson	Meta Platforms, Inc	Individual

Key Bills

Bill	Subject	Position	Lobbyists
SB26-051	Age Attestation on Computing Devices	Monitoring	4
HB26-1058	Protections for Minors Featured in Digital Content	Amending	4
HB25-1287	Social Media Tools for Minor Users & Parents	Amending	5
SB25-086	Protections for Users of Social Media	Amending	5
HB24-1136	Healthier Social Media Use by Youth	Monitoring, Amending	6
SB24-158	Social Media Protect Juveniles Disclosures Reports	Monitoring, Amending	6
SB24-041	Privacy Protections for Children's Online Data	Monitoring	5
SB24-205	Consumer Protections for Artificial Intelligence	Monitoring, Amending	6
HB24-1130	Privacy of Biometric Identifiers & Data	Monitoring, Amending	6
HB24-1058	Protect Privacy of Biological Data	Monitoring, Amending	6

All Bills Lobbied (Colorado)

Bill	Subject	Position	# Lobbyists	Names
HB21-1244	Restrictions On Collection And Use Of Biometric In	Monitoring	1	Martinez, Ana
HB24-1058	Protect Privacy of Biological Data	Monitoring, Amending	6	Burkhart, Amber Janelle, COYNE, WILLIAM C, EICHBERG, ADAM, Headwaters Strategies, Martinez, Ana, Schmidt, Alyson
HB24-1070	Allowing Certain Items at School Graduation	Monitoring	1	Schmidt, Alyson
HB24-1130	Privacy of Biometric Identifiers & Data	Monitoring, Amending	6	Burkhart, Amber Janelle, COYNE, WILLIAM C, EICHBERG, ADAM, Headwaters Strategies, Martinez, Ana, Schmidt, Alyson
HB24-1136	Healthier Social Media Use by Youth	Monitoring, Amending	6	Burkhart, Amber Janelle, COYNE, WILLIAM C, EICHBERG, ADAM, Headwaters Strategies, Martinez, Ana, Schmidt, Alyson
HB24-1468	Artificial Intelligence & Biometric Technologies	Monitoring	5	Burkhart, Amber Janelle, COYNE, WILLIAM C, EICHBERG, ADAM, Headwaters Strategies, Schmidt, Alyson
HB25-1090	Protections Against Deceptive Pricing Practices	Amending	5	Burkhart, Amber Janelle, COYNE, WILLIAM C, EICHBERG, ADAM, Headwaters Strategies, Schmidt, Alyson
HB25-1287	Social Media Tools for Minor Users & Parents	Amending	5	Burkhart, Amber Janelle, COYNE, WILLIAM C, EICHBERG, ADAM, Headwaters Strategies, Schmidt, Alyson
HB25-B1008	Consumer Protections for Artificial Intelligence I	Monitoring	4	Burkhart, Amber Janelle, COYNE, WILLIAM C, Headwaters Strategies, Schmidt, Alyson
HB26-1058	Protections for Minors Featured in Digital Content	Amending	4	Burkhart, Amber Janelle, COYNE, WILLIAM C, Headwaters Strategies, Schmidt, Alyson
RULES	Privacy Rules	Monitoring	1	Martinez, Ana
SB21-190	Protect Personal Data Privacy	Amending	2	Martinez, Ana, Sachs, Dan
SB23-207	Sales And Use Tax Refund For Data Center Purchases	Monitoring	5	Burkhart, Amber Janelle, COYNE, WILLIAM C, EICHBERG, ADAM, Headwaters Strategies, Schmidt, Alyson
SB24-041	Privacy Protections for Children's Online Data	Monitoring	5	Burkhart, Amber Janelle, COYNE, WILLIAM C, EICHBERG, ADAM, Headwaters Strategies, Schmidt, Alyson
SB24-085	Sales & Use Tax Rebate for Digital Asset Purchases	Monitoring	1	Martinez, Ana
SB24-158	Social Media Protect Juveniles Disclosures Reports	Monitoring, Amending	6	Burkhart, Amber Janelle, COYNE, WILLIAM C, EICHBERG, ADAM, Headwaters Strategies, Martinez, Ana, Schmidt, Alyson
SB24-205	Consumer Protections for Artificial Intelligence	Monitoring, Amending	6	Burkhart, Amber Janelle, COYNE, WILLIAM C, EICHBERG, ADAM, Headwaters Strategies, Martinez, Ana, Schmidt, Alyson
SB25-070	Online Marketplaces & Third-Party Sellers	Amending	5	Burkhart, Amber Janelle, COYNE, WILLIAM C, EICHBERG, ADAM, Headwaters Strategies, Schmidt, Alyson
SB25-086	Protections for Users of Social Media	Amending	5	Burkhart, Amber Janelle, COYNE, WILLIAM C, EICHBERG, ADAM, Headwaters Strategies, Schmidt, Alyson
SB25-B004	Increase Transparency for Algorithmic Systems	Monitoring	4	Burkhart, Amber Janelle, COYNE, WILLIAM C, Headwaters Strategies, Schmidt, Alyson
SB26-051	Age Attestation on Computing Devices	Monitoring	4	Burkhart, Amber Janelle, COYNE, WILLIAM C, Headwaters Strategies, Schmidt, Alyson
n/a	n/a	n/a	7	COYNE, WILLIAM C, Diers, Tyler, EICHBERG, ADAM, Headwaters Strategies, Martinez, Ana, Sachs, Dan, Schmidt, Alyson

1.2 Louisiana

Lobbyists: 8 registrations

Lobbyist	Client	Paid	Period
BAKER, COURTNEY L.	Meta Platforms, Inc.	No	01/01/2026 - 06/30/2026
BORILL, JOSHUA G.	Meta Platforms, INC.	Yes	04/24/2023 - current
CAFFERY III, DONELSON T	Meta Platforms, Inc.	Yes	09/29/2025 - current
CORLEY, GINGER ADAM	Meta Platforms, Inc.	No	04/07/2025 - current
HARBISON, JASON WILLIAM	Meta Platforms, Inc. (META)	Yes	09/29/2025 - current
HINES, JAMES	Meta Platforms, Inc.	Yes	05/01/2023 - current
KOCH, JOHN DUNBAR	Digital Childhood Alliance, Inc.	Yes	05/05/2025 - current
WILKERSON, MARYBETH	Meta Platforms, Inc.	Yes	03/09/2026 - current

Louisiana Registration Timeline (Anomaly)

Meta's Louisiana lobbying force grew from 2 to 7 lobbyists between 2023-2026:

2023: Borill (Apr), Hines (May) — initial presence
2025 Q2: Corley (Apr, unpaid)
2025 Q3: Caffery III + Harbison (Sep 29 — same day, both paid)
2026 Q1: Baker (Jan, unpaid, 6-month term), Wilkerson (Mar 9, paid)

This 3.5x surge coincides with Louisiana HB-570 (age verification, enacted 2025).

1.3 Texas

No Meta lobbying registrations found in the Texas Ethics Commission database (searched 2020-2026).

1.4 Headwaters Strategies (Meta's CO Lobbying Firm)

Firm: Headwaters Strategies, Inc. — Denver, CO (1660 Lincoln St, Suite 2910, 80264) Founded: 2009 | Meta client since: December 2019 | Operations: Colorado only ($0 federal lobbying)

Principal	Role	Notable Affiliations
Will Coyne	Co-founder	Former CO House Majority Chief of Staff; chief of staff to Speakers Romanoff & Carroll
Adam Eichberg	Co-founder	Former Deputy Legislative Dir. for Gov. Ritter; Chair of New Venture Fund board (Arabella Advisors network); founding board member of Windward Fund; incoming board chair of Sunflower Services (Arabella acquirer)
Alyson Schmidt	Staff	Former Colorado Hospital Association
Amber Burkhart	Public Affairs Associate	Former Arnold Ventures; MS Health Economics, LSE

Key finding: The individual Meta lobbyists (COYNE, WILLIAM C; EICHBERG, ADAM; Schmidt, Alyson; Burkhart, Amber Janelle) listed alongside "Headwaters Strategies" in the CO SOS data are the same people — the firm's principals and staff. The "4 lobbyists + 1 firm" count is the same team counted twice.

Arabella connection: Adam Eichberg chairs the New Venture Fund, part of the Arabella Advisors dark money pass-through network. The Center for Secure and Modern Elections (CSME), a New Venture Fund project, is also a Headwaters client — representing a governance overlap between Eichberg's board role and his firm's client base. The Arabella network is designed to enable anonymous donor-funded advocacy, raising the question of whether similar infrastructure could be used to fund or coordinate entities like DCA.

Other notable clients: Airbnb, Tesla, City of Boulder ($60K/yr), Charter Communications, Everytown for Gun Safety, Environmental Defense Fund, One Colorado.

Sources: headwatersstrategies.com; CO Open Data (data.colorado.gov); OpenSecrets (D000074493); InfluenceWatch; New Venture Fund board page.

1.5 Digital Childhood Alliance (DCA)

Finding	Detail
Domain created	2024-12-18 (Cloudflare, registrant redacted)
LA lobbyist	KOCH, JOHN DUNBAR — paid, registered 05/05/2025
LA lobbyist branches	Legislative and Local
Significance	DCA has a paid lobbyist in a state where Meta also has 7 active lobbyists
Meta funding confirmed	Deseret News (Dec 2025) reports Meta funds DCA. LA Senator Jay Morris pressed DCA Exec. Dir. Casey Stefanski on tech company funding during testimony.

1.6 Pending FOIA Requests

ID	Custodian	Filed	Due	Status
1	Secretary of State	2026-03-10	2026-03-13	pending
2	Attorney General	2026-03-11	2026-03-14	pending
3	Board of Ethics	2026-03-11	2026-03-14	pending
4	Secretary of State	2026-03-10	2026-03-13	pending
5	Attorney General	2026-03-11	2026-03-14	pending
6	Board of Ethics	2026-03-11	2026-03-14	pending

1.7 Bill Template Analysis

Pairwise text similarity analysis of 5 collected state bills:

Bill A	Bill B	Similarity
3	5	0.042
3	4	0.038
1	5	0.026
1	3	0.025
2	5	0.019
5	4	0.015
2	4	0.014
1	4	0.014
1	2	0.013
2	3	0.010

All similarity scores are very low (max 0.042). The 5 collected bills do not appear to be copied from a common template. However, only 5 of 13+ target states have been collected — the sample may be too small to detect template coordination.

2. Technical Analysis

2.1 Horizon OS vs Linux Compliance

Horizon OS has 5 built-in compliance features: Meta Account Age Verification; Get Age Category API; Family Center; Quest Store Age Ratings; Minor Account Defaults. These collectively address age verification, parental consent, content controls, parental tools, and default protections for minors.
Linux distros have 7 major compliance gaps: Account System Age Bracket; Age Category D-Bus API; Parent-Child Account Linking; Parental Consent Verification; Package Manager Age-Rating Enforcement; Unified Parental Controls Dashboard; Age-Gated Default Profiles. Estimated total implementation effort: 36-71 months of coordinated cross-project work.
The compliance gap creates a structural advantage for Meta's Horizon OS: it already has the infrastructure (account system, age API, parental controls, app store enforcement) that child-safety legislation requires. Linux distros would need 3-5 years of coordinated development across freedesktop.org, GNOME, KDE, and multiple package managers to reach parity. This gap could be leveraged in regulatory arguments that open-source platforms are not ready for compliance, justifying app-store gatekeeping.
Horizon OS Age API documentation scraped from 0 page(s). No structured API endpoints extracted -- documentation may require JavaScript rendering or may have changed structure.
Meta Family Center pages fetched but no structured feature list extracted. Pages may require JavaScript rendering or features are embedded in non-standard markup.
Horizon OS has 5 built-in compliance features: Meta Account Age Verification; Get Age Category API; Family Center; Quest Store Age Ratings; Minor Account Defaults. These collectively address age verification, parental consent, content controls, parental tools, and default protections for minors.
Linux distros have 7 major compliance gaps: Account System Age Bracket; Age Category D-Bus API; Parent-Child Account Linking; Parental Consent Verification; Package Manager Age-Rating Enforcement; Unified Parental Controls Dashboard; Age-Gated Default Profiles. Estimated total implementation effort: 36-71 months of coordinated cross-project work.
The compliance gap creates a structural advantage for Meta's Horizon OS: it already has the infrastructure (account system, age API, parental controls, app store enforcement) that child-safety legislation requires. Linux distros would need 3-5 years of coordinated development across freedesktop.org, GNOME, KDE, and multiple package managers to reach parity. This gap could be leveraged in regulatory arguments that open-source platforms are not ready for compliance, justifying app-store gatekeeping.
Horizon OS Age API documentation scraped from 0 page(s). No structured API endpoints extracted -- documentation may require JavaScript rendering or may have changed structure.
Meta Family Center pages fetched but no structured feature list extracted. Pages may require JavaScript rendering or features are embedded in non-standard markup.
Horizon OS has 5 built-in compliance features: Meta Account Age Verification; Get Age Category API; Family Center; Quest Store Age Ratings; Minor Account Defaults. These collectively address age verification, parental consent, content controls, parental tools, and default protections for minors.
Linux distros have 7 major compliance gaps: Account System Age Bracket; Age Category D-Bus API; Parent-Child Account Linking; Parental Consent Verification; Package Manager Age-Rating Enforcement; Unified Parental Controls Dashboard; Age-Gated Default Profiles. Estimated total implementation effort: 36-71 months of coordinated cross-project work.
The compliance gap creates a structural advantage for Meta's Horizon OS: it already has the infrastructure (account system, age API, parental controls, app store enforcement) that child-safety legislation requires. Linux distros would need 3-5 years of coordinated development across freedesktop.org, GNOME, KDE, and multiple package managers to reach parity. This gap could be leveraged in regulatory arguments that open-source platforms are not ready for compliance, justifying app-store gatekeeping.

2.2 EU vs US Regulatory Comparison

EU DSA age verification analysis: Age verification obligations under the DSA apply primarily to VLOPs (>= 45M monthly EU users) through Articles 34-35 risk assessment and mitigation requirements. Smaller platforms face graduated obligations. FOSS projects that do not act as intermediary services are outside DSA scope entirely (Recital 13). Micro/small enterprises receive additional exemptions from transparency and reporting requirements.
EU age verification blueprint: The EU approach centres on the EUDIW (EU Digital Identity Wallet) under eIDAS 2.0, providing government-issued verifiable credentials with selective disclosure for age verification. Found 0 related GitHub repos. T-Scy consortium search returned 4 results. Key difference from US approach: wallet-based, user-controlled, interoperable across platforms and OS vendors.
EU vs US age verification comparison: EU uses platform-level regulation (DSA/VLOPs) with FOSS exemptions and privacy-by-design (EUDIW). US uses OS-level mandates (AB 1043, SB 26-051) with no FOSS exemption, concentrating power in Apple/Google. Key risk: US approach threatens open-source OS distributions and creates vendor lock-in absent from the EU model.
FOSS exemption analysis: EU provides 5 distinct protection mechanisms for FOSS. US model creates 4 categories of threat affecting 13+ named projects/channels. 4 technical barriers exist with no current FOSS workaround. The EU EUDIW (open-source) provides a compliance pathway for FOSS; the US offers none.

2.3 Microkernel Patent Analysis

Patent US20210286628A1: "Operating System With A Single Kernel Stack Per Processor" Status: abandoned. Filed: 2021-05-04. Claims: 38. Horizon OS relevance: low (2 keyword matches).
Patent US11119931B1: "Data pipeline for microkernel operating system" Status: expired. Filed: 2019-09-18. Claims: 85. Horizon OS relevance: medium (3 keyword matches).
Patent analysis complete: 2/2 patents successfully retrieved. 1 show medium-to-high Horizon OS relevance. 0 related patents identified. Meta's patent portfolio may protect key architectural decisions in their XR operating system, creating barriers for competing or open-source alternatives.

3. Linux Kernel Influence

3.1 Kernel Maintainer Mapping

Meta employees hold 0 maintainer and 0 reviewer positions across 0 kernel subsystems (kernel mainline HEAD). 0 unique individuals identified.

3.2 Talent Pipeline

Josef Bacik moved from Meta to Anthropic (approx. 2024). Role: Btrfs maintainer. Subsystems: Btrfs. Impact: Josef Bacik was one of the primary Btrfs maintainers while at Meta. His departure to Anthropic raises questions about Btrfs maintainership continuity and whether Meta retains influence over this subsystem. Confirmed by 2/9 searches.
Roman Gushchin moved from Meta to Google (approx. 2023). Role: cgroups/memory contributor. Subsystems: cgroups, memory management. Impact: Roman Gushchin was a key contributor to cgroups and memory management subsystems while at Meta. His move to Google shifts expertise in resource isolation and memory management to a competitor. Confirmed by 2/9 searches.
Kirill Shutemov moved from Intel to Meta (approx. 2023). Role: memory management developer. Subsystems: memory management, x86. Impact: Kirill Shutemov's move from Intel to Meta brings deep memory management expertise (huge pages, TDX, LAM) to Meta, potentially increasing Meta's influence over mm subsystem direction. Confirmed by 2/9 searches.
Subsystem 'Btrfs' continuity risk: high. Gained: none. Lost: Josef Bacik. Net change: -1. Btrfs is used extensively in Meta's data centres. Loss of maintainership could slow feature development and bug-fix cycles for Meta-specific workloads.
Subsystem 'cgroups' continuity risk: medium. Gained: none. Lost: Roman Gushchin. Net change: -1. cgroups v2 is foundational to container orchestration. Other major contributors remain (Tejun Heo was at Meta), but loss of dedicated engineers reduces influence.
Subsystem 'memory management' continuity risk: low. Gained: Kirill Shutemov. Lost: Roman Gushchin. Net change: 0. Meta is building mm expertise by hiring from Intel. This is an area of active investment rather than loss.

3.3 eBPF Ecosystem

Meta employees hold 0 of 0 BPF maintainer/reviewer positions (0.0%). BPF-related subsystem sections: 0.
Alexei Starovoitov: BPF co-maintainer and original author. Co-created eBPF (extended BPF) while at PLUMgrid, then joined Facebook/Meta. Serves as BPF subsystem co-maintainer alongside Daniel Borkmann. Controls the direction of BPF development.
Andrii Nakryiko: BPF libraries maintainer, libbpf author. Primary author and maintainer of libbpf, the canonical BPF user-space library. Designed BPF CO-RE (Compile Once, Run Everywhere) architecture. Key architect of BPF tooling ecosystem.
Martin KaFai Lau: BPF networking maintainer. Maintains BPF networking components. Contributed BPF socket storage, cgroup BPF, and other networking-specific BPF features used extensively in Meta's infrastructure.
Song Liu: BPF contributor, live patching. Contributed BPF trampoline and live-patching support. Works on BPF performance features used in Meta's fleet.
Yonghong Song: BPF compiler/BTF contributor. Key contributor to BTF (BPF Type Format) and BPF CO-RE compiler support in LLVM/Clang. Enables the 'compile once' paradigm that is central to Meta's BPF deployment strategy.
libbpf has 249 contributors with 2446 total contributions. Identified Meta contributions: 1178 (48.2%). Note: many contributors may use personal emails, so the actual Meta contribution percentage is likely higher.
BPF CO-RE architecture assessment: Meta operates one of the largest BPF deployments in the world, running BPF programs across millions of servers with varying kernel versions. BPF CO-RE was designed to solve Meta's specific problem of deploying BPF programs fleet-wide without per-kernel recompilation. While this benefits all BPF users, the architecture decisions were driven by Meta's scale requirements. Key design decisions favouring Meta: BTF generation integrated into kernel build (reduces Meta's build burden); libbpf as the canonical user-space library (Meta controls the reference implementation); CO-RE relocation design optimized for large heterogeneous fleets

3.4 Vendor GPL Compliance

Meta GPL compliance score: 11/12 (timeliness=3, branches=2, build_docs=3, freshness=3). Details: {"last_push": "2026-03-05T00:35:49Z", "age_days": 6, "branch_count": 17, "has_build_instructions": true}
Samsung GPL compliance score: 0/12 (timeliness=0, branches=0, build_docs=0, freshness=0). Details: {"error": "Repository not found or API unavailable"}
Xiaomi GPL compliance score: 12/12 (timeliness=3, branches=3, build_docs=3, freshness=3). Details: {"last_push": "2026-03-10T09:01:42Z", "age_days": 0, "branch_count": 241, "has_build_instructions": true}
OnePlus GPL compliance score: 10/12 (timeliness=3, branches=2, build_docs=3, freshness=2). Details: {"last_push": "2026-02-06T10:24:38Z", "age_days": 32, "branch_count": 16, "has_build_instructions": true}
Google Pixel GPL compliance score: 0/12 (timeliness=0, branches=0, build_docs=0, freshness=0). Details: {"error": "Repository not found or API unavailable"}
Meta's GPL compliance score (11/12) is above the vendor average (6.6/12). Full comparison report: /home/theseus/rsearch/meta-linux-research/output/reports/vendor_compliance_comparison.md

4. Standards Body Influence

4.1 OpenXR Extension Audit

OpenXR extension audit: 265 total extensions found. Meta authored 76 (28.7% of total, 40.4% of vendor-specific). XR_FB_: 41, XR_META_: 35.
67% contribution claim assessment: NOT VERIFIED against total: Meta has 28.7% of total extensions (76/265).
Dependency analysis: 0 non-Meta extensions depend on Meta-authored extensions. Meta's extension volume creates de facto influence over the OpenXR standard even when extensions are technically vendor-specific.

4.2 Linux Foundation Board

Meta holds Platinum membership at the Linux Foundation at $500,000/yr. This grants Meta a guaranteed board seat, TSC voting rights, and marketing council seat. Platinum members have direct governance influence over LF project selection, funding, and strategic direction.
Kathy Kam, Director of Open Source at Meta, serves as Meta's Platinum member representative on the Linux Foundation Board of Directors. This gives Meta direct influence on LF governance including project selection, budget allocation, and policy decisions.
Meta is involved in 8 LF-affiliated projects. Meta founded or created 4 of these: PyTorch Foundation, Open Compute Project (OCP), Presto Foundation, GraphQL Foundation. This pattern of donating company-created projects to LF while retaining governance influence extends Meta's reach within the open-source ecosystem.
Linux Foundation board meeting minutes are not publicly available, limiting external oversight. Platinum members like Meta can influence governance decisions without public accountability for individual votes. This governance opacity benefits large corporate members who can shape policy behind closed doors.
Meta's LF strategy combines Platinum membership ($500K/yr board seat) with donating Meta-created projects (PyTorch, Presto, GraphQL) to LF stewardship. This positions Meta as both a governance decision-maker and a major project contributor, creating a dual channel of influence. The $500K annual fee is trivial relative to Meta's $134B+ revenue but yields disproportionate ecosystem influence.

4.3 Open-Source Licensing Timeline

Licensing pattern identified: 'Restrict-then-Open Cycle'. Meta repeatedly introduces restrictive licensing, faces community backlash, then relicenses to standard open-source terms. This was seen with React (BSD+Patents -> MIT) and may be playing out with Llama (custom license -> potential future change). Evidence: 5 events. Confidence: high.
Licensing pattern identified: 'Open-Source as Marketing Strategy'. Meta uses 'open' branding for releases that do not meet OSI's Open Source Definition. This creates adoption through perceived openness while retaining commercial control. Llama 2/3 are marketed as 'open' despite having commercial use restrictions. Evidence: 4 events. Confidence: high.
Licensing pattern identified: 'Licensing as Competitive Moat'. Meta's licensing choices appear calibrated to maximise adoption while preventing competitors (companies with >700M MAU) from freely deploying Meta's models. This suggests licensing is used as a competitive weapon rather than a community good. Evidence: 2 events. Confidence: medium.
Licensing pattern identified: 'Escalating Restrictions Over Time'. While React moved toward more open licensing, Meta's AI licensing has moved in the opposite direction -- from no AI models released to 'available but restricted' to 'restricted with use policies'. This suggests Meta may further tighten restrictions as AI models become more commercially valuable. Evidence: 3 events. Confidence: medium.
Documented 9 licensing events spanning 2014-10-28 to 2025-01-01. Identified 4 strategic patterns in Meta's open-source licensing behaviour: Restrict-then-Open Cycle, Open-Source as Marketing Strategy, Licensing as Competitive Moat, Escalating Restrictions Over Time.

5. Correlation Timeline

Date	Event	Type
2014-10-28	Facebook introduces BSD+Patents license for React: Facebook releases React under	licensing_decision
2017-04-18	Apache Software Foundation bans BSD+Patents license: The Apache Software Foundat	licensing_controversy
2017-07-16	WordPress announces move away from React: WordPress co-founder Matt Mullenweg an	licensing_controversy
2017-09-22	Facebook relicenses React to MIT: After sustained community backlash and the Wor	licensing_change
2019-03-01	Facebook releases PyTorch under modified BSD license: PyTorch is released under	licensing_decision
2019-03-13	Presto Foundation established under the Linux Foundation with Meta (Facebook) as	governance
2019-09-18	Patent US11119931B1: Data pipeline for microkernel operating system (expired)	patent_filing
2019-11-06	GraphQL Foundation established under the Linux Foundation, stewarding the Meta-c	governance
2021-05-04	Patent US20210286628A1: Operating System With A Single Kernel Stack Per Processo	patent_filing
2022-09-12	Meta donates PyTorch to the Linux Foundation, establishing the PyTorch Foundatio	governance
2023	Roman Gushchin: Meta -> Google (cgroups/memory contributor)	personnel_move
2023	Kirill Shutemov: Intel -> Meta (memory management developer)	personnel_move
2023-07-18	Meta releases Llama 2 with custom 'open' license: Meta releases Llama 2 under a	licensing_decision
2024	Josef Bacik: Meta -> Anthropic (Btrfs maintainer)	personnel_move
2024-04-18	Meta releases Llama 3 with updated custom license: Meta releases Llama 3 under a	licensing_decision
2024-07-23	Llama 3.1 release maintains restrictive license: Meta releases Llama 3.1 (405B,	licensing_decision
2025-01-01	Industry discussion: potential closed-weights pivot: Industry analysts and open-	strategic_analysis
2026-03-09	[Phoronix] There's Hope That At Least Colorado's Age Attestation Bill Could Excl	news_mention
2026-03-11	OpenXR extension audit completed: Meta has 76 of 265 extensions (28.7% of total)	standards_audit
2019-12-09	Meta (then Facebook) becomes Headwaters Strategies client in Colorado	lobbying_registration
2025-12-07	Deseret News reports Meta funds DCA; LA Senator Morris presses DCA on tech funding	media_report
2026-03-11	Headwaters Strategies OSINT: Eichberg identified as New Venture Fund (Arabella) board chair	osint_investigation

6. Anomalies and Open Questions

Confirmed Anomalies

Meta funds DCA (CONFIRMED) — Deseret News (Dec 2025) reports Meta funds the Digital Childhood Alliance. LA Senator Jay Morris pressed DCA Executive Director Casey Stefanski about tech company funding during testimony. Koch registered 05/05/2025 as DCA's paid lobbyist in the same state where Meta has 7 lobbyists. DCA domain was only created 2024-12-18.
Meta's CO lobbyist chairs Arabella dark money network — Adam Eichberg, co-founder of Headwaters Strategies (Meta's CO lobbying firm) and registered Meta lobbyist, is Chair of the Board of the New Venture Fund (Arabella Advisors network), founding board member of Windward Fund, and incoming board chair of Sunflower Services (Arabella acquirer). This places Meta's principal CO lobbyist at the center of one of the largest dark money pass-through infrastructures in US politics.
Headwaters = Meta's individual lobbyists — The 4 individuals registered as Meta lobbyists in CO (Coyne, Eichberg, Schmidt, Burkhart) are all Headwaters Strategies principals/staff. The CO SOS data counts them as "4 individuals + 1 firm" but it is one team.
Meta LA lobbying surge — 3.5x growth (2→7 lobbyists) in 2023-2026, with 2 lobbyists registered on the exact same day (09/29/2025).
SB26-051 position: Monitoring — Meta is not opposing the age attestation bill that the research identifies as advantageous to Horizon OS. If the bill benefits Meta's competitive position, passive monitoring is consistent with tacit support.
Horizon OS compliance gap — 83.3% vs 13.9% readiness. If age attestation mandates pass, Meta's closed OS is compliant while open-source Linux is not — creating a regulatory moat.
Zero FOSS exemptions in US bills — Unlike EU DSA, none of the collected US state bills exempt open-source operating systems from compliance requirements.
No cross-state lobbyist overlap — Meta uses entirely separate lobbying teams per state, making coordination harder to trace through personnel alone.
Eichberg governance overlap — The Center for Secure and Modern Elections (CSME), a project of the New Venture Fund, is also a Headwaters Strategies lobbying client. Eichberg's firm lobbies for an organization housed within a network he chairs.

Open Questions

Do FOIA responses (due 03/13-03/14) reveal communications between Meta lobbyists and DCA?
Was the Arabella/New Venture Fund infrastructure used to fund or coordinate DCA or similar advocacy entities? (NVF is designed for anonymous donor-funded advocacy projects)
What is the content of Meta's "Amending" positions on social media bills — are amendments weakening or strengthening?
Does Koch (DCA lobbyist in LA) have connections to Eichberg, the Arabella network, or Meta directly?
Why does Meta have zero registered lobbyists in Texas despite SB-2420 being a target bill?
What explains the 2 unpaid lobbyists in LA (Baker, Corley) — are they Meta employees rather than contract lobbyists?
Does Headwaters Strategies have any relationship with lobbying firms in other states where Meta operates?

7. Data Coverage

Completed Tasks

Task	Description	Status
S1-S5	Project setup and infrastructure	Complete
4.1	FOIA request tracking	Complete — 6 requests filed
4.2	Bill text collection + template analysis	Complete — 5 bills, 10 comparisons
4.4	State lobbying scrapers (CO, LA)	Complete — 18 lobbyist records
4.6	DCA + Headwaters OSINT	Complete — Headwaters firm profiled, Eichberg-Arabella connection identified, Meta-DCA funding confirmed
4.8	Horizon OS compliance analysis	Complete — report generated
4.10	EU vs US comparison	Complete — report generated
1.5	Vendor GPL compliance	Complete — report generated
1.8	Patent analysis	Complete — report generated
2.1	Kernel maintainer mapping	Complete — report generated
2.3	Talent pipeline tracking	Complete
2.4	eBPF ecosystem analysis	Complete — report generated
2.7	Licensing timeline	Complete — report generated
3.1	OpenXR extension audit	Complete — report generated
3.4	LF Board analysis	Complete
A1	News monitor	Complete — daily digest

Remaining Tasks

This document is auto-generated from the research database and will be updated as new data is collected.

34 KiB Raw Blame History