GROUNDWORK

AI + EARTH · AN EDITORIAL JOURNAL

ISSUE 037WEEK 37

THIS WEEK, FOLLOW THE SIGNAL

Where doesa prompt go?

A question begins as language. Its answer passes through models, hardware, electricity, cooling, and a real place. This week, we follow the route from a sentence to the coast of Finland.

Editorial landscape · not photography of the Hamina facility
THE WEEKLY JOURNAL

GROUNDWORK 037

The interface feels weightless.
The system beneath it is not.

Groundwork looks past the smooth surface of AI and follows the physical relationships beneath it—without turning uncertainty into a slogan or complexity into a reason to look away.

THE PHYSICAL LAYER

Look past the interface.
The story continues below it.

Photography sets the atmosphere. Evidence tells us what is actually happening.

Editorial landscape · not photography of the Hamina facility

THE EARTH REPORT

One story.
Four honest angles.

Hamina, FinlandSeptember 7, 2026

This week: seawater cooling, recovered heat, and the physical route beneath an AI response.

01

The Win

Designing the facility as part of a place.

In Hamina, seawater cooling and a district-heating connection make the data center legible as local infrastructure—not an invisible cloud. The project does not erase impact, but it shows how heat can be treated as a resource when a compatible network exists.[7][8][9]

02

The Tradeoff

A global percentage can hide a local constraint.

Data centers remain a minority of global electricity demand, yet their loads are concentrated. A project can look modest in a worldwide total while materially affecting one grid, water system, neighborhood, or planning process.[5][10]

03

What We Learned

A digital answer has a physical route.

A prompt becomes tokens, tokens are processed by a model, and the computation runs on hardware. Electricity, cooling, buildings, networks, and geography sit beneath the answer—even when the interface makes them disappear.[1][6]

04

What We Can Do

Ask where, when, how much—and for whom.

Choose a system suited to the task. Ask what is measured, where the computation runs, which grid and cooling system serve it, and whether efficiency gains reduce total demand or simply make more use possible.[5][6]

UNDER THE SURFACE

The route beneath
a single response.

This is a conceptual path, not a measurement of one product. The exact model, tools, hardware, and facility can change every step.

  1. 01

    Prompt

    Language enters the system.

    You write or speak a request. The product may add instructions, earlier conversation, retrieved documents, or search results before sending context to the model.

  2. 02

    Tokens

    Text becomes processable pieces.

    A tokenizer represents text as tokens—often words, subwords, punctuation, or other character sequences. The boundaries depend on the tokenizer and language.

  3. 03

    Context

    Relationships are evaluated.

    The model uses learned parameters and the available context to estimate which token should come next. Modern systems commonly use Transformer-based attention mechanisms.

  4. 04

    Response

    Prediction repeats.

    The selected token is added to the sequence and the process repeats. The language model generates the response; any search or retrieval comes from additional systems around it.

  5. 05

    Infrastructure

    Hardware performs the computation.

    Servers, accelerators, memory, storage, networking, cooling, and backup equipment support the request. Their contribution varies by system and facility.

  6. 06

    Place

    The answer lands somewhere.

    The local electricity system, climate, cooling design, water conditions, and community determine what the physical demand means in that place and moment.

Language-model mechanics: [1][3][4]
Physical infrastructure: [5][6]

FOLLOW THE WHOLE SYSTEM

NEW TO GROUNDWORK?

Three foundations.
No classroom required.

These Field Notes stay between issues. Read one now or return when a weekly story raises the question.

  1. 01What is a large language model?
  2. 02How does tokenization work?
  3. 03Training versus using a model

THE WIDER JOURNEY

Language becomes computation.
Computation becomes place.

Move through the system slowly—from the words on the screen to the infrastructure and community beneath them.

FOLLOW THE SYSTEM

EVIDENCE, METHOD & CREDIT

Trust should remain inspectable.

Citations stay visible in the story. Full context waits here when the reader wants it, rather than interrupting every paragraph.

01Sources and claim context
  1. 01

    Google for Developers · Developer education

    Introduction to Large Language Models Living educational documentation; checked August 30, 2026

    Supports the explanation of language models, tokens, context, and next-token prediction. Provider-authored education is used for mechanics, not environmental performance claims.

  2. 02

    OpenAI · Model-provider tool

    Tokenizer Living documentation; checked August 30, 2026

    Provides a model-specific way to inspect tokenization. Groundwork does not present one tokenizer's boundaries as universal.

  3. 03

    Google for Developers · Developer reference

    Machine Learning Glossary Living glossary; checked August 30, 2026

    Supports the plain-language distinction between training, inference, parameters, serving, and model use.

  4. 04

    Vaswani et al. · Primary research paper

    Attention Is All You Need June 12, 2017; revised August 2, 2023

    Introduced the Transformer architecture based on attention mechanisms. It is included as primary technical history, not as a claim that every current language model is identical.

  5. 05

    International Energy Agency · Intergovernmental analysis

    Energy and AI — Executive summary April 10, 2025; checked August 30, 2026

    Supports the physical connection between training and deploying AI models, data centers, electricity demand, and concentrated local effects.

  6. 06

    International Energy Agency · Intergovernmental analysis

    Energy demand from AI April 10, 2025; checked August 30, 2026

    Supports the description of data-center equipment and the need to consider both efficiency and total demand.

  7. 07

    Google Data Centers · Facility-operator source

    Hamina, Finland Current facility profile; checked August 30, 2026

    Supports the facility-specific description of seawater cooling and Google's stated heat-recovery goals. Operator claims remain attributed.

  8. 08

    Haminan Energia Oy · Local utility source

    Data-center heat for Hamina's district-heating network 2024; checked August 30, 2026

    Describes the heat-pump project and its stated design potential. Design capacity is not presented as verified annual delivery.

  9. 09

    City of Hamina · Local-government source

    The impacts of the Hamina data center as a research target June 22, 2026; checked August 30, 2026

    Provides current local context and reports that heat from data-center cooling is being directed to the district-heating network.

  10. 10

    Lawrence Berkeley National Laboratory · U.S. national-laboratory report

    2024 United States Data Center Energy Usage Report December 19, 2024

    Supports the distinction between direct cooling-water use and indirect water associated with electricity generation. U.S. findings are not treated as universal facility averages.

02Image credits and usage context

Groundwork uses atmospheric landscapes as editorial context. They are not presented as photography of the Hamina facility.

Unsplash license