Data Domain
Reference & ontology SSOT.
329 KPIs · 1,300+ platforms · 90+ reference APIs — the A&D data spine every product consumes.
Who it is for
Anyone who has been burned by three tools holding three versions of the same platform list.
The problem
Every product needs the same reference data — missions, platforms, subsystems, KPIs — and the moment two of them hold their own copy, nobody can say which is right.
datadomain.weproject.aiSign-in required
See it live
Real, admin-approved numbers from across the estate, refreshed as you watch — not a mockup.
Explore the whole estate — every product, screen and capability →
Real, currently-approved numbers from WeProject, SMAT, Data Domain, Academy and Supremacy.
Numbers you can check
- KPIs in the shared reference registry
- 329
- Checked by verify-launcher-claims.mjs counts the mission-contract catalogues the Data Domain seed loads, and the live kpi_registry
- platforms in the aerospace & defence data spine
- 1,300+
- Checked by verify-launcher-claims.mjs queries the live Data Domain database
- reference data APIs
- 90+
- Checked by verify-launcher-claims.mjs counts the route modules Data Domain serves
- capability areas
- 5
- of the estate's areas this product is in (Data Domain)
In the estate
Loading the estate…
What it does
One writer, many readers
A single service owns the store. Every other product reads; none writes. There is no reconciliation step because there is nothing to reconcile.
Implemented in apps/data-domain/src/app.ts
Permission on two axes
An action is allowed when the person may take it and the calling application is granted that domain. The grants are an editable matrix, not a code change.
Implemented in packages/lasstech-core/src/auth/policy.ts
Change requests from read-only consumers
An application without write access can still propose a correction, which an operator reviews. The alternative — editing a local copy — is how the divergence starts.
Implemented in apps/data-domain/src/routes
Reference data travels with the deployment
Data Domain is deployed alongside the products, or standalone on its own. Reference data is read live from it over the internal network, so a disconnected install keeps working without any product carrying a private copy.
Implemented in docker-compose.local.yml
Who it is for
Across the lifecycle
The spine · under every phase