What in development means
Every statement on this site about BramHA is a statement of intent. No figures or orders exist, and the one date is a target. This is how to read the site, and what would have to be true before that changes.
· 4 min read
IN SHORT
In development means that every statement about BramHA is a statement of intent. No chip has been taped out, no chip exists, and nothing is for sale. There are no figures and no orders, and the one date, first silicon in November 2027, is a target and not a promise. Each of those would change only after a specific thing has happened, such as a published specification, a signed tape-out, or a measured part, and not before.
The phrase "in development" appears across this site. It is easy to read past, and easy to read as a polite way of saying "nearly ready". It means exactly this: BramHA is a program, not a part. No chip has been taped out, no chip exists, and nothing is for sale.
This article is a guide to reading the site with that in mind.
Every statement is intent
When a page says the silicon "is being designed to" close a control loop on the chip, or "is intended to" let a machine prove what it is, the wording is deliberate. It describes what the program is aiming at.
No sentence on the site should be read as a description of an existing part. If one seems to say so, read it as intent. The four jobs, control, motion, sensing, and identity, are the scope the silicon is being designed for. The first design, a real-time controller with a root of trust, is what the program plans to build first. What BramHA is gives the full definition in the same terms.
The same applies to how the work is done. AI Employees doing the engineering, a named engineer signing every gate, and the design work running on Czar Forge are described as the way the program is being set up.
No figures, one target, no orders
No figures. The site has no performance, power, or price figures, and no process-node figures.
A figure for a chip is either a measurement of a part or a commitment in a published specification. Neither exists. A number written before that would be a guess presented as a fact.
What the site does state are trade-offs that hold in general: mature process nodes cost area and power per unit of compute, and a small first design does little.
One target. First silicon is targeted for November 2027. That is a target, not a promise, and it is the only date on the site. The program role among the AI Employees holds the schedule behind it across the other roles, as the work of any chip program requires. The intermediate dates are not published, and nothing else on the site should be read as a hint at one.
No orders. Nothing can be ordered, and there is no partner intake. The silicon is intended, eventually, for robot makers who would build it into their machines. Today there is no part, no terms, and no process for obtaining one. Can I buy a BramHA chip gives the short answer.
What would have to be true before any of that changes
Each kind of claim rests on something that has to happen first. These are conditions, not a schedule, and listing them is not a promise that any will be met.
Before the site could describe the first design in detail, its specification would have to be signed by a named engineer and published.
Before it could name a process, the process and the foundry would have to be decided and announced.
Before it could say a chip exists, a named engineer would have to sign a tape-out, and a foundry would have to fabricate the part.
Before it could publish a figure, a fabricated part would have to be brought up and measured.
Before it could say anything about certification, a certification would have to be sought and granted. None is claimed, and nothing here implies one is planned.
Before anything could be ordered, there would have to be a part, terms, and a way to obtain it. None of those is decided.
Until a condition is met, the corresponding statement stays in the forward-looking form or stays off the site.
Why write it this way
A robot maker reading about a part for a machine needs to know exactly what can be relied on. At present the answer is the reasoning and nothing else: that a robot's own silicon does jobs that need certainty, not density, and that a mature process node is enough for them.
That reasoning can be examined on its merits today. Everything else waits for the work. What is not done yet and the page at /program keep the current state.
Questions this raises
- Does in development mean a launch is close?
- Not by itself. The phrase describes the present state only: the program exists, and the chip does not. Separately, first silicon is targeted for November 2027, which is a target and not a promise.
- Why does the site use phrases such as is being designed to?
- Because nothing has been built. A sentence in the plain present tense would claim a part that does what is described. The forward-looking form is the accurate one.
- Can I rely on the descriptions when planning a machine?
- Not as commitments. They describe intent. There is no published specification to design against, there are no figures, and nothing can be ordered.
KEEP READING