Where safety lives
Safety stays on the machine as its vendor built it. BramHA is being designed as a part a robot maker may build in. It is not a safety system, and no certification is claimed.
· 4 min read
IN SHORT
Safety lives on the machine, as its vendor built it. BramHA is being designed as a part a robot maker may build into a machine. It is not a safety system, it claims no safety or functional-safety certification, and the safety case remains the vendor's design and the vendor's responsibility. Czar Grid does not sit inside any safety loop either.
A program that designs a chip for a robot's control loop will be asked about safety, and it should be. The answer is short. Safety lives on the machine, as its vendor built it, and BramHA does not change that.
The program is in development and no chip exists. This article sets out what the silicon is in relation to safety, what it is not, and who holds the safety case.
On the machine, as its vendor built it
A robot is made safe by its maker. The vendor decides how the machine stops, what it does when something fails, how it limits its own force and speed, and how all of 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 the brakes, the drives, the power supply, the sensors, the software, and how they are arranged. No single part can answer for it.
Element 31's standing position reflects this. Safety, stops, and motion stay on the machine as its vendor built them.
A part, not a safety system
BramHA is being designed as a part a robot maker may build into a machine. Its jobs are control, motion, sensing, and identity. The first design is a real-time controller with a root of trust.
A controller is close to the things that matter for safety. The chip may run a vendor's control loop. That does not make it a safety system.
The distinction is practical. A safety system is designed, analyzed, and demonstrated as one, within a particular machine, by the party responsible for that machine. A part is something the vendor selects and builds in. What role the part plays in the machine's safety, if any, is for the vendor to decide and to show.
So the program describes the silicon as a part. Silicon for the vendors who build the machine explains who that part is for.
No certification is claimed
No safety or functional-safety certification is claimed for BramHA. None should be implied by anything written about it.
The plainest reason is that there is nothing to certify. No chip has been taped out, and the specification of the first design is not published.
Some of the words used to describe the program could be misread, so it is worth being exact about them.
Real-time means that a loop is intended to close on a fixed beat. It is a statement about timing, not about safety.
Root of trust means that a machine is intended to be able to prove what it is and what it is running. It is a statement about identity. No security evaluation is claimed for it.
Mature process nodes are well understood as a class. That is a reason for choosing them. It is not a safety rating.
Is BramHA safety certified? gives the short answer to the direct question.
What the Grid leaves alone
The same boundary already governs Element 31's inference pool. 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.
BramHA does not alter that. A machine with Element 31 silicon inside it would be served by a Grid in the same way as any other machine. The Grid would still never sit in the loop.
The two stand in different places with the same rule. The Grid is outside the machine and stays out of its loops. The silicon is intended to be inside the machine, as a part, under the vendor's design.
What a robot maker should take from this
Three points follow for a vendor or an integrator.
The safety case stays yours. Nothing in the program is intended to take it over, share it, or stand in for it.
The silicon should be judged as a part. When there is a specification to read, a robot maker would assess it as any other part is assessed, against the needs of the machine it would go into. There is no specification to read today.
And the limits are stated up front. No chip exists. There are no performance, power, or price figures. The process and the foundry have not been announced. Nothing can be ordered. The page at /program keeps the list of what is not done.
Questions this raises
- Is BramHA a safety-rated part?
- No. No chip exists, and no safety or functional-safety certification is claimed. Nothing in the program's description should be read as implying one.
- If the chip runs the control loop, is it not part of safety?
- A part can sit inside a machine without being the machine's safety system. How a machine is made safe, and what role any part plays in that, is decided and demonstrated by the robot maker.
- Does Czar Grid take part in safety?
- No. Czar Grid is not a controller and does not sit inside any real-time or safety loop. BramHA does not change that.
KEEP READING