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.
What it does
Each capability names the module that implements it. A check on every build fails if one stops existing.
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
Offline reference bundles
Each product carries a generated bundle so it keeps working when the service is unreachable. This is also what makes a disconnected deployment possible.
Implemented in apps/frontend/src/constants/dd-fallback/kpis.generated.json
Questions this page didn't answer
Send them and we will answer directly, including the ones with awkward answers.
Get in touch