The intelligence
Engines we built, and run on our own work.
Not adjectives. These are the systems that ship the ventures on this site, and they were proven against our own deadlines before they were offered to anyone else.
Legion
LiveOne mind that delegates. Legion turns Claude Code, Codex, Cursor, opencode and Hermes into a single accountable engineering system instead of five tools you switch between by hand.
Visit legion.opusaether.comHow a run works
Legion plans the work, routes each slice once, and executes dependency-aware branches in isolated worktrees so two agents cannot fight over the same file. What comes back is evidence you can inspect before you merge, rather than a summary asking to be trusted.
Model-agnostic on purpose
No single harness is the point. A slice goes to whichever model suits it and the routing decision stays in the record, so a run is inspectable from the moment work was assigned through to the final hint it leaves behind.
It builds our own work first
Legion ships the ventures on this site, this page included. The store factory below runs as a Legion domain plugin, which is why the two engines are less separate than the headings suggest.
- Harnesses
- Claude Code, Codex, Cursor, opencode, Hermes
- Core plugins
- Nine
- Isolation
- One git worktree per branch
- Output
- An evidence contract you read before merging
- Source
- github.com/Opus-Aether-AI/legion-core, public
Store Factory
Coming soonOne monorepo that builds and operates AI-first, 3D-heavy headless Shopify storefronts. Each store is a thin app over shared packages, so a new one inherits the whole machine rather than starting again.
What a store is made of
A brand config carries the contract as typed schemas, a parameterized React Three Fiber library supplies the 3D, and shared Shopify clients handle cart, checkout and provisioning. A store app holds its own brand and very little else.
Adding one is a generated step
New stores come out of a generator rather than a copy of the last one. That is why Casa Forma, The Automotive Archive, Parva and Bhagwan Bazaar can share a pipeline without sharing a look: the machinery is common, the brand is not.
It runs on Legion
The factory ships as a Legion domain plugin covering planning, audit, smoke tests and upgrades. Operating storefronts at this count is mostly a scheduling problem, and that is the part the engine takes.
- Live stores
- Casa Forma, The Automotive Archive
- In build
- Parva, Bhagwan Bazaar
- Commerce
- Shopify Storefront and Admin APIs
- 3D
- Parameterized React Three Fiber scenes
- Standalone access
- Not yet open
Nidavellir
Coming soonThe internal product-to-manufacturing system. Nidavellir reads a mesh, weighs it against the chosen material, nozzle and print goal, and derives a settings recommendation with the reasoning recorded beside it.
Visit manufacturing.opusaether.comIt checks the geometry means what it says
A file can look plausible on screen and still be a poor manufacturing input. A missing face shows only as a line, two surfaces occupy the same place, an assembly export carries reversed normals or a different scale from the drawing beside it. Topology, connected components, bounds and orientation are inspected before material is discussed at all, and if the geometry needs repair or its units cannot be established, that becomes a flag and you hear about it before work continues.
Slicing follows from the part
Slicer choices decide where layers meet, which surfaces take support, where the nozzle slows, and whether the part is being favoured for surface appearance, feature definition or a shorter run. Nidavellir combines its reading of the mesh with the material, the nozzle and the stated goal to propose those settings, and records why it proposed them, so a reviewer sees more than a profile name.
It assists a decision it does not make
The proposal goes to a person who runs the machines, and the accountability stays with them. The most aggressive slicing mode is treated differently from the finish-preserving ones: where a change might affect visible finish, the tooling has to surface it rather than quietly take the time saving.
- Reads
- Mesh topology, connected components, bounds, orientation
- Weighs against
- Material, nozzle, and the goal for the part
- Records
- Why each proposal was made, not just a profile name
- Status
- Internal, still in development
Point one of these at your problem.