The gates between a specification and a tape-out
A chip program moves through stages: specification, logic design, verification, physical design, sign-off, tape-out, and bring-up. This is what each one is, and where a person signs.
· 5 min read
IN SHORT
A chip program runs through specification, logic design, verification, physical design, sign-off, tape-out, and bring-up. On BramHA, AI Employees are intended to do the work in each stage, and a named engineer signs three gates: the specification, the design freeze, and the tape-out. The program is in development and no chip has been taped out.
A chip is designed in stages, and the stages run in a fixed order because each depends on the one before. Some of the boundaries between them are ordinary handovers. A few are gates: points where the design commits to something that is expensive to undo.
This article walks through the stages in plain language and marks where, on BramHA, a named engineer signs. The program is in development and no chip has been taped out. Read this as a description of how a chip program works and how this one is intended to be run.
From a specification to frozen logic
Specification
The specification says what the chip must do: its functions, its interfaces, and the guarantees it has to keep. Every later stage is measured against this document.
For BramHA's first design, the subject is a small real-time controller with a root of trust. The specification itself is not published. On the program, the architecture role drafts it.
Gate: a named engineer signs the specification.
Logic design
Logic design turns the specification into a precise description of the circuit's behavior, written in a hardware description language. It is text, kept in a repository and revised like source code. The logic design role writes it.
Verification
Verification asks whether the logic does what the specification says. It runs the design in simulation against tests, looks for cases the designer did not think of, and reports where behavior and specification disagree.
This stage is a loop, not a step. Verification finds a fault, logic design corrects it, and verification runs again. On most chip programs it takes more effort than writing the logic in the first place.
The loop ends at the design freeze, when the logic stops changing so that the work downstream has a fixed target.
Gate: a named engineer signs the design freeze.
From frozen logic to a checked layout
Physical design
Physical design turns the frozen logic into a layout. The logic is translated into basic cells, the cells are placed on the surface of the chip, and wires are routed between them. The result has to meet timing, so that every signal arrives when it must, and it has to obey the manufacturing rules in the foundry's process design kit.
For BramHA, the process and the foundry have not been announced.
Sign-off
Sign-off is the name for the final checks on a finished layout. Does it meet timing under the conditions it has to work in? Does it obey every manufacturing rule? Does the layout still implement the logic that was verified?
Despite the name, sign-off in this sense is a set of checks, not a signature. The checks produce evidence. On this program the AI Employees are intended to run them and assemble the results, and the decision that follows belongs to a person.
Tape-out and bring-up
Tape-out
Tape-out is the release of the final layout to a foundry for fabrication. After it, the silicon cannot be changed. A fault found later is corrected only by revising the design and fabricating again. The glossary entry on tape-out covers the term.
Gate: a named engineer signs the tape-out.
Bring-up
Bring-up is what happens when fabricated chips come back. A part is powered for the first time, its basic functions are checked, and firmware runs on real silicon instead of in simulation. This is where the firmware role's work meets the hardware.
Bring-up is the first point at which anything about a chip can be measured. That is why BramHA has no performance or power figures: there is no part to measure.
Where the signatures fall, and why there
The three gates sit at the three commitments. The specification commits the program to what it is building. The design freeze commits it to a version of the logic. The tape-out commits it to silicon.
Between gates, AI Employees write, test, lay out, and re-plan, with the program role holding the schedule across the others. At each gate they propose, and a named engineer signs. No AI Employee approves a gate.
A named engineer signs every gate explains the reasoning behind that boundary, and the page at /program sets out what is not yet done.
Questions this raises
- Which stages need a person's signature?
- Three gates: the specification, the design freeze, and the tape-out. A named engineer signs each. AI Employees are intended to do the work in every stage and prepare what the engineer reviews, and no AI Employee approves a gate.
- What is the difference between sign-off and tape-out?
- Sign-off is the body of final checks on a finished layout: timing, manufacturing rules, and agreement with the verified logic. Tape-out is the release of that layout for fabrication. The checks are evidence, the tape-out is the decision, and a named engineer signs it.
- Where is BramHA in this sequence?
- The program does not publish a position or a schedule. What can be said is that no chip has been taped out, no chip exists, and the first design's specification is not published.
KEEP READING