The handoffs between products
18 places where one product hands you to another — each one a link a signed-in user sees inside the product, shown here in the same words. This is the integration, described by the thing that implements it rather than by us.
When you are in Academy
On any page
Simulators draw missions/platforms/KPIs from Data Domain
AcademyData Domain
On flight software
Break down flight software in SMAT's DBW
AcademySMAT-AI· design breakdown
On getting started
Try it for real in SMAT-AI
AcademySMAT-AI· workflow
When you are in SMAT-AI
On any page
Reference data (missions, platforms, KPIs)
SMAT-AIData Domain
On coverage overview
Back to the spec these KPIs trace to
SMAT-AIWeProject· objectives
On first analysis
Learn the physics behind the analysis
SMAT-AIAcademy
On link budget
Link-budget & antenna fundamentals
SMAT-AIAcademy
On tree ground station
Train on ground-station & link theory
SMAT-AIAcademy
On tree satellite
Train on satellite design
SMAT-AIAcademy
When you are in Supremacy
On any page
Turn this gap into a tracked spec
SupremacyWeProject· requirements
On competitors
Compare against the platform ontology
SupremacyData Domain
On gaps
Turn this gap into a tracked spec
SupremacyWeProject· requirements
When you are in WeProject
On any page
See the reference SSOT this spec is built on
WeProjectData Domain
On getting started
Next: analyze your design in SMAT-AI
WeProjectSMAT-AI· workflow
On objectives
Verify coverage & KPIs in SMAT
WeProjectSMAT-AI· coverage overview
On requirements
Where this requirement came from (intel)
WeProjectSupremacy
On strategy
Prove this meets its KPIs in SMAT
WeProjectSMAT-AI· link budget
On system breakdown
Open the mission/platform ontology
WeProjectData Domain
Engineering knowledge is six kinds of thing
A mission objective, a thermal constraint, a test report and an approval record answer different questions. ISBEGO names the six, so "what have we not covered" becomes a query instead of a debate.
Intent
12The purpose and direction — WHY the system or organization exists and what it is trying to achieve.
Structure
34The make-up and composition — WHAT the system and organization are built from.
Boundaries
20The limits and rules that constrain the system — what it must and must not do.
Evidence
22The artefacts and proof that things are true or done.
Governance
27Decisions, authority and oversight — how the work is steered and controlled.
Operations
36The activities and execution — how the work actually gets done over time.
151 ontology classes are graded against these six, each recording where the grading came from and how sure it is — part of 381 entity types across 7 applications. How the classification works · What re-derives every number here
These are in-product links, so they need a sign-in. What you can open right now without one is the acronym reference — where 898 of 1,098 terms link to a simulator you can run in the browser.
Questions this page didn't answer
Send them and we will answer directly, including the ones with awkward answers.
Get in touch