YANA· Ops
Coming soon
The automation layer for aerospace operations
4,471 typed, deterministic aerospace operations — orbit transfers, propulsion, conjunction screening, standards audits — that an n8n workflow, an AI agent or a CI job calls as a function. Your process. Your data. No far side.
4,448 of them touch no network at all, so mission data never leaves your process. In this industry that is not a feature — it is the price of admission.
3 planes · 51.6° · 481-point earth · terminator 2026-03-20T16:33:00Z · drawn to scale
Every serious tool for spaceflight compute assumes a person at the console. Desktop suites licensed per seat and driven by hand. Expert libraries that want a specialist, a build system and an apprenticeship. Spreadsheets nobody can audit once their author leaves the programme.
The rest of your stack stopped assuming that years ago. Workflows retrain models overnight, agents draft the paperwork, CI blocks the merge — and the moment any of them needs orbital mechanics, there is nothing shaped like a function to call. The physics layer is the one layer automation still cannot reach.
That is the whole thesis. 4,471 operations that make spaceflight compute callable — by a workflow, by an agent, by a build — with the discipline this industry demands of flight software: typed interfaces, deterministic outputs, and 4,448 operations that never touch a network at all.
Four numbers, and they descend. Each says what tightened; the last one is the only figure checked against somebody else's implementation.
Drawn to scale, on the front page rather than in a footnote. No vendor volunteers the figure that shrinks its own headline; filter us down to what we will stand behind and judge what survives.
Every other number on this page is a count, and a catalogue of names that never executes would produce the same counts. This is a real call, recorded when the page was built.
The round trip returns az_rad exactly and el_rad to 5.551115123125783e-17 — below the IEEE-754 double epsilon 2.220446049250313e-16, a drift the library's own classifier bins as machine. Step 02's inputs are step 01's outputs, named rather than repeated.
Every light below is one operation, placed one-for-one from the registry when this page was built — 4,471 in a single frame, clustered into the eight largest aerospace domains of its 86 categories. The 23 gold sparks are the complete list of operations that ever touch a network; the other 4,448 run sealed inside your process, wherever it runs. Drift through it — every name that surfaces is real.
One light = one operation · 4,471 drawn · 4,448 offline · 23 networked · placed at build
Three pipelines, named operation by operation from the registry. Every operation below is typed, deterministic, and declares no network — your data stays inside the workflow that calls it.
A fresh ephemeris lands and n8n calls the registry like any other node: RTN Rectangular Conjunction Screening Volume gates the candidates, Conjunction Miss Distance & Relative Kinematics (TCA) works the close approach, Conjunction Assessment (Foster-Patera) puts a probability on it. Your ops channel gets a number, not a feeling — and the same inputs raise the same alert every time.
Over the MCP server, an AI agent plans a manoeuvre with Hohmann Transfer Δv and prices it with Tsiolkovsky Propellant Mass. The model does the reasoning and the writing; every number it quotes comes out of a typed function, not out of the model.
A materials change opens a pull request, and the pipeline runs Outgassing RML/CVCM Screening (ECSS-Q-ST-70-02) and ECSS Weighted Compliance Mean before anyone reviews it. Compliance drift fails the build in minutes instead of surfacing at the review board months later.
Nothing here has ever been published — yet. What ships first is being decided right now, and the people deciding read this address. If you run ground segment, flight dynamics, or ECSS and CCSDS conformance work, the operations you name go to the front of the queue.
One address, straight to the people building it. No mailing list, no tracking — nothing on this page sets a cookie or makes a request to anyone.