Skip to content

IN DEVELOPMENT · NO CHIP HAS BEEN TAPED OUT

A named engineer signs every gate

AI Employees propose. A named engineer signs the specification, the design freeze, and the tape-out. Because a fabricated chip cannot be patched, that signature is where responsibility for the design sits.

· 4 min read

IN SHORT

On BramHA, AI Employees propose and a named engineer signs. The three gates are the specification, the design freeze, and the tape-out, and no AI Employee approves any of them. A fabricated chip cannot be patched afterwards, so each signature commits the program to something costly or impossible to undo. The program is in development and no chip has been taped out.

A software team can correct a mistake after release. A chip program cannot. Once a design has been sent to a foundry and fabricated, its logic is fixed in the part.

That one fact shapes how BramHA is being organized. AI Employees do the engineering work, and a named engineer signs every gate. The program is in development and no chip has been taped out, so this describes how the work is intended to be governed. It is not a record of gates passed.

The boundary

AI Employees propose. A named engineer signs the specification, the design freeze, and the tape-out. No AI Employee approves a gate.

This is the boundary Element 31 keeps for team work elsewhere: "Agents on a Czar prepare and propose; a named person approves." On the chip program it is applied at the three points where the design commits to something.

The three gates

The specification. This is the statement of what the chip must do. Everything downstream is built and tested against it. If the specification is wrong, a design can pass every check and still be the wrong chip. The architecture role drafts it, and a named engineer signs it.

The design freeze. This is the point at which the logic stops changing. Before it, verification can send work back to logic design freely. After it, physical design works against a fixed target, and any change to the logic means rework across the layout. A named engineer signs the freeze.

The tape-out. This is the release of the finished layout for fabrication, and the last point at which anything about the silicon can be changed. A named engineer signs it. The glossary entry on tape-out defines the term.

The gates between a specification and a tape-out places these three in the full sequence of stages.

Why a chip cannot be patched

Firmware can be revised after a chip is made. The silicon cannot. A fault in the logic or the layout is in every part from that fabrication run. Correcting it means changing the design and fabricating again, with the cost and the wait that another run brings.

Mature process nodes make a run less costly than one at the leading edge. They do not make it free or quick. The asymmetry holds either way: before tape-out a change is an edit, and after it a change is a new chip.

For a part meant to sit on a machine, the stakes are plain. BramHA is being designed for jobs a robot keeps for itself, such as closing a control loop on time and proving what the machine is. A robot maker who builds a controller into a machine has to be able to rely on it doing what its specification says.

What a signature means

A signature is not a formality added at the end of automated work. It means a person has read what is being proposed, and the evidence for it, and takes responsibility for the decision.

That puts a requirement on the AI Employees. Their job at a gate is to finish the work and also to present it so that a person can judge it: what was specified, what was tested, what failed and was corrected, and what remains uncertain. A proposal that cannot be reviewed cannot be signed.

It also explains the word "named". An approval attributed to a process or a system has no one behind it. An approval with a name does.

What a signature does not mean

It is not a certification. A named engineer's signature is an engineering approval inside the program. No safety or functional-safety certification is claimed for BramHA. The chip is being designed so that it could run a vendor's control loop, and the safety of any machine it might be built into remains the vendor's design and the vendor's responsibility.

It does not mean the design is made by AI alone, and it does not mean AI plays a minor part. Both halves hold together: AI Employees do the engineering, and a person signs. AI Employees design the chip describes the roles.

And it does not mean a gate has been passed. The first design's specification is not published and no chip has been taped out. The page at /program keeps the list of what is not yet done.

Questions this raises

Can an AI Employee sign a gate if every check passes?
No. Passing checks are evidence, and evidence is what the AI Employees prepare. The decision to approve belongs to a named engineer at every gate, whatever the checks show.
Does the signature mean the chip is safety certified?
No. It is an engineering approval inside the program. No safety or functional-safety certification is claimed for BramHA, and the safety of a machine remains its vendor's design and responsibility.
Why can a chip not be fixed after it is made?
The logic is fixed in the physical layout when the chip is fabricated. Firmware can be revised afterwards, but a fault in the silicon itself can only be corrected by changing the design and fabricating again.

KEEP READING