+8 Commodity PressureHighly specialized numerical methods and domain-specific data make this hard to compress into a generic AI feature or widget.
Heavy technical/math jargon: Jacobian, KKT, Hessian, ESS, posteriorSpecialized numerical validations: "G1F_PASS: 68/68 synthetic light-time checks passed across 17 synthetic journeys."Domain-specific data assets (ocean-forcing NetCDF archive ~8.44 GB)
+18 Model DependencyRelies on an unrun S50 posterior architecture and a blocked external aircraft-performance source—clear single-point dependencies for predictive capability.
"S50 event-sequential posterior — NOT RUN""SRC AIRCRAFT PERFORMANCE MODEL .......... BLOCKED"Dependency on aircraft-performance source for predictive runs
-12 Workflow OwnershipSource-controlled checkpointing, branch/continuation case management and archived forcing assets indicate this is central to a repeated scientific workflow.
Public scientific checkpointing with dated checkpoints and carried-forward statesBranch and continuation case management (16 branches / 80 cases)Predictive execution locking / run authorization gates
-0 Distribution EmbeddednessSome embeddedness via a public repo and a web dashboard, but no obvious partner channels, marketplaces, or platform integrations for wide distribution.
Public repository referenced (underlying GATE_RESULT.json not included)Web-based dashboard / UI strings (File Model Observations Solver...)Archived checkpoint/log infrastructure (CURRENT PUBLIC CHECKPOINT LOG)
-8 Integration DepthDeep data and systems integrations: Copernicus forcing, NetCDF ocean-forcing archive, SATCOM observation inputs and aircraft performance provenance.
Copernicus forcing files referencedNetCDF ocean-forcing archive (~8.44 GB)SATCOM observation records (BTO/BFO) inputs
-0 Enterprise TrustNo visible enterprise/compliance signals, procurement hooks, or corporate customer evidence—this is a public research project, not an enterprise product.
Enterprise markers: none presentSite framed as "an independent, source-controlled MH370 inference project" rather than a commercial offering
-6 Switching CostSignificant data gravity for researchers (large NetCDF archives, checkpoint history, carried-forward state) but limited commercial collaboration lock-in.
Archived forcing assets and run logsCURRENT PUBLIC CHECKPOINT LOG and carried-forward statesNetCDF ocean-forcing archive (~8.44 GB)
-0 Monetization MaturityNo pricing, commercial packaging, or customer/procurement evidence—this is not positioned as a monetized SaaS.
Pricing visibility: hiddenPrimary buyer: researchers / investigators / technical analysts (research posture)No customer logos, enterprise case studies, or pricing tiers shown
+6 Category BaselineGeneric SaaS gets no category adjustment.
generic saas
-6 Relative PlacementModerately less vulnerable — domain data, checkpointed workflows and system integrations give tangible defensibility vs. the mostly‑shallow peer set, though absent monetization and a blocked posterior limit the move.
Strong defenses: source‑controlled checkpointing, dated carried‑forward states and branch/continuation case management (16 branches / 80 cases).Meaningful data gravity and integrations: Copernicus forcing files, ~8.44 GB NetCDF ocean‑forcing archive, SATCOM BTO/BFO inputs and aircraft‑performance provenance.Specialized technical validation: repeated synthetic light‑time checks (G1F_PASS 68/68) and heavy numerical checks (Jacobian/Hessian/KKT) — not a thin marketing wrapper.