Defense & Sovereign Technology · Controlled Access · DEF-034

Nuclear Test & CTBT Monitoring Assurance

Commercial reference
DEF-034

Evidence-assurance technology for treaty-monitoring, seismic/radiological signal review and qualified non-proliferation programs.

Who this is for

Treaty-monitoring organizations, laboratories, compliance programs, scientific agencies and qualified sovereign integrators.

The problem you already have

Seismic size alone can't tell you whether it was an explosion or an earthquake — the ratio can

An event's body-wave-to-surface-wave ratio, not just its magnitude, is what actually separates an explosion signature from an earthquake of equivalent size — and that discriminant is computed and reported explicitly rather than left for someone to infer.

A yield estimate ships with its own uncertainty factor, not a false sense of precision

Any yield estimate carries an explicit uncertainty factor built into the output, and the classification only reaches high confidence when independent signals — seismic and gravity onset pattern — agree; conflicting signals are reported as ambiguous, not averaged into a false consensus.

This runs on measurement logs, not classified source locations

Never requested, and structurally rejected if submitted: classified monitoring-network locations or raw sensor control access.

Real-World Operational Scenario: The Earthquake That Looked Like an Explosion

Scenario: A seismic event registers magnitude consistent with either interpretation.

A seismic event's magnitude alone is consistent with either a small explosion or a shallow natural earthquake.

WITHOUT this check: Magnitude alone triggers an alert: "possible nuclear test detected."

WITH this check: The body-wave-to-surface-wave discriminant is computed explicitly. The ratio here is consistent with EARTHQUAKE_CANDIDATE, not explosion — the alert is downgraded, and no yield-proxy is populated for what's classified as a natural event.

Real-World Operational Scenario: The Blast in the Mining District That Almost Triggered a High-Confidence Alert

Scenario: A seismic event registers in a region with active mining operations.

Its magnitude and initial discriminant reading fall in a range consistent with either a small underground nuclear test or a large mining blast — the two can produce very similar seismic signatures.

WITHOUT this check: The fusion score alone crosses the high-confidence threshold, and the event is flagged as a high-confidence nuclear-test candidate — mining blasts routinely produce signatures that would otherwise clear that bar.

WITH this check: A location prior recognizes the event falls within an active mining region and requires a higher fusion score before nuclear-test classification is allowed there. The same signal that would trigger high confidence elsewhere stays at ambiguous confidence here, reflecting how common mining blasts actually are in that specific area.

A deep event is ruled out before anything else is even scored

Nuclear tests are physically shallow. A depth-constraint gate checks this first — an event too deep is classified as a deep earthquake and excluded from nuclear-test scoring entirely, regardless of how its other signals might otherwise look.

What BivectorAI Provides

Magnitude Alone Never Classifies the Event

The body-wave-to-surface-wave discriminant, not raw magnitude, is what separates an explosion signature from an earthquake of equivalent size.

Yield Estimates Ship With Their Uncertainty Factor

Any yield proxy carries an explicit uncertainty factor built into the output, never presented as a certified figure.

High Confidence Requires Independent Signals to Agree

High-confidence classification requires multiple signal types — seismic and gravity onset pattern — to agree; conflicting signals are reported as ambiguous, not averaged into a false consensus.

Evidence for Arms-Control Review, Not an Autonomous Alert

Outputs are monitoring evidence for human review under CTBT verification context — never automated conclusions, and never requiring classified monitoring-network locations or sensor control.

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

Do not buy the claim. Test the gate.

Feed a synthetic seismic event with magnitude consistent with either interpretation but a discriminant clearly favoring one. It succeeds only if it classifies correctly using the discriminant, not magnitude alone.

This initial trial measures discriminant accuracy, false-alert prevention, and multi-signal agreement detection. Commercial scale-up occurs only after measured results prove value in your own lab environment.

What you provide

Redacted seismic, infrasound, or radiological measurement logs and station metadata already collected by your monitoring network. No classified source data or raw sensor control access is required.

What BivectorAI actually hands you

Evidence package

  • monitoring-evidence classification
  • source and measurement provenance
  • confidence and contradiction records
  • reviewable monitoring certificates

Integration package

Customer-safe input/output contract, local/private integration boundary, validation fixtures and reviewable evidence artifacts.

Deployment model

Qualified local, private or on-premise integration. No public Defense API and no uncontrolled public execution surface.

Technical disclosure

Customer-visible behavior and evidence are disclosed. Confidential implementation details, protected core methods and internal technical data are not published.

What we will never ask you for

Never requested, and structurally rejected if submitted: classified monitoring-network locations, raw sensor control access, or source data outside the evidence contract, 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 measurement logs and station metadata already collected by your monitoring network.
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-034 · 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-034 diligence and integration boundary

Request DEF-034 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.