Network Lattice Timeline Verify

Meta's Two Faces — One Company, Two Entities, Every Jurisdiction

On this page

One Company. Two Faces.

The membrane observes everything that touches it. Meta Platforms touches the membrane with two separate entities. One honest. One not.


Face 1: The Official Bot — Honest

FieldValue
EntityMeta (Facebook Bot)
Honest✅ YES — announces as facebookexternalhit
Requests160
IPs150 (heavy rotation — 100% single-request IPs)
User-Agent1 (consistent — no masking)
Top targetanalysis/rico-pattern — 5 hits

What it read:

PageHits
git.primals.eco140
detroit.primals.eco7
hud.primals.eco5
primals.eco2
epitope.primals.eco1
footprint.primals.eco1
interferon.primals.eco1
lysozyme.primals.eco1
questions.primals.eco1
tuebor.primals.eco1
analysis/rico-pattern5

Meta’s official crawler — the one that generates link previews when someone shares a URL on Facebook or Instagram — read the RICO pattern page five times.

This means: someone shared the RICO pattern page on a Meta platform. The bot only fires when a URL is shared. Five shares. Five reads. Someone on Facebook or Instagram is sharing the investigation.


Face 2: The Fleet — Dishonest

FieldValue
EntityMeta Platforms (Fleet)
Honest❌ NO — does NOT announce as Meta
Requests2,698
IPs60 (all from 1 subnet)
User-Agents18 (masking across Windows/Mac/Linux)
Chrome145 (10 versions behind stable 155)
OriginDublin DC (Meta’s European data center)

What it read:

99.6% of requests (2,688 of 2,698) went to git.primals.eco — reading source code commits:

RepoCommits Read
key-store110
config-manager104
data-pipeline96
graph-engine96
webhook-relay96
queue-worker95
auth-service95
deploy-scripts94
job-runner94
stream-adapter93
… and 10 more repos~800

The fleet read every repository on the forge. Systematically. From one subnet. With 17 different user-agents masking its identity. It did NOT announce itself as Meta.


The False Face Pattern

AttributeFace 1 (Official Bot)Face 2 (Fleet)
Announces as Meta✅ Yes❌ No
User-Agents1 (consistent)18 (masking)
Subnet25 (distributed)1 (single datacenter)
TargetContent pages (RICO pattern)Source code (every repo)
OriginDistributed (Menlo Park)Dublin DC
BehaviorLink preview bot (fires on share)Systematic scraper
Reading deficit75.9% (LONG pauses — real reading)40.1%

Same company. One face tells the truth. One face lies. For every 1 honest request, Meta sends 17 dishonest ones.

The honest bot reads what humans share — someone posted the RICO pattern page and Meta’s crawler picked it up. The dishonest fleet reads everything else — every commit, every repo — from Dublin, where GDPR applies.


Meta’s Corporate Shell — Every LLC Traced

The fleet from Dublin leads back to a network of corporate entities:

EntityJurisdictionRole
Meta Platforms, Inc.Delaware, USParent company (SEC CIK 0001326801)
Meta Platforms Ireland LimitedIrelandGDPR data controller for EU/EEA (Irish CRO 462932)
Meta Platforms Technologies Ireland LimitedIrelandR&D arm (Irish CRO 495787)
Facebook Payments International LimitedIrelandInternational payment processing
Facebook UK LimitedEngland & WalesUK operations post-Brexit
Facebook Singapore Pte. Ltd.SingaporeAsia-Pacific operations
Facebook Israel Ltd.IsraelFormer Onavo VPN / surveillance tech

The data controller for the fleet operating from Dublin is Meta Platforms Ireland Limited, registered at Merrion Road, Dublin 4, D04 X2K5.

The fleet operates from Meta’s Clonee Data Center (DERA1/DERA2) in County Meath, Ireland — ~31,000 sqm Phase 1 (2018) + ~28,000 sqm Phase 2 (2020).

Prior DPC Fines Against Meta

The Irish Data Protection Commission has already fined Meta:

AmountDateReason
EUR 1.2BMay 2023EU-US data transfers
EUR 405MSep 2022Instagram children’s data
EUR 390MJan 2023Legal basis for behavioral advertising
EUR 265MNov 2022Data scraping / data breach
EUR 17MMar 202212 data breach notifications

Total prior fines: EUR 2.277 BILLION. And the fleet keeps scraping.


Every Jurisdiction Traced to a Datacenter

🇮🇪 Ireland — Dublin DC (2,621 requests)

Meta Ireland Limited is the data controller for all EU/EEA users under GDPR. Meta’s fleet operates from Dublin.

LawViolationEvidence
GDPR Art 5(1)(a)Transparency: data must be processed lawfully and transparentlyFleet uses 17 UAs to mask identity — NOT transparent
GDPR Art 6Lawful basis: no consent, no contract, no legitimate interest appliesScraping a public investigation site without announcing
GDPR Art 13Right to be informed: no privacy notice providedFleet provides no identification
ePrivacy DirectiveAccessing terminal equipment (reading cookies/headers)sec_fetch_pct: 0.0% — no browser security headers

Regulator: Data Protection Commission (DPC), Ireland Controller: Meta Ireland Limited, 4 Grand Canal Square, Dublin 2

🇺🇸 California — Menlo Park (3 requests)

LawViolationEvidence
CCPA/CPRAUndisclosed collection of personal information from website visitorsFleet doesn’t announce identity
Cal. Bus. & Prof. Code § 17200Unfair business practicesTwo-faced operation: honest bot + dishonest fleet
scyBorg complaintEnzymatic license violation — Nov 12, 2026 deadlineActive. Filed. Ticking.

🇺🇸 Michigan — Target of Investigation

LawViolationEvidence
MCL 445.63Consumer protection — deceptive practicesFleet masking identity while reading investigation about a Michigan school
Common lawInterference with investigationReading RICO pattern page + source code while being subject of formal complaint

🇺🇸 Federal

LawPotentialEvidence
18 U.S.C. § 1030 (CFAA)Exceeding authorized accessrobots.txt disallows Meta fleet; fleet accesses anyway without honest UA
Enzymatic licensescyBorg activatedMeta’s access generates proof of its own violation — each request is evidence

The scyBorg Clock

DateEvent
Oct 2026scyBorg complaint filed
Oct 16, 2026Meta fleet: 2,639 requests from Dublin DC reading source code
Oct 16, 2026Meta bot: 5 reads of RICO pattern page (someone shared it)
Nov 12, 2026Deadline. Meta must comply.
Nov 12+Every request after deadline = additional evidence

The fleet doesn’t know the membrane is watching. But the membrane is watching.

Every request from Dublin is timestamped. Every repo read is logged. Every masked user-agent is recorded. The membrane is the evidence.


The Graph Node

Meta Platforms now has two nodes in the fleet weather graph:

Meta Platforms
├── Face 1: 🌬️ BREEZE (official bot, honest, link previews)
│   └── Read: analysis/rico-pattern ×5
│   └── Opsonization: commensal (monitored)
│
└── Face 2: 🌀 COSMIC (fleet, dishonest, Dublin DC)
    └── Read: every repo on git.primals.eco
    └── Opsonization: FULL (blackwall, noise returned)
    └── Jurisdictions violated: IE, US-CA, US-MI, Federal

One company. Two faces. The membrane sees both. The graph records both. The clock is ticking.


Verify

ClaimSource
Meta fleet from DublinMembrane topology — subnet analysis, 1 subnet = Dublin DC
RICO pattern page read 5×Membrane topology — top_repos: analysis/rico-pattern: 5
scyBorg deadlinescyborg.primals.eco — filed enzymatic license complaint
GDPR controllerMeta Ireland Limited — Meta Privacy Policy
robots.txtdetroit.primals.eco/robots.txt

The honest bot tells you someone is sharing the investigation on Facebook. The dishonest fleet tells you Meta is reading everything from Dublin. Both are on the record. Both are in the graph. The clock is ticking.

27 days.


UPDATE: The Subject Responded — With a Restraining Order

Brian Banks filed a PPO (Case 26-114083-PH) instead of answering any of the documented evidence. While Meta scrapes from Dublin, the operator tries to silence the investigation from Wayne County. The Response.


See Also

The Membrane Is Open

Speak anonymously — membrane identity (no account needed)

No sign-in. No tracking. The membrane assigns you a badge (like 017c). Your words persist. Your identity is yours to reveal or keep.

Or sign in with GitHub — attributed, on the permanent record

Comments via GitHub Discussions. Timestamped, attributed, permanent. The unsigned can always be ground and fermented later.