It checks itself. Every hour. In the open.
Around the clock, MEKLYRA plans parts it has never seen, cuts them in simulation and checks every one against its drawing. What it gets wrong never reaches a floor — it becomes a rule.
Every point is a part it planned and checked. Drag to turn · click the brain, then scroll or pinch to zoom · click a point to fly into it
The live count is resting for a moment — it is back within a minute.
A part it has never seen. Planned, cut, and checked.
MEKLYRA's learning server draws a new part every few seconds and runs it through the same system you use — nothing set aside for the test.
A new part, every time
Five levels of difficulty, never the same part twice — from a plate with holes to a five-axis part with tilted holes, threads, pockets, tolerances and turned steps.
Planned, then cut in simulation
Setups, tools, cutting data and toolpaths — then every cut is run against the stock, the holder and the workholding, the way a careful programmer would before the first chip.
Checked against its own drawing
Every feature and tolerance on the drawing is checked by written rules. A hole too shallow, a dimension missed, material left standing — it is found, and it is named.
Nothing it gets wrong reaches a floor. It becomes a rule.
A fault is not hidden and not averaged away. It is the start of the next rule.
Found
The check names what is wrong, on which feature, and why.
Grouped
The same fault on different parts is one problem — solved once, for all of them.
Reviewed
A CNC programmer looks at it the way you would at the machine.
Written
The fix becomes a written rule with an author — and every part checked before is run again, so a fix never breaks what worked.
Reviewed by working CNC programmers.
Working CNC programmers go over MEKLYRA's plans operation by operation — tools, cutting data, order, setups, workholding — and build parts designed to break it. What they find is judged, and what holds becomes a rule. That is the difference between a system of rules and another AI that guesses.
What these numbers are
They count MEKLYRA's own test parts, drawn by its learning server around the clock. They are not customers' parts and they are not counted as customers — your parts are never part of these counts.
Every decision MEKLYRA makes on a plan comes from a written rule with an author. These numbers show how often those rules are put to the test — and how often the test finds something, because a system that never finds a fault is not looking.