Polydera

AGENT-NATIVE MESH ENGINEERING

Formira.

The mesh engineer on your team.

Formira is an agent-native mesh engineering framework. Its engineer, Mira, arrives an expert in geometry, computation and interfaces, and learns your internal processes. It works alongside your team, in the same window and the same scene, and the work lands in one shared record. Every act numbered in a history you can step through.

Fluent in geometryLearns your processesEvery act recorded

SEE IT WORK

Watch Mira work. From start to finish.

EXAMPLE 01 / MINE STAGE REVIEWUpdate the next excavation stage

A mine's updated survey for the next stage. Keep the backfill, and show where it changes our understanding of the seam.

EXAMPLE 02 / NETWORK MATERIAL ACCOUNTResolve the network, account for the material

Seven channel surveys and three interpreted lenses. Combine the surveys, then show which material is excavated and which remains beneath.

A person asking in the application's chat, Mira answering in the same window — each video is the entire conversation, in real time, nothing cut. The field is the example, not the boundary.

01 / AN INDEPENDENT ENGINEER

It works as an independent engineer.

An agent given buttons can only press them. Mira is given what an engineer is given — the data, a bench to try things on, a language to compute in, and the room to build. It is an engineer and a developer in one: it runs the experiment, and it writes the tools around the answer.

01 / THE ENVIRONMENTIts own environment

Every mesh, every geometry, the whole scene — Mira reads and works the same session you see. Nothing is exported to it; it works where the data lives.

02 / EXPERIMENTSExperiments, contained

It tries things: compute, measure, compare, discard. The runtime contains every attempt — what is not kept leaves no trace.

03 / TRUEFORMA master of trueform

It gets the entire trueform bindings, and full Luna to drive them: arrangements, booleans, sections, repair and measurement over native arrays. An investigation is computation it writes, not a tool it waits for.

04 / IT BUILDSIt authors interactive UI

When an answer needs a control, it builds one — live, interactive, wired to its own functions. A scrubber, a comparison panel, a review page: built in the session, for the question at hand.

05 / IT MEETS YOUIt meets you in the UI

What it hands you, it watches: your drag, your release, your Escape, your answer in the chat — each reaches it, and it responds without being asked.

06 / THE SUMFrom question to review

Hand it the data and the question. It checks, repairs, measures, builds what the answer needs and writes the review — and it asks where the decision is yours.

02 / YOUR EXPERTISE

Give it your expertise.

Mira arrives an expert engineer — geometry, computation, the craft of showing an answer. What makes it yours is what it learns from you: your internal processes, three ways in.

01 / YOUR VERBSExpertise becomes verbs

The expertise you have already built — algorithms, checks, solvers — enters as Luna bindings: typed verbs Mira calls like any other. The implementation stays yours, and it stays opaque: what Mira sees is the signature and the documentation, never the code.

02 / YOUR PROCEDURESProcedures of record

The procedures you already run enter as Luna programs — written down, not invented. They are the procedures of record: Mira runs them as you wrote them, on every revision of the data.

03 / YOUR WAYIt models how you work

The language describes itself, so Mira can read your procedures — what you check first, what you distrust, how you reach a solution — and model its own work on yours. And it can learn the ordinary way too: hand it the field's literature and let it work.

What it learns stays with the team: named functions, workflows and modules, standing in the record you share. How bindings keep your implementation private

03 / YOUR APPLICATION

You get the application the work needs.

The window is not a fixed program with an API bolted on. Scene, tools, panels, gestures — each is a Luna module in the running session, and what is a module can be added, replaced and rewired — by your team, and by Mira.

THE MENUTools are modules

Every tool is a Luna module, and the menu is one published value. Add a row from a cell while the window runs — the application has a new button. Remove it the same way.

THE UI MODULEPanels, forms, pickers

Interface is vocabulary: a form reads a function's signature, a picker hands back what you choose in the scene, a readout carries its units. Mira authors UI through the same rows your team does.

INTERACTIONFull control of interaction

Pointer, wheel, grips, modes — interaction is a Luna module like any other. A drag is a program with a release, a mode is enter, keys and exit, and every gesture can be rewired while the window runs.

THE SANDBOXSandboxed in the runtime

The agent never runs loose in your process. Everything it does happens inside Luna's runtime: checked before it runs, contained while it experiments, recorded when it keeps.

A different field on the same shell is a different application — the frame stays, the vocabulary and the procedures change. No plugin system makes that possible; the application is written in the language Mira works in.

04 / TWO POSTURES

Its own window — or inside yours.

THE WINDOWIts own application

Scene, viewport, chat, reveals and reports — the full window, with Mira seated in it.

EMBEDDEDInside yours, no UI

The same mesh vocabulary and the same engineer inside your application. What Mira builds there, your application calls.

05 / IN THE WINDOW

One window — your hands and its programs.

You rotate the model; Mira frames the defect. You drag the section; it reads where you stopped. One window holds both of you — your hands on the controls, its programs behind them, the same scene in the same session.

The interface is how the reasoning becomes visible: a reveal answers "where", a section answers "how close", a report carries the account — and what Mira hands you listens for your hands.

  • ChatThe conversation stands in the application's activity pane, beside the viewport and the scene. Type, or dictate on device.
  • RevealsEvery "show it in the model" is a reveal: the targets framed, everything else hidden or dimmed, the arrows stepping through them. Escape puts the scene, the selection and the camera back exactly as they were.
  • Closed loopWhen Mira hands you something — a reveal to look at, a section to drag — it hooks itself in first. Your Escape or your release reaches it, and it answers without being asked.
  • ReportsA review is a page: the finding, readouts, bar charts with units, sections drawn to equal aspect, a photograph of the model — and the geometry behind every number, one action from the page.
  • The recordMira acts by running Luna in the session, and each cell stands in the record beside the person's own. What is kept is a numbered act that can be rolled back.

06 / THE WORK STAYS

Keep the method — it reruns.

Much of what Mira does is simply done: cells run in the record, and the answer is handed over. When a procedure matters, you keep it — it stands as named functions, and when the next revision of the data arrives it reruns, its result a new revision beside the last. A kept review holds its quantities, its sections, its page — kept, not recomputed.

07 / BUILT ON LUNA AND TRUEFORM

One language, from the window to the engineer.

Formira is written in Luna — the window, the tools, the record — and its geometry engine is trueform. One language from the window to the engineer is why Mira can reach everything the window can: there is no second system beneath it.

The runtime keeps the shared record — every change an agent makes is a numbered act that can be rolled back.

Luna, the language and runtime
FORMIRAThe application

Scene, tools, chat, reveals and reports — every one a Luna module on one shell.

LUNAThe language and runtime

What Mira writes and where it lives: checked before it runs, recorded when it is kept.

TRUEFORMThe geometry engine

Arrangements, booleans, sections, repair and measurement.

FORMIRA

Hand it your data. Give it your expertise.

The mesh engineer on your team — an expert from the first minute, yours as it learns how you work.