Program 02 · NEXUS
All programsNeural EXploration Unified System
Cislunar Awareness & Intelligence
Cislunar space is about to become somewhere decisions are made under pressure, and almost nothing about it is currently measurable. NEXUS is being built to answer four questions: what is up there, where and when you are, what a decision maker should do about it, and what any of it costs.
In development and in architecture. Nothing in this program is sold today, and no sensor, ground station or timing source of ours exists.
Constanellis builds five programs from the ground outward: FORGE and NEXUS on the ground, HERMES in orbit, WIRES and ATLAS on the lunar surface. NEXUS is the ground stage of that sequence.
The question
Altitude has always mattered, in warfare and in commerce, and the arguments about it are old. What is new is the distance. Geosynchronous orbit is roughly a tenth of the way to the Moon, and the volume beyond it is not covered by the sensors, the catalogues or the timing services that make near Earth orbit legible. Two facts make that harder rather than easier. A spacecraft that maneuvers continuously does not hold a predictable orbit, and a predictable orbit is the assumption every catalogue is built on. And the radio spectrum those measurements travel on cannot be assumed available at the moment it matters most.
NEXUS covers four areas. Domain awareness, which is knowing what is in the volume and what it is doing. Navigation and timing, where the timing standard is the harder and the more valuable half. Decision support, which is turning that into something a person can act on in the time available. And the economic work, which is the measurement corpus, the price ladder and the input output model that say what any of it costs. The catalog carries the stage, the unit of sale and the prerequisite for each line.
Program scope
A catalogue of objects and behaviour beyond geosynchronous orbit, built for a regime where continuous maneuver is normal rather than exceptional. A track that assumes a predictable orbit stops being a track once the object stops holding one, and the measurement problem is harder at cislunar distance than the near Earth version everyone has practised on.
Position and navigation matter, and the timing standard underneath them matters more. Precision comes from synchronisation, which is why a timing source is the thing an adversary or an accident takes away first. The design target is resilience rather than redundancy: the effect holds under degradation, instead of a second copy of the same fragile thing.
The volume of observation is not the constraint. Making sense of it inside the time a decision actually has is. The work is automated correlation with the person kept in the loop at the point of judgement, and with every input carrying its source, its uncertainty and its age, so the judgement can be audited afterwards.
A traceable measurement corpus, a price ladder, and an input output model that traces how a change in one service moves the others. Measured results, estimates and proposed capabilities are kept apart, so a comparison cannot quietly turn an assumption into a fact.
Deliverables
The question, the evidence that bears on it, and the evidence that does not yet exist, each item carrying its source, date, units, and stated limits.
How the service or the architecture you are deciding on depends on transportation, power, timing and manufacturing, and what a change in one moves in the others. Labeled as analysis, never as measured fact.
Published and estimated figures kept apart, with the assumption behind each estimate written down so it can be challenged.
When a source revises or a figure is retracted, the brief revises with it, and the change is recorded.
The catalog · 4 lines, 1 quoting today
Each line with what you receive, how it is bought, and the stage it is actually at. No prices: the number is quoted against your requirement.
| Line | What you receive | Unit of sale | Status | Earliest |
|---|---|---|---|---|
| N-01Interface mismatch analysis for a named architecture | Every interface where the provider and the receiver disagree, quantified, ranked and traced to its source | Per architecture, per revision | Quoting today | Immediate |
| N-02Price ladder and input output matrix | A maintained, machine readable dataset of what lunar goods and services are said to cost and what each system consumes and produces | Per report, then per seat | In development | Year 1 to 2 |
| N-03Subsidy gap analysis | What anchor commitment closes a business case that does not close on its own, computed rather than asserted | Per case | In development | Year 1 to 2 |
| N-04Measurement corpus access | Reference data from qualification campaigns, structured so it can be used to design against rather than read | Per seat, per domain | In development | Year 2 to 3 |
Maturity
Every label reads from the one auditable maturity file. Nothing has flown; nothing below is offered as a service today.
| Part | Status | What it is |
|---|---|---|
| Cislunar domain awareness | Knowing what is in the volume beyond geosynchronous orbit and what it is doing, in a regime where continuous maneuver breaks the predictable orbit every catalogue assumes. Architecture only. We operate no sensor. | |
| Navigation and timing | Position, navigation and the timing standard underneath them, designed to hold under degradation rather than to be duplicated. Architecture only. We operate no timing source. | |
| Decision support | Correlation at machine speed with the person kept at the point of judgement, and every input carrying its source, uncertainty and age. Architecture only. No system is fielded and no assessment has been delivered. | |
| Measurement corpus | Observations organized with source, units, date, and limitations, measured results kept apart from estimates and proposals. | |
| Price index | Cost and price figures for lunar infrastructure services, with the basis of each figure and its date. | |
| Input/output model | The dependency structure between services, so a change in one can be traced through the others. | |
| Coordination layer | Where organizations face related requirements, made legible with the evidence and assumptions attached. | |
| Data products | The form in which the above is delivered to a customer. Scope and terms are agreed per engagement. |
Limits
Engagement
You describe the decision, the volume or service, and the evidence you already hold, at a non-sensitive level. No technical data changes hands.
We reply with what the evidence can and cannot establish, and what a brief would contain. No work is proposed before that.
The brief arrives with its sources, assumptions, and limits attached, and a corrections path if a source moves. Controlled technical data is handled under our ITAR registration and only under an agreement written first.
Evidence
Named, versioned, citable publications.
Fourteen lunar services, what each depends on, and what evidence is held. Preview.
Collect first-party sources into a brief in your browser.
Every NEXUS line with its unit of sale, its prerequisite and the stage it is actually at.
Related programs
Tell us which decision you are trying to make, the volume or service involved, the evidence you already have, and the gaps that matter. That gives us a practical starting point, and the reply says what we can establish and what we cannot.
Start a conversation