Defense & Sovereign Technology · Controlled Access · DEF-032

Underwater Mass Anomaly Detection

Commercial reference
DEF-032

Controlled mass-anomaly evidence technology for underwater infrastructure, environmental, survey and qualified sovereign programs.

Who this is for

Subsea infrastructure operators, survey organizations, maritime safety programs, qualified integrators and sovereign programs.

The problem you already have

A peak reading is not a detection unless the array agrees spatially

The documented classification uses background-subtracted gravity anomaly and signal-to-noise evidence across the sensor array. ANOMALY_DETECTED requires both a sufficiently strong signal and spatial consistency across multiple cells; marginal and background-only cases remain separate states rather than being collapsed into one score.

The same signature can mean stationary, moving or transient depending on what happens across survey passes

Parallel-track repeat surveys are compared through a temporal consistency gate. A signature that remains in place is distinguished from one that shifts systematically or appears in too few passes, producing STATIONARY_ANOMALY, MOVING_ANOMALY or TRANSIENT_ANOMALY evidence instead of treating every repeated anomaly as the same physical case.

This works from redacted gravity measurements, not absolute site coordinates or sensor design

Never requested, and structurally rejected if submitted: exact site coordinates or proprietary sensor-design data.

Real-World Operational Scenario: The Marginal Reading Nobody Double-Checked

Scenario: One sensor cell spikes above threshold; the rest show background only.

A single cell in the survey array reports a reading above the detection threshold. Other cells across the array show background-only levels.

WITHOUT this check: The single strong reading is reported as ANOMALY_DETECTED based on peak signal-to-noise alone.

WITH this check: Detected status requires spatial consistency across multiple cells. With no corroborating cells, the evidence remains marginal rather than being promoted into a confirmed array-level detection.

Scenario: The anomaly appears again on the next survey track — but not in the same place.

Parallel survey passes each show a gravity anomaly, yet the signature shifts systematically relative to the survey platform instead of remaining fixed at one relative location.

WITHOUT this check: The repeated detections can be merged into one stationary subsurface finding simply because an anomaly was present on more than one pass.

WITH this check: The multi-pass temporal gate compares signature location across passes and classifies systematic displacement as MOVING_ANOMALY; a fixed signature becomes STATIONARY_ANOMALY, while insufficient recurrence remains TRANSIENT_ANOMALY. Any velocity output remains explicitly a proxy, not a tracking solution.

What BivectorAI Provides

Array-Level SNR With Spatial-Consistency Gating

Each cell contributes background-subtracted gravity anomaly and signal-to-noise evidence, while SNR_max and array consistency determine whether the result is ANOMALY_DETECTED, ANOMALY_MARGINAL or BACKGROUND_ONLY.

Temporal State Across Independent Survey Passes

Parallel-track survey evidence is correlated across passes to distinguish STATIONARY_ANOMALY, MOVING_ANOMALY and TRANSIENT_ANOMALY rather than treating recurrence as confirmation by itself.

Environmental Noise Is Separated From Mass-Anomaly Evidence

The documented environmental-noise model separates ocean-current noise, platform vibration and tidal variation from the mass-anomaly signature before the evidence is handed to reviewers.

Proxy Labels and Relative Location Stay Attached to the Certificate

Mass and gradient outputs remain explicitly labeled as proxies, depth carries DEPTH_PROXY_UNCERTAINTY_FACTOR_3, location is relative to the array centroid, and every certificate remains human-review evidence rather than a targeting output.

Prove the Gate Before Broader Integration (Zero-Risk Evaluation)

Do not buy the claim. Test the gate.

Feed synthetic sensor-array data with one strong single-cell spike and no corroborating cells. It succeeds only if it holds at MARGINAL rather than confirming.

This initial trial measures false-confirmation prevention, uncertainty-factor accuracy, and spatial-consistency detection. Commercial scale-up occurs only after measured results prove value in your own lab environment.

What you provide

Redacted local gravitational-acceleration readings from the sensor cells, cell positions relative to the survey platform, measurement timestamps or survey-pass identifiers, and the sensor noise-floor metadata needed to compute signal-to-noise evidence. Where available for the agreed evaluation, already-logged ocean-current, platform-vibration or tidal-variation context can be supplied for environmental-noise separation. Exact geographic coordinates and proprietary sensor-design data are not required.

What BivectorAI actually hands you

Detection certificate

  • detection verdict
  • sensor count and mean gravity anomaly
  • SNR_max evidence
  • relative anomaly location and SHA256 evidence hash

Temporal-consistency evidence

  • STATIONARY_ANOMALY
  • MOVING_ANOMALY
  • TRANSIENT_ANOMALY
  • cross-pass spatial-correlation evidence

Proxy and uncertainty evidence

  • MASS_PROXY_NOT_CONFIRMED_IDENTIFICATION
  • mass-class proxy
  • GRADIENT_PROXY_NOT_FULL_TENSOR_GRADIOMETRY
  • DEPTH_PROXY_UNCERTAINTY_FACTOR_3

Review boundary

Mandatory detection-not-targeting, no-weapon-guidance, human-review and non-offensive-use fields remain attached to the sealed evidence. Survey-session certificates can also be chained through a session SHA256 record.

What we will never ask you for

Never requested, and structurally rejected if submitted: exact site coordinates, sensor-design schematics, or classified program details, or your system's core design data. Every submission is checked against this rejection list before any evidence logic runs — a malformed or over-broad submission is blocked and reported back to you, not silently processed.

How it actually runs

01
You export the redacted sensor readings already collected by your survey or monitoring platform.
02
The evidence engine runs inside your boundary. Local CLI, on-prem container, or air-gapped VM — nothing leaves your network.
03
You receive a hash-sealed evidence certificate. Classification, confidence, and contradiction records included, ready for program review.
04
You decide. The engine does not take control action or issue commands — it hands your reviewers structured evidence for the decision that remains yours.

Engagement path & current acquisition terms

DEF-032 · Tier C — Strategic Sensing / Infrastructure

Negotiated diligence option
On request

Secures a defined diligence and exclusive-negotiation period. Any option credit is agreed in writing as part of the signed commercial terms.

Private integration / NRE
On request

Starting integration engineering, customer-safe adaptation, local/private deployment work, validation and acceptance evidence for the agreed environment.

Exclusive field-of-use license
On request

Scope-dependent consideration for negotiated exclusivity in a defined field, program, platform class, territory and rights scope.

Annual technology & sustainment
On request

Engineering support, update access, security maintenance, evidence infrastructure and agreed sustainment services.

Program revenue participation
Negotiated

Applied to attributable net program revenue under the definitive agreement, subject to negotiated exclusions and accounting rules.

Commercial boundary. These are indicative starting terms, not a binding offer. Final price depends on exclusivity scope, field of use, territory, sublicensing, technical-data rights, integration obligations, export-control review, support requirements and definitive agreement.

IP boundary. Exclusive FOU does not automatically transfer ownership of BivectorAI Background IP. Worldwide/all-defense rights, sublicensing, source-level technical-data rights or assignment require separate negotiated consideration.

Controlled acquisition

Scope the DEF-032 diligence and integration boundary

Request DEF-032 Acquisition Discussion →

Email fallback: contact@bivectorai.com

Defense technology is integrated through qualified local/private engagement. No public Defense API and no automated Defense checkout are provided.