Skip to content

IN DEVELOPMENT · NO CHIP HAS BEEN TAPED OUT

Silicon for the vendors who build the machine

BramHA is eventually for robot makers: the vendors and integrators who build the machine. It is intended as a part they build in, beside Czar Chassis and not instead of it. Nothing can be ordered.

· 4 min read

IN SHORT

BramHA is eventually for robot makers: the vendors and integrators who build the machine. It is intended as a part they build in, not a product an end facility buys. It sits beside Czar Chassis, through which a vendor offers the Grid under its own name. The program is in development, nothing can be ordered, and there is no partner intake.

A chip for a robot's control and motion is not something a facility buys. It is something the maker of the robot builds in. BramHA is eventually for those makers: the vendors and integrators who build the machine.

The program is in development. No chip exists and nothing can be ordered. This article describes who the silicon is intended for, how that sits beside Czar Chassis, and what a robot maker can and cannot know today.

A part, built in

The four jobs BramHA is being designed for are control, motion, sensing, and identity. Each sits deep inside a machine: at the controller, at the joint, beside the sensors, at the point where the machine joins a network.

Choices at that depth are made by whoever designs the machine. A robot maker selects a controller, designs the joints, writes the control software, and builds the safety case around all of it.

So the silicon is intended as a part. A vendor would build it in, as it builds in any other part, under its own design. The chip may run the vendor's control loop. The loop and the safety case remain the vendor's. Where safety lives sets that out.

Why not the facility

An end facility buys machines, not the parts inside them. It cares what a machine does, how it is supported, and whether it can be trusted on the site's network.

What Element 31 has for the facility is a different thing: the inference pool. A Czar Grid serves perception, decisions, and adaptation to every machine in a facility, from any vendor, over the site's own network.

A facility would meet BramHA only indirectly, inside a machine it bought from a maker that chose to build the part in. Even then, the one job a site would notice is identity: a machine that can prove what it is and what it is running before the site lets it on the network.

Beside Czar Chassis

Robot vendors and integrators already have one route into Element 31's family. Czar Chassis is how a vendor or integrator offers the Grid under its own name, with its fleet. The vendor's customers get the vendor's machines and the vendor's inference pool, presented as the vendor's product.

BramHA would sit beside that, on the other side of the link.

Chassis concerns the pool. It is about the heavy AI work, served from inside the building, carrying the vendor's name.

The silicon concerns the machine. It would be a part inside the vendor's own robot, doing the work that cannot wait and cannot fail.

The two are separate. A vendor can use Chassis with machines built on any electronics. Nothing in the program describes the silicon as requiring Chassis, or the reverse. And the boundary between the two sides holds either way: the Grid is not a controller and does not sit inside any real-time or safety loop, whoever's name is on it.

There is also a difference in status that should not be blurred. Czar Chassis is a way to use a product that exists. BramHA is in development.

What a robot maker would be weighing

When there is something to evaluate, the program's intent suggests what a robot maker would be looking at.

A small part with a narrow job. The first design is a real-time controller with a root of trust. It is not a vision processor or an AI accelerator, and a small first design does little.

Mature process nodes. The program's reasoning is that these suit parts built into machines with long working lives. The cost is more area and power for each unit of compute.

Nothing can be ordered

Today there is nothing for a robot maker to evaluate, and it is better to say so than to imply otherwise.

No chip has been taped out, and no chip exists. The specification of the first design is not published. The process and the foundry have not been announced. There are no performance, power, or price figures. No safety or functional-safety certification is claimed.

Nothing can be ordered, and there is no partner intake. Can I buy a BramHA chip? gives the same answer in brief.

Questions this raises

Can a robot maker order or sample a BramHA chip?
No. No chip has been taped out and no chip exists. Nothing can be ordered, and there is no partner intake.
Does a vendor need Czar Chassis to use BramHA?
The two are separate. Czar Chassis is how a vendor or integrator offers the Grid under its own name with its fleet. The silicon is intended as a part inside the machine. Neither is described as requiring the other.
Would a facility buy BramHA directly?
No. It is intended as a part a robot maker builds into a machine. A facility would meet it, if at all, inside a machine it bought from that maker.

KEEP READING