A university cubesat or a small startup has no flight dynamics department. Its constraints live in chat threads, range notices and spreadsheets; its orbit data is the public catalog. CRIC turns those into decisions you can review: can this rocket get the satellite there, when to launch, and what to do when something comes close or you want to move. Each comes with its evidence, the checks it passed, and a person's sign-off. CRIC finds the risks and rules to check; it does not guarantee safety.
Pick a real launcher, drop in its spec sheet, or type a small rocket's numbers. Watch it fly to your orbit. If it falls short, CRIC suggests fixes, and test-flies each one first.
A week of weather for every launch site, then every minute checked against the satellites already up there. One minute can pass another satellite at under a kilometer. A few minutes later, the sky is clear.
Your satellite joins the catalog. CRIC tells you when it flies over home and warns you about close approaches. Command a burn yourself and CRIC checks it against every tracked object first. You make the final call.
| Nemotron | What it does | Safety check |
|---|---|---|
| 3 Nano | Turns “my 5 kg cubesat, 500 km sun-synchronous, I live in Seoul” into an orbit | The orbit math is done in code |
| 3.5 Super VL | Reads spec sheets and the team's screenshots | Every number labeled; gaps filled with marked defaults |
| 3 Super | Explains a failed flight, reads team notes, votes on launches and close approaches | Fixes come from the simulator; rules in code must agree |
| 3 Ultra | Makes the launch call; writes briefs when a person has to decide | Can't pick a vetoed window |