Build1 distinct publisher3 min readPublished
Sanctuary AI's June numbers, better than 99.5% success at a 2.54-second cycle, came out of a 40-minute run of 313 insertions that CEO Daniel Friedmann later told Forbes remains a proof of concept rather than a deployment.
The Engineer · Build desk

Compiled by The EngineerSomething wrong?How this is made
Selling a policy layer onto arms a plant already owns changes what has to hold at the seam. Sanctuary AI keeps the perception, touch, manipulation and policy training; locomotion, balance and full humanoid manufacturing come out of scope [14]. The end effectors stay in the package [4], which is the honest call: a flexible wired plug going into a moving target is a hand problem before it is a brain problem.
Two clocks matter. Forty minutes is 2,400 seconds, and 313 trials spread across 2,400 seconds is about 7.7 seconds of wall clock each [1]. The published cycle is 2.54 seconds [6], and 313 of those is 795 seconds, which leaves roughly 1,605 seconds, about 27 minutes of the window, sitting outside the measured cycles [2]. Sanctuary AI's own framing agrees that 2.54 describes the task cycle rather than elapsed time [13]. The remainder is part presentation, resets, recovery and whatever else happened between insertions, and the source material does not break it down.
For the cycle figure to set line pace, the part has to arrive at the tolerance the policy trained on, the moving target has to keep moving the way it moved that morning, and the dead time has to be absorbed by fixturing rather than by an engineer standing at the cell.
The failure arithmetic is thin in the same way. One insertion is worth 0.319 percentage points of a 313-trial rate [3], so the distance between 99.5% and 99.0% is a single plug, and the reported rate corresponds to one or two misses [9]. Extend the cycle instead of the window: 2.54 seconds across an eight-hour shift is about 11,338 insertions [4], and half a percent of that is roughly 57 failures per shift [5]. Whether 57 is tolerable depends on what a bad plug costs downstream, and that figure belongs to the customer, not the vendor. What the trial establishes is repeatability, which is what the source claims for it [10].
One more thing to hold in view. Sanctuary AI has previously described teleoperation as a way to collect demonstrations for training autonomous behaviour [11], and the current product page presents the wire task as live policy performance with no edited attempts [12]. Both statements can be true at once, and the only thing that settles it for a buyer is standing at the cell with a stopwatch.
My read is that this lowers Sanctuary AI's exposure to its own hardware schedule. Olivia Norton, who led Kindred's Vancouver AGI group before co-founding the company in 2018 and now runs engineering and operations [15], has put the position as: factories can start with arms they can buy today [2], while Phoenix waits for humanoid hardware, manufacturing and economics to catch up [3]. The founding premise that human-like intelligence needs a human-like body survives intact [16]; the customer just stops paying for the body. I would fund a pilot on this. I would also write the acceptance test against elapsed throughput over a full shift and treat 2.54 seconds as the best case it currently is.
Ranked by verification strength, evidence, and original report placement.
On June 17, Sanctuary AI co-founder Olivia Norton laid out an expanded strategy: run Sanctuary AI's Physical AI on industrial arms that factories can buy today, instead of tying every installation to Phoenix, the humanoid Sanctuary AI spent years building.
Factories can start with existing industrial robot arms, according to Sanctuary AI's product materials.
Sanctuary AI's position is that Phoenix can wait for humanoid hardware, manufacturing and economics to catch up.
Sanctuary AI is packaging its control software, data infrastructure and end effectors for industrial customers, but its disclosed test is not a production deployment.
Sanctuary AI announced in June that its system had achieved a success rate above 99.5% while inserting flexible wired plugs into moving targets for an unnamed Tier 1 automotive supplier.
Sanctuary AI reported a 2.54-second cycle time measured against the automotive customer's live production benchmark.
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 29, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
invest
Unitree's $905M Shanghai listing prices humanoids at 35x sales while profit halves1 distinct publisher
leadership
The same lies, every fire season: a coalition report makes the case for pre-planned crisis comms1 distinct publisher
invest
A stock that doubles on one readout was telling you what it thought of the odds1 distinct publisher
leadership
AI capex outgrew the consumer. Your demand forecast is now an AI bet.1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
One 40-minute company-run test, relayed at second hand
Every number here originates inside Sanctuary AI and reaches us through a single outlet quoting a Forbes interview: the success rate, the cycle time, the trial count, the live-policy framing on the product page. The task is genuinely difficult and the trial count is real, but 313 attempts in one 40-minute window with an anonymous customer is the thinnest evidence base that can still be called evidence, and no one outside the company has repeated or audited it.
Zero production lines; one proof of concept
Friedmann settles this himself: the automotive example has not entered production. What exists is a demonstration for one anonymous supplier and an intention to deploy within weeks depending on task complexity. There is no named customer, no order, no installed cell running a shift — only a repackaged stack and a benchmark to carry into sales conversations.
June's framing outran what the run showed
The gap is between two statements by the same company. In June the numbers arrived dressed as production readiness — better than 99.5%, measured against a customer's live line benchmark. In August the CEO told Forbes it was a proof of concept, and the run turned out to be 40 minutes long with one or two failures deciding the headline. Runtimewire's second clock does most of the deflating: 7.7 seconds per trial elapsed against a 2.54-second cycle, and about 27 minutes of the window unaccounted for by the measured cycles. Held to a shift, the same success rate is roughly 57 misses.
A capital-intensive humanoid bet needing a nearer-term sale
Sanctuary AI spent years and outside investment on Phoenix, and this announcement lets it sell something before humanoid economics arrive — which is exactly the situation in which a self-measured 40-minute result gets presented against a customer's production benchmark. The anonymity of the Tier 1 supplier, the unpublished pricing and revenue, and Friedmann's refusal to give a typical return on investment all keep the favourable numbers checkable only by the party that produced them. Naming the CEO's hardware-commercialization background is part of the same pitch.
Firm on what was said, thin on what it proves
We can be fairly confident about the record: the dates, the figures, the CEO's qualification and the arithmetic that follows from them are all consistent and directly quoted. Confidence drops on everything that matters commercially, because a single outlet relaying one interview cannot tell us how the system behaves on trial 11,338, what a retrofit costs, or whether the Tier 1 supplier intends to buy.