One pool for every cell in the fabrication hall

A yard builds a few very large things with equipment from many suppliers. The welding robots came from one, the blast and paint cells from another, the inspection cameras from a third, and the drones and crawlers that survey the hull from a fourth, chosen job by job over years. Each arrived with its own vision, its own model, and its own idea of where the data goes. The hull is the customer's and the yard's; its survey imagery should not be anyone else's. A pool in the yard serves every cell and keeps the survey.

What is in the hall

A fabrication hall is a sequence of cells, each doing one hard thing to a block of steel. Welding robots lay seams along panels and stiffeners, guided by vision that finds the joint and watches the pool of metal. Blast cells strip and profile the surface before paint, with cameras that judge whether the surface is ready. Weld-inspection stations look at every seam for the defects that would otherwise be found at survey, or at sea. Outside the hall, drones fly the hull and crawlers walk the tanks, producing the survey imagery that follows the ship for its life.

Each of these machines carries a small model and wants a larger one. The welding robot can track the seam; judging the seam it just laid is a bigger question. The blast cell can see the surface; deciding it is ready is a judgment the yard would rather make with its own standard than the supplier's. The survey drone produces more imagery of this hull than anyone has time to look at.

Why the cloud and a GPU on every machine both fail here

Each cell's supplier brings a separate AI system, and each is a separate uplink out of a hall that would rather have none. Weld inspection should answer at the cell, inside the cell's cycle, not a round trip to a distant region later. And hull survey imagery belongs to the yard and its customer; a cloud that learns on it is a cloud that has taken it.

A GPU on every machine fails on the floor itself. A fabrication hall is a hard place to keep delicate compute alive: grit, heat, spatter, and vibration are the working conditions, not exceptions. Compute sized for each cell's hardest moment sits idle while the block is moved. And what the inspection camera learns about this yard's seams stays with that supplier, so the next cell learns it again or never does.

What the pool serves

The first thing the pool serves is the cells. Welding robots, blast cells, and weld-inspection vision from several suppliers are served from one Czar Grid over the yard's own network. Substrate's Inference service answers each cell inside the budget its supplier set: the robot tracks the seam, the pool judges it. A seam flagged at the cell is reworked at the cell, while the block is still in front of the robot, rather than found at survey. Evaluation writes the model version beside every judgment, so a weld passed in the hall can be reconstructed when the surveyor asks. Safety, stops, and motion limits stay on the robot as the vendor built them; the pool answers questions, it does not drive the machine.

Tasks that cross cells belong to the yard, not to any one supplier. Agency Studio lets the yard write a block's inspection sequence, or the handover check between blasting and paint, as a bounded task approved by a named role, recorded, and replayable. The sequence is the yard's, and so is the record of every run.

The second thing the pool serves is the hull survey. Drone and crawler survey runs on site, on the pool, and the models improve on the yard's own hulls. Adaptation runs overnight on the yard's own captures, so the survey model learns how this yard's steel, this yard's paint, and this yard's seams actually look. Memory and Retrieval let a surveyor pull every image of a frame or a tank across the build. Where a yard wants a season of survey footage worked through in bulk, the Compute network is being built for that kind of overnight batch job; the inspection that happens at the cell never leaves the yard.

What stays in the yard and who holds the record

The pool can be air-gapped, or connected only to systems the yard already secures. Local Bridge permits the routes the yard declares, one by one: the production system, the quality record, the customer's survey portal if the yard chooses. Each supplier's software is a route, not a path out. Watchman verifies the integrity of what is running. The survey imagery, the weld judgments, and the task records stay on the Grid, in a record the yard and its customer hold and an auditor can read without a supplier's export.

How it is placed and bought

Czar nodes go in the yard's own rack, in the room that already holds the network equipment and the production system, away from the grit of the hall, on the yard's own network. The subscription is for the configured Grid as one line, with hardware, platform license, and sustainment together, fixed for the term; a new cell on the pool does not move it. Where a supplier ships the Grid under its own name with its cells, that is Czar Chassis, and the yard still holds its own record.

A ship is surveyed for as long as it floats, and the yard that built it is asked about it for as long. A pool in the yard means the answer is in a record the yard kept, on hardware the yard owns, learned on the hulls the yard built.