Ask the engineering console for a whole task, not one part: “we need a 6U for Earth imaging in SSO for 3 years, 5 m resolution”, “design a 3U CubeSat for IoT step by step”, “I want to launch a 12U for AIS in Q2 2027”. The console splits it into steps and computes each one from the platform data — no AI model is involved.
- Requirements. What the question states and what had to be assumed (size, orbit, altitude, launch window) — assumptions are marked and change when you add them to the question.
- Orbit. Period, eclipse, pass time and natural decay against the 5-year rule.
- Route 1 — a ready platform. Satellite buses that meet the payload mass, power, pointing and orbit requirements.
- Route 2 — assemble from components. A full CubeSat bus picked by the designer, with ADCS for imaging and an antenna in the same band as the radio.
- Payload, power, mass and communications. Candidate cameras or modems, the power budget with generation and battery sizing, compatibility of the picked units, the mass against the CubeSat limit, and the downlink margin.
- Launch. Deployers for the size, launch windows to the orbit in the chosen period and a planning price range.
- Result. What fits, what to check first and which figures to ask the vendors for.
Every step can be collapsed, refined with one click, and the requirements saved as “My mission” to check any other product against them. The same answer is available to machines through POST /wp-json/kls/v1/mrd-console and the MCP tool ask_console.