Power vs. Capacity: What Is Actually Scarce

Power is not the same thing as capacity. In digital infrastructure, "megawatts" are often treated as a proxy for deployable compute, but in practice power is a stack of constraints that must clear sequentially before electricity becomes usable, revenue-generating capacity. This is why headline MW figures can be directionally informative yet economically ambiguous. What matters is not whether power exists in theory, but whether it is deliverable, financeable, and energizable on a timeline that survives real-world bottlenecks.

The first distinction is between interconnection and delivery. Interconnection is the right to connect to the grid at a specified load; delivery is whether that load can be served reliably and economically across seasonal peaks, congestion, and curtailment regimes. A project can point to contracted or "available" power while still facing binding constraints in queue studies, network upgrades, or firm service conditions. Even when interconnection is real, deliverability can be conditional, and the economic value of a megawatt can vary materially depending on node constraints, demand charges, congestion pricing, and curtailment provisions.

Infrastructure and lead times create a second layer of scarcity. Substations, transformers, switchgear, and transmission upgrades are physical bottlenecks with long procurement cycles. Permitting and land-use approvals can be equally binding and often non-linear, particularly when local stakeholders or environmental requirements become gating items. In parallel, commercial terms matter: pricing, indexation, termination rights, curtailment language, and credit support can determine whether "cheap" power stays cheap through cycles and whether the asset retains optionality when conditions change. These constraints are why two assets with similar MW claims can have very different intrinsic value.

This is also why "powered land" and "powered capacity" should be treated as different states. Powered land can represent genuine option value, but it is not the same as energized, usable capacity. The practical question is conversion: what is the realistic path from land and intention to deliverable, energized load, and how much execution risk is embedded in that path? Some projects are genuinely near-term, with interconnection secured, equipment paths mapped, permitting substantially de-risked, and an execution history that supports timelines. Others are earlier-stage options that may be real but should be valued as such, with explicit discounts for queue uncertainty, upgrade scope, procurement lead times, and financing conditions.

When we evaluate "power" claims, we focus less on the number and more on the state of the stack: the quality of interconnection, the realism of deliverability, the capital required to energize incremental MW and whose balance sheet funds it, the specific contract terms that govern curtailment and pricing, and the timeline implied by equipment and permitting realities. The intent is not skepticism for its own sake; it is precision about which layer is actually scarce.

The bottom line is that scarcity in digital infrastructure is often not "power" in the abstract. Scarcity is more commonly deliverable power at the right node, time-to-energize, and infrastructure readiness that converts plans into operating capacity. Getting this distinction right is a prerequisite for separating durable, long-duration assets from headline MW that may not be monetizable on the timeframe the market is discounting.

This note is for informational purposes only and does not constitute investment advice or an offer or solicitation to buy or sell any securities. Any offering by Twill Capital, LLC would be made only to qualified investors through confidential offering materials.