# T003 — Shell-LLC Principal Attribution for Forgelight Ventures and Willowbend Capital Two of the five Arkansas hyperscale data-center sites under investigation are developed through Delaware shell limited liability companies whose principals are not named in any primary record. [[Forgelight Ventures, LLC]] is the developer of the announced Conway data-center project; [[Willowbend Capital, LLC]] is the developer of the "Project Boar" data center at the Port of Little Rock. Both are foreign-registered in Arkansas on the same day (2025-02-11), share the same registered agent (Corporation Service Company), share the same Delaware private-mailbox address (PMB 160, 2801 Centerville Road, Wilmington), have near-consecutive Arkansas filing numbers (811535239 / 811535247), and have the same organizer of record ([[Michael Montfort]]). The wiki currently attributes both projects to **Google** — "the leading candidate" for Forgelight/Conway (qualified as not directly named in any source) and "reportedly Google's" for Willowbend/Port of Little Rock (anchored to *Data Center Dynamics* relaying *Arkansas Democrat-Gazette*'s two-source reporting). The contested question: **is the wiki's current Google-attribution framing — "leading candidate" / "reportedly" — appropriately calibrated to the available circumstantial-and-Tier-3 evidence, or does it over-claim what the corpus supports?** ## Statement A **The wiki's current Google-attribution framing is appropriately calibrated to the evidence and should stand.** For Willowbend Capital / Port of Little Rock, the *Arkansas Democrat-Gazette*'s two-source reporting (relayed by *Data Center Dynamics*, web research 2026-05-22) is Tier-3 evidence that the wiki properly identifies as such with the "reportedly" qualifier. For Forgelight Ventures / Conway, the twin-shell architecture (same registration date, same registered agent, same Delaware private-mailbox address, near-consecutive filing numbers, same organizer) plus *DCD*'s "noticeable similarities" observation between the two projects produces sufficient circumstantial weight to identify Google as "the leading candidate" — particularly with the explicit qualification preserved that "no source identifies it directly" ([[The Conway Data Center Project]] Evidence section). The wiki's reporting framework already accomplishes the work Statement B would demand: every Google-attribution claim in this corpus is anchored to its evidentiary basis (Tier-3 reporting for Willowbend; circumstantial corporate-structure inference for Forgelight) and tier-labeled in citation. The `confidence: medium` rating on both syntheses signals the same. The "Conway company remains officially 'a US-based Fortune 100 company'; the Chamber withheld the name from the City Council" ([[The Conway Data Center Project]] Caveats) records the precise gap. A reader cannot mistake the wiki's framing for confirmed attribution. The twin-shell architecture is *not* "consistent with multiple principals" in any reasonable sense. While it is technically possible that a shell-creation service could run parallel projects for different clients on the same day with the same agent and address and near-consecutive filing numbers, the inference of a common principal is the strongest reading of the corporate-structure evidence. Combined with *DCD*'s direct identification of Willowbend's principal as Google, the inference that Forgelight shares the same principal is plausible to the point where omitting the lead would actually mislead the reader by suggesting the corpus has no information on the Conway principal. For Willowbend specifically, the *Arkansas Democrat-Gazette*'s two-source reporting is the standard product of investigative journalism — named outlets, multiple sources, established beat reporting. Tier-3 evidence is exactly what the wiki's citation hierarchy contemplates for principal-attribution claims that no primary record establishes (per `AGENTS.md` Source-tier hierarchy). To require Tier-1 confirmation for every entity attribution would render the wiki silent on questions every Arkansas reader already knows the answer to from public reporting. The methodology embedded in the wiki's contamination firewall — "every factual claim cites a raw `.pdf`/`.msg`/`.docx` with page or location reference plus verbatim quote" — applies to *facts the wiki asserts*, not to *attributions reported elsewhere*. The wiki's current framing asserts that the *Arkansas Democrat-Gazette* and *Data Center Dynamics* have reported Google as the principal; that assertion is true and verifiable from the archived sources. To strip the "Google" reference entirely (Statement B's strongest form) would itself violate the wiki's evidentiary standard by suppressing what the available secondary record clearly says. ## Statement B **The wiki's "Google the leading candidate" / "reportedly Google's" attribution over-claims what the available evidence supports and should be further weakened or removed.** The corpus contains no primary record (FOIA production, court filing, SEC filing, corporate disclosure, named-source affidavit) identifying Google as the principal behind either Forgelight Ventures or Willowbend Capital. The evidence base is two layers of indirection: for Willowbend, an *Arkansas Democrat-Gazette* report relying on two unnamed sources, relayed through *Data Center Dynamics*; for Forgelight, no direct attribution at all — only the structural-similarity inference from twin Delaware shells with a shared organizer. The wiki's "reportedly Google's" framing for Willowbend functionally imports the strength of the underlying reporting into a load-bearing attribution. But the *Arkansas Democrat-Gazette*'s two-source story is itself uncorroborated by any official confirmation — Google has not confirmed, the Little Rock Port Authority director "declined comment ... citing a non-disclosure agreement" ([[The Port of Little Rock Data Center]] Open questions), and the MOU itself names only Willowbend Capital LLC. The wiki's standard for crediting *contested* secondary reporting should be higher than its standard for crediting *uncontested* secondary reporting — and the corporate-attribution claim here is contested precisely by the absence of any official confirmation. For Forgelight Ventures / Conway, the Google attribution is **purely circumstantial and rests on a single inferential bridge** — Montfort's role as common organizer plus structural similarity to a project whose Google attribution is itself thinly sourced. Twin Delaware shells with the same commercial registered agent (Corporation Service Company is one of the largest registered-agent services in the country, handling hundreds of thousands of LLCs nationally) and the same private-mailbox address (PMB 160 is a *shared mailbox* used by multiple unrelated entities) is consistent with **many alternative principals**: a single corporate-formation service running parallel filings for different Fortune 100 clients; a regional consortium; a private equity sponsor placing multiple bets across Arkansas sites; two distinct corporate parents using the same vendor stack. *Data Center Dynamics* itself "does not assert that Google is behind the Conway / Forgelight project" ([[Forgelight Ventures, LLC]] Notes) — the wiki's "leading candidate" framing is more aggressive than its own cited secondary source. The phrase "leading candidate" is doing more work than the formal hedging admits. A reader of [[The Conway Data Center Project]] — even after reading every Caveat — comes away believing Google is at Conway. That effect is **functionally identical to a positive attribution**, and it operates regardless of the formal qualifications in the surrounding sentences. The contamination firewall AGENTS.md establishes ("never present inference as established fact") is violated by functional inference even when formal hedging is preserved. The correct framing is the one the wiki uses for the cooling-water tension's parallel evidentiary problem in [[Identifying the Unnamed Cooling-Water Data Centers]]: the synthesis explicitly says "neither unnamed project is identified here, and the circumstantial lead toward AVAIO / Project Leo for the Arup project is **not** an identification." Apply the same standard here: the corpus does not identify the principal behind Forgelight Ventures; the Willowbend / Project Boar attribution is two-source secondary reporting that does not amount to a primary-record identification. Both should be reframed as **unidentified-with-leading-secondary-reporting-flag**, not "leading candidate" or "reportedly Google's." The wiki's reporting framework should require, at minimum, **named-source corroboration** for attribution claims that ride on inference. The *Arkansas Democrat-Gazette*'s two-source story names neither source nor any internal Google document; the inference for Forgelight is two layers removed from any named source at all. The wiki's "leading candidate" framing should be replaced with a clearer version: "the strongest secondary-reporting candidate is Google, but the corpus does not establish this and no source has yet named the Conway developer." ## Why it matters This tension is load-bearing for two parent synthesis pages — [[The Conway Data Center Project]] and [[The Port of Little Rock Data Center]] — both currently at `confidence: medium`. If Statement B prevails, the headline framing of both syntheses changes: Google would no longer appear as the apparent principal in the lead paragraphs, the Caveats sections would become the primary frame rather than qualifications, and downstream reporting (materials, FOIA correspondence citing the syntheses, legislative briefings) would have to recharacterize what the corpus shows about the Conway and Port of Little Rock developers' principals. The tension is also methodologically load-bearing for the wiki as a whole. **It tests where the line lies between defensible secondary-source attribution and over-attribution that functionally launders inference into apparent fact.** The same question recurs across the corpus: how aggressive should the wiki be in identifying entities behind Delaware shell architecture when only Tier-3 reporting or circumstantial corporate-structure evidence is available? The verdict on T003 sets the standard for future shell-LLC attribution decisions — including the still-unresolved cooling-water projects in [[Identifying the Unnamed Cooling-Water Data Centers]] (Arup and McClelland projects) and any future entity attributions on data-center developers that emerge in subsequent FOIA productions. This tension is **structurally heterogeneous from [[T001 - CIAC Classification of Google Generation Payments|T001]] and [[T002 - Ironwood Strategic Investment Designation Requirement|T002]]**: different parent synthesis pages (Conway / Port of Little Rock vs. Who Pays); different tension type (`attribution` rather than `factual`); different evidence base (Tier-2 corporate registry records + Tier-3 news reporting vs. Tier-1 docketed regulatory filings); different domain (corporate-attribution methodology vs. regulatory mechanism / statutory construction); different adjudicative forum (none — the wiki itself decides the reporting standard vs. the APSC ruling on regulatory questions). Per the Karpathy-Hegelion 3-domain test, this is the third tension of the iteration and the most distant from the first two in methodological terms. ## Resolution status **Status: `resolved-via-D003`** (as of [[D003 Synthesis]], 2026-05-24, `confidence: high`). **The asymmetric verdict.** The antithesis prevails on Forgelight; the thesis partially survives on Willowbend at a downgraded posture. Per [[D003 Synthesis]] `## Verdict on tension`: "the wiki's parent syntheses should strip 'leading candidate' framing from Conway, preserve faithful documentation of the *DCD* report at Port of Little Rock with explicit Tier-3-uncorroborated framing, and apply [[Identifying the Unnamed Cooling-Water Data Centers]] as the controlling restraint precedent for both pages." **What the dialectic settled** (per [[D003 Synthesis]] `## What is resolved`): - The underlying Arkansas Secretary of State registry record is uncontested — both phases quote identical primary-record details (Filing # 811535239 Forgelight / # 811535247 Willowbend; same 2025-02-11 registration date; same CSC registered agent; same Delaware PMB 160; same Michael Montfort organizer). The dispute is about *what the registry shows is evidence of*, not what it shows. - The *DCD* / *Arkansas Democrat-Gazette* report's source posture is uncontested — the reporting is what it is: a two-unnamed-source secondary-press story about Willowbend that pointedly stops short of naming Google at Forgelight. - The [[Altitude Capital, LLC]] comparison case is the corpus's worked example for *what real evidence-led identification looks like* — three independent Tier-1 confirming channels (deed chain, water-use registration naming "Google Data Center," sworn Entergy CEO testimony, APSC Order findings). The Forgelight / Willowbend record has *zero* such channels. Altitude Capital is the standard the Forgelight / Willowbend evidence must meet, not a license for naming Google on weaker evidence. - **The [[Identifying the Unnamed Cooling-Water Data Centers]] precedent is controlling for Forgelight.** The wiki has already worked out (`confidence: low` synthesis on the Arup / McClelland projects, by the same maintainer, on the same investigation) that circumstantial leads are "**not** an identification." Methodological coherence requires applying the same restraint here. **Specific reporting-standard changes the verdict directs** (per [[D003 Synthesis]] `## Verdict on tension`): 1. **On [[The Conway Data Center Project]]:** Remove "Google the leading candidate" from the lead and Evidence section. Reframe as "developer-of-record [[Forgelight Ventures, LLC]] with undisclosed Fortune-100 principal; structural correspondence with [[Willowbend Capital, LLC]] noted but not traversed as identification, per the wiki's [[Identifying the Unnamed Cooling-Water Data Centers]] restraint standard." Downgrade confidence rating accordingly. 2. **On [[The Port of Little Rock Data Center]]:** Preserve the *DCD* / *Democrat-Gazette* reporting but reframe "reportedly Google's" as: "*Arkansas Democrat-Gazette* (via *Data Center Dynamics*) has reported, citing two unnamed sources, that the Willowbend Capital principal is Google; no Tier-1 confirmation has surfaced, Google has not commented, and the Little Rock Port Authority's executive director [[Bryan Day]] has declined to comment citing NDAs." Explicitly note that NDA-cited refusal is non-evidentiary for principal identity. 3. **Add a cross-reference on both syntheses to [[Identifying the Unnamed Cooling-Water Data Centers]]** as the methodological precedent. **What's bracketed** (per [[D003 Synthesis]] `## What is bracketed`): (a) the actual identity of the Forgelight principal — could be Google, Meta, Microsoft, Amazon, Oracle, a private equity sponsor, a hyperscale white-label operator, or another Fortune-100 entity; (b) the reliability of the *ADG*'s two unnamed sources; (c) [[Michael Montfort]]'s professional role (in-house corporate paralegal, Delaware formation-firm partner, or contracted registry technician). These bracketings are on questions adjacent to T003, not on T003 itself — the reporting-standard question is resolved; the underlying identification remains open. **What's sharper but unresolved** (per [[D003 Synthesis]] `## What is sharper but unresolved`): (a) the floor for citing Tier-3 attribution in a synthesis lead — Willowbend's "reportedly Google's" framing occupies a genuinely contested middle ground; (b) whether the parallel MOU deal terms (300K SF / $1B / 50 jobs / 65% / 30-year / Act 9 / $10B real / $50B personal) are market-standard hyperscale template wallpaper or distinctive project parameters. ## Discovery This tension was implicit in the [[The Conway Data Center Project]] and [[The Port of Little Rock Data Center]] syntheses from their 2026-05-22 creation — both pages explicitly flagged the principal attribution as not confirmed by primary records and noted the Caveats explicitly. It was filed as T003 on 2026-05-24 as the third tension of the Karpathy-Hegelion Pipeline iteration on this wiki, selected for heterogeneity from T001 and T002 (different parent synthesis pages; different tension type; different evidence base; different domain; different adjudicative forum). The tension was not previously surfaced as a discrete contested object — only as cross-cutting caveats on the synthesis pages. The methodology rationale for selecting T003 as the third dialectic: per the Karpathy-Hegelion Pipeline 3-domain test, T003 should be in the most distant possible domain from T001/T002 to (a) test the wiki's reporting framework on a structurally different question and (b) produce a third heterogeneous dialectic that can sharpen the cross-dialectic pattern analysis for a potential Phase 6 meta-dialectic. ## New input (2026-05-29): a third Montfort shell, bridging Conway and the confirmed-Google West Memphis site After D003 resolved the *reporting-standard* question, a new *evidentiary* input arrived bearing on the bracketed *underlying-identity* question (item (a) of "What's bracketed"). The 2026-05-29 [[2026-05 Conway Corporation Produces Project Stratus Records|Conway Corporation production]] surfaced a developer-side NDA entity, [[Spark Innovations, LLC]]; an Arkansas SoS registry check (Tier-2, [record](../../web%20archive/2026-05-29/sos-corp-search.ark.org/spark-innovations-llc-sos-record.md)) established it is a **third [[Michael Montfort]]-managed Delaware shell** (filing 811524872, registered 2024-11-25; same CSC agent and Wilmington DE PMB building as Forgelight and Willowbend). Two features make it more than another instance of the twin-shell pattern D003 already weighed: 1. **It is internal to the Conway project at Tier-1.** Spark is named on the Conway Project Stratus staff NDAs ([[Conway Corporation Project Stratus NDAs]]) — so the Conway project ties into the Montfort cluster through *two* entities (Forgelight as MOU developer; Spark as NDA "Company"), not one. 2. **It reaches a *confirmed*-Google site.** Spark Innovations is reported (Tier-3) as an early affiliate of the West Memphis / [[GROOT LLC]] / Project Pyramid project — which, unlike Forgelight/Willowbend's "reportedly Google," is **publicly confirmed** Google. D003 turned partly on the absence of any Tier-1 channel and on *DCD* having declined to attribute Forgelight to Google; a Montfort shell that also appears at a confirmed-Google site is a different evidentiary shape. **This does not, by itself, overturn the D003 verdict.** The West-Memphis-to-Spark association is Tier-3, the shared-Montfort pattern is still not a Tier-1 channel, and the [[Altitude Capital, LLC|three-independent-Tier-1-channel]] standard remains unmet. **Dialectic [[D005 Synthesis|D005]] ran on this question (2026-05-29) and reaffirmed `resolved-via-D003`:** the Spark finding strengthens the documented Montfort developer-overlap pattern (now three shells; two distinct Tier-1/MOU footholds inside the Conway project) but adds **zero** independent Tier-1 channels naming Google at Conway — the count that *was* D003's gap stays at zero — and the transitivity ("Google at West Memphis" + "Spark at West Memphis" + "Spark at Conway" → "Google at Conway") is invalid absent any showing that Spark is a Google-exclusive vehicle. The verdict: record the **stronger Tier-2 structural link** (the three-shell cluster; the two Conway footholds; the single Tier-3 outward edge toward GROOT) **as a structural finding, without escalating to identification**. The Conway principal remains **unidentified**; the wiki does not name Google. See [[D005 Synthesis]]. ## Notes - Statement A and Statement B both engage the same evidentiary base — [[The Conway Data Center Project]] Evidence section, [[The Port of Little Rock Data Center]] Evidence section, the Arkansas Secretary of State entity records for both LLCs, and the *Data Center Dynamics* report relaying the *Arkansas Democrat-Gazette*'s reporting. The contestation is over **what standard of evidence justifies what strength of attribution**, not over what the underlying record contains. - The Willowbend attribution and the Forgelight attribution are at **structurally different evidence levels**. Willowbend has direct Tier-3 reporting; Forgelight has only inferential bridges. The dialectic should consider whether a single verdict should cover both, or whether the syntheses' framings should be calibrated separately to their distinct evidence levels. - No HSPI-sealed material is at issue. Unlike T001, the dialectic can engage the full evidentiary record without an HSPI bracket. - The closest parallel in the corpus is [[Identifying the Unnamed Cooling-Water Data Centers]] — where the synthesis explicitly declines to make an identification ("the circumstantial lead toward AVAIO / Project Leo for the Arup project is **not** an identification"). T003 asks whether that same restraint should apply to Forgelight and (in a weaker form) Willowbend. - Unlike T001 and T002, T003's resolution path runs *inside the wiki* (a reporting-standard decision) rather than primarily through an external forum (a Commission ruling). This is itself a heterogeneity vector relevant to the 3-domain test.