Aximyr · by Tesryn
Aximyr helps engineers turn requirements into reviewable designs, robot programs and the verification evidence behind them. Its parts are chosen against the makers’ own data and assembled from their own 3D models, with every figure cited to the page it came from. What it can’t prove, it says.
01 — How it works
Say what you are building, in your own words, or attach the RFQ, the drawing or the customer’s STEP file. Aximyr reads it into fields you can see and correct, and asks only the questions that decide the design.
Sketch a part to exact dimensions and extrude it, or make it from parameters. The parts nobody sells (adapter plates, fingers, fixtures, pedestals) are designed to fit what they join.
Bought parts arrive as their makers’ own models. They join by their real interfaces: an ISO 9409 flange to a flange, a bolt pattern to its holes.
Payload, grip, air supply, interfaces, interference, gravity, and how each part is held. Every check answers PASS, FAIL, UNKNOWN or NOT CHECKED, with the quote it rests on.
A bill of materials, drawings, assembly instructions, a layout and a report that cites its sources, bound to one revision. Change a requirement and Aximyr marks what has gone stale.
The first application is robotic palletizing. From a request, Aximyr proposes the cell, checks payload, reach, grip and fit against the makers’ data, lays it out, and writes the robot program for an engineer to review. It is preliminary engineering, and partial today: one cell type, demonstrated on real manufacturer data, with what it checked and what stays unknown written into the package. Robot programs are handed over for review, never sent to a controller; passing the checks does not certify a design or replace an engineer’s review.
02 — Four answers, never a guess
It holds, on the maker’s own data or a calculation from it.
It doesn’t, and here are the figure and the limit.
Nothing proves it either way yet, and here is what would.
No check covers it, or it wasn’t run.
A model’s guess never becomes a PASS. Neither does a default. A value nobody stated is not zero: the check tries it at its best case to find a FAIL, and if none appears it stays UNKNOWN and names what is missing.
03 — What holds it together
Aximyr holds a fact only with its evidence: a verbatim quote at a page of a document whose bytes are pinned by hash. Click Why? on any check and the page opens with the quote outlined. Where makers disagree, you see both.
A robot, a gripper and a coupling are not yet a design. Between them sit the parts no catalogue lists: the plate that carries a gripper on a flange, the fingers cut for one workpiece. Aximyr works out which ones a job needs, designs them, and checks every hole against the model of the part it bolts to.
It runs on a local model and works the same tools you do: reads a messy request, asks what decides the design, places parts, runs the checks and explains them with citations. Its suggestions appear as ghosts in the 3D view for you to accept. A number it states counts for nothing until you confirm it. Turn it off and every workflow still runs.
Every change is an event in one hash-chained log, whether a person, the AI engineer or the service made it. Replay the log and you get the same design, digest for digest. Save versions, compare them and roll back. Comment on a part, a point on the model or a check.
04 — What it’s made of
Switch a module on for the projects that need it. Every one is drawn from the same datum, and every one rests on the same checks, evidence, library, delivery and record.
Describe the job in plain words. Aximyr reads it into a requirement, picks the robot, gripper and coupling against their makers’ data, designs the adapter plate between them, guards the cell and checks the payload against the robot maker’s own load diagram.
Sketch a profile with holes and pockets to exact dimensions, or read one from a DXF, and extrude it. A maker’s STEP comes in as a part of the project, and every hole is checked on the model it bolts to.
Make what you designed: STL, 3MF and OBJ for printing, slicing to G-code, laser G-code with kerf compensation, nesting on a sheet, and 2.5D milling.
Structural, thermal, fluid and magnetostatic studies on a part. Each solver is held to a closed-form answer before its results are trusted.
The research process for magnetic tweezers: requirements, the magnet’s architecture, sizing from cited formulas, verification by FEM, the parts, and the BOM.
Colours, finishes, the light and the floor for the whole system, and ray-traced renders to save as pictures. Presentation only: no check reads it.
It runs on a local model and works the same tools you do: reads a messy request, asks the questions that decide a design, places parts and runs the checks. Its proposals arrive as ghosts in the 3D view for a person to accept. Turn it off and everything still works.
Every check answers PASS, FAIL, UNKNOWN or NOT CHECKED, with the quote it rests on. An unstated input is not zero: a check works it at its best case to find a FAIL, and otherwise stays UNKNOWN and names what is missing.
Every fact is the maker’s own words, quoted at a page of a document pinned by its SHA-256 hash. Why? opens the page with the quote outlined. Where makers disagree, both are shown; neither is picked quietly.
Exact variants with cited specifications and the makers’ own CAD. A part without a model is shown as missing, with how to get it. Catalogues come in from CSV, JSON, Excel and BMEcat.
A bill of materials that invents no price, drawings a lead releases, assembly instructions with no invented torque, a layout, and a report that cites its sources, all bound to one revision with a SHA-256 manifest.
Every change, by a person, the AI engineer or the service, is an event in one hash-chained log. Replay it and you reach the same design. Save versions, compare them and roll back.
05 — Proof, not adjectives
unsupported PASS across 31 frozen requests run with no model: 21 feasible, 7 invalid, 3 incomplete, all answered as expected
catalogue quotes re-read by the tests, each found on the cited page of the maker’s own document
to place 3 parts with every network call refused; 26 checks in 39 ms, the BOM in 38 ms, five runs ending on the same design digest
06 — Where the line is
07 — Bring a real job
Send the RFQ, the drawing or the customer’s STEP file, or just describe the job. You get a walkthrough on your own request, with the checks, the citations and the unknowns in plain view.
