Aegis Station Infrastructure is a one-person architecture and flight-software shop with a published reference set: surface vehicles, a logistics chain, and the station they are built toward. Every page on this site ends in open items. This page is how those items find owners.
The program is written as requirements, not finished designs, because the people who have spent a career on a given thing will design it better. Five kinds of people move it forward.
Geophysics, cryogenic propulsion, structures and fatigue, thermal, radiation transport, human factors. Push any page deep enough and the right answer is a name, not a claim. If a requirement on this site is set at the wrong level, say so. If an open item is yours, take it.
Aegis Station is architect, integrator, and software developer. Structures, tanks, landing gear, pressure vessels, mechanisms, thermal and communications hardware are bought or partnered. Engines and deep-throttling cryogenic propulsion are development partnerships. Each vehicle page carries a make, buy, or partner position you can respond to.
Ice prospecting, regolith mechanics, short-range hoppers, and autonomous water logistics have customers before any station exists. Study contracts, teaming on solicitations, and subcontracts to universities and labs are how the surface program gets built. Bring the requirement you actually have.
The shop is bootstrapped and software-first. What capital buys next is not a rendering. It is testbed campaigns for the prospecting method, hardware-in-the-loop against the flight software, and subsystem demonstrators with partners. Serious inquiries get the model chain, not a pitch.
Lunar water at industrial scale is an infrastructure question before it is an engineering one: who builds, who owns, who gets access. The strategy notes on this site are the current position. Disagreement in writing is welcome and gets answered in writing.
A reference architecture that closes on paper and says where it does not. Mission and sizing trades, trajectories and abort profiles, and flight-software constants sit in one linked model chain, so a number on a page can be traced to the cell that produced it.
Software that runs. Flight software on NASA's core Flight System for the tanker, rover, hopper, and prospecting rover, and a ground coordination stack that dispatches them as a mixed fleet. The demonstrations are documented on their capability pages. The repositories are private and are opened under agreement.
A counterpart who answers. Questions go to the person who set the requirement, and the reply is technical, not a form response.
Honest closure is a rule on every page here, so it applies to the shop itself. These are the limits a collaborator should know before the first call.
The flight software has flown complete missions against physics models with known ground truth. It has not flown on a vehicle. Hardware-in-the-loop and testbed campaigns are the next layer, and they need partners with benches.
There is no machine shop, clean room, or test range behind this site. Every physical article in the reference set is a partnership, and the make, buy, or partner positions on the vehicle pages are proposals, not orders.
A single design authority is fast and unchecked in equal measure. The things one person cannot verify are the things a second reader catches first. That is why the pages end in open-items lists instead of conclusions.
Each capability is specified to the level that sets the requirement and sizes the vehicle. Detailed design, qualification, and certification are downstream and belong to the people and organizations that do them for a living.
Pick the vehicle, capability, or strategy note closest to your field. Read to the open items. The program architecture page maps every domain to the page that carries it.
Write with the page and the item in the first line. "SIDA-F-001, depth of investigation, here is what a small aperture actually resolves" gets a faster and better answer than a general introduction.
The first exchange is about the engineering. Agreements, non-disclosure where the software or a partner's detail requires it, and commercial terms follow once both sides know there is something to build.
Aaron C. Smith, design authority. Aegis Station Infrastructure LLC. Public updates are posted on the capability pages as they change. There is no mailing list and no form.
Why the program is shaped this way, in a page: We're Going to Talk One Day.