HEARTHCube mark
HEARTHCube · Configuration A

Bring the power with the machine.

A sovereign AI compute island engineered as one object: compute, persistent generation, storage, thermal systems, deterministic control and evidence.

Pre-build design basis · Unit One will convert architecture into measured evidence.

Concept visualization of HEARTHCube at twilight
The machine

One object. Three physical domains.

Configuration A is one Alpha and one Bravo joined by the HEARTH Spine. The separation is deliberate. The integration is the product.

Alpha

Sovereign compute

Two independently isolatable immersion Compute Cells, eight accelerators per cell, approximately 31 kW mission IT inside a 36 kW operating ceiling.

HEARTH Spine

Controlled interfaces

DC power, dual-grade thermal transfer, deterministic communications, safety, bonding, evidence and service access.

Bravo

Persistent generation

A roughly 60 kWe-class solid-oxide fuel-cell source, approximately 300 kWh-class LFP storage, grid-forming conversion and the thermal plant.

HEARTHCube Configuration A cutaway
Design basis visual · Configuration ANot a fabrication drawing
Alpha

Compute that can be isolated, metered and scheduled.

The compute side is engineered as two cells rather than one undifferentiated payload. Each cell has its own power and cooling boundaries so maintenance, measurement and operating experiments can happen without treating Alpha as a black box.

Alpha compute module cutaway
Concept visualization · Alpha compute module · design intent only
HEARTH Spine interface corridor
Design basis visual · named interfaces, bounded domains, one machine
HEARTH Spine

The interface corridor is part of the architecture.

The Spine carries the coupling JSE intends to own: power, thermal transfer, control, safety, bonding, evidence and service access. That interface constitution is what allows the machine to evolve without losing its identity.

Bravo

Persistent power. Fast electrical support.

Bravo is the island power plant. Slow generation, fast storage and grid-forming conversion are designed as one electrical system, then coupled to a thermal architecture that can use heat where a real sink exists and reject it safely where one does not.

Bravo island power plant cutaway
Concept visualization · Bravo packaging remains subject to vendor and site closure
HEARTHCube system boundary diagram
Design basis visual · system boundaryClaims are adjudicated at the boundary appropriate to the claim
Unit One

The first machine is a measuring instrument.

Unit One is not required to exhibit mature fleet economics. It is required to produce the evidence that lets the next unit be engineered, financed and sold with less ambiguity.

~31 kW
Mission IT
Unit One operating basis.
36 kW
Compute ceiling
Current Alpha operating limit.
~60 kWe
Persistent generation
Solid-oxide fuel-cell class.
~300 kWh
Electrical storage
LFP class, current design basis.
HEARTH thermal ladder showing heat capture, preservation, reuse and dry rejection
Controlled thermal design basis · useful heat is optional, dry rejection is mandatory
Thermal doctrine

Preserve the grade. Use what is real.

Alpha and Bravo heat are physically separate because they are not thermodynamically equivalent. Direct reuse is preferred when a legitimate sink exists. Temperature lift or time-shift is optional. Dry rejection remains the safe end-state.

Configuration C

Scale by federation. Not by losing the boundary.

The controlled scale thesis is four to eight Alphas around one materially different Bravo-C. The visual at right is intentionally conceptual: the architecture scales only when the shared plant, interfaces and fault domains are engineered to support it.

Conceptual multi-module HEARTHCube cluster
Concept art · not Configuration C geometry · not as-built
Where the work begins

Does the site deserve the machine?

HEARTHCube begins with deployment fit: workload, power timing, sovereignty, physical site and the economic cost of waiting.