Is BramHA safety certified?
No. No chip exists, so there is nothing to certify, and no safety or functional-safety certification is claimed. The safety case for a machine is the robot maker's.
· 3 min read
IN SHORT
No. BramHA is in development. No chip has been taped out and no chip exists, so there is nothing to certify. No safety or functional-safety certification is claimed, and none should be implied. The silicon is being designed as a part a robot maker may build in. The safety case is the robot maker's design and responsibility.
No. BramHA is not safety certified, and no safety or functional-safety certification is claimed for it.
The first reason is the simplest one. BramHA is in development. No chip has been taped out and no chip exists. There is nothing that could have been assessed. The rest of this article explains what the silicon is in relation to safety and who holds the safety case.
Nothing exists to certify
A certification is a finding about a particular part or system, reached by examining it. The program has no part to examine.
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.
So any statement that BramHA is certified, rated, or qualified for safety would be false today. The program makes no such statement. It also makes no statement about certification in the future, and nothing in this library should be read as a plan or a promise.
A part, not a safety system
BramHA is being designed as a part a robot maker may build into a machine. Its four jobs are control, motion, sensing, and identity. The first design is a real-time controller with a root of trust.
A controller sits close to things that matter for safety, and the chip may run a vendor's control loop. That does not make the chip a safety system.
A safety system is designed, analyzed, and demonstrated as one, inside a particular machine. A part is something the maker of that machine selects. What role a part plays in a machine's safety, if any, is for the maker to decide and to show. Where safety lives goes through this in full.
The safety case is the robot maker's. A robot is made safe by the vendor that builds it. The vendor decides how the machine stops, what it does when something fails, and how that is shown to work. That body of design and evidence is the safety case.
It belongs to the vendor because only the vendor sees the whole machine. A stop depends on many parts and on how they are arranged. No single part answers for it, whoever made that part.
Element 31's standing position is that safety, stops, and motion stay on the machine as its vendor built them. BramHA does not change that. The silicon is intended to sit inside the vendor's machine, under the vendor's design and the vendor's responsibility.
Words that should not be misread
Some of the terms used to describe the program can sound like safety claims. They are not.
Real-time means that a control loop is intended to close on a fixed beat. It describes timing.
Root of trust means that a machine is intended to be able to prove what it is and what it is running. It describes identity. No security evaluation is claimed for it.
Mature process nodes are well understood as a class, which is why the program chose them. That is a reason for a design choice, not a rating.
A named engineer signs every gate: the specification, the design freeze, and the tape-out. That describes how the program is run. It is not a certification of what the program produces.
The same holds for the Grid
The question sometimes extends to Element 31's inference pool. The answer there is the same. A Czar Grid serves perception, decisions, and adaptation over the site's network. It is not a controller and does not sit inside any real-time or safety loop.
A machine served by a Grid, or built with Element 31 silicon, or both, is as safe as its vendor made it. Neither adds to the vendor's safety case, and neither takes it over.
What a reader can rely on
A reader can rely on the program's list of what is not done. No chip has been taped out. No certification is claimed. Nothing can be ordered, and there is no partner intake.
What is not done yet keeps that list, and the common questions are answered at /faq.
Questions this raises
- Will BramHA be certified later?
- The program has made no statement about certification. Nothing here should be read as a plan or a promise to obtain one.
- Does the root of trust carry a security certification?
- No. No chip exists, the specification of the first design is not published, and no security evaluation is claimed.
- Does using Czar Grid add a safety certification to a machine?
- No. Czar Grid is not a controller and does not sit inside any real-time or safety loop. Safety, stops, and motion stay on the machine as its vendor built them.
KEEP READING