Skip to content
Patents & licensing

# Patent‑backed rails for verifiable accountability.

Public‑safe overview of MVG’s AI safety and accountability portfolio (20+ filings / in progress). Our posture follows the same evidence spine used across products: Verify → Permit → Gate → Receipts. For licensing and partnership diligence, request the NDA pack.

Request NDA package Verifiable diligence Verify diligence (offline) Email security@
Portfolio map Public vs NDA HALTSEAL themes Counsel FAQ

### No patent license by publication

Public drafts may be distributed under text licenses, but patent rights are not licensed by publication. Any patent license requires a separate written agreement. Nothing on this page is an offer to license.

How to engage Counsel‑friendly 3 steps

### Public → NDA → Pilot

A clean diligence path for Security, Legal, and Procurement — designed to minimize ambiguity and maximize verifiability.

1) Public‑safe overview Representative themes only. No enabling details.
2) NDA diligence pack Relevant filings, claim sets, claim charts, integration paths.
3) Pilot + license terms Field of use, enforcement point, acceptance criteria.
HALTSEAL Procurement kit Contact security

## Portfolio map (public‑safe)

We publish themes that are safe to discuss publicly. Unpublished claim details, prosecution strategy, and diligence materials are shared under NDA with qualified partners.

HALTSEAL
Allowed Agentic AI Verify‑to‑Activation

### Fail‑closed gating where outputs become action

Verify deployment + freshness, mint short‑lived permits, and gate side effects at non‑bypassable control points with immutable receipts.

Product overview Themes
CTC
Filed / in progress Admissible automation Replay‑verifiable

### Canonical receipts + continuity‑verified anchoring

Standards‑track posture for high‑stakes decisioning: canonical bytes, deterministic reason codes, and independent replay verification.

Product overview Public drafts
Kingdom
Filed / in progress Conformance packs PASS/FAIL/HOLD

### Deterministic validators + portable Conformance Packs

Procurement‑ready governance substrate: policy packs, deterministic validators, fail‑closed outcomes, and replayable conformance evidence.

Product overview Procurement kit

## Public vs NDA boundary

What you can evaluate publicly, and what we share only under NDA.

Public site | Under NDA (diligence pack)
--- | ---
Representative themes, posture, and public drafts | Specific claim sets, unpublished filings, and scoped claim charts
Informational only (non‑binding) | Access controlled by NDA; licensing requires separate written agreement
No enabling implementation details | Integration surfaces + enforcement point options (as applicable)
Conceptual evidence spine | Acceptance criteria, evidence schema, verifier harness expectations
No representations about ownership/encumbrances | Ownership and diligence representations (as applicable to the scope)
Safe to distribute broadly | Limited distribution to qualified partners

### NDA diligence pack (what you get)

For qualified partners, we provide a scoped diligence pack that matches your use case (field of use, enforcement point, and integration surface).

- Relevant filings and claim sets (scoped to your deployment)
- Claim charts against representative architectures
- Integration plan + enforcement point options (driver/firmware/hypervisor/egress)
- Acceptance criteria, evidence schema, and verifier expectations
- High‑level licensing model options and pilot structure

Request NDA package Contact security

## HALTSEAL — representative themes (public‑safe)

HALTSEAL targets a new security boundary: model output becomes action. The claim set is built around fail‑closed verify‑to‑activation gating with auditable evidence.

Verify‑to‑Activation Freshness

### Append‑only anchoring + freshness checks

Deployment logic is committed and anchored to an append‑only verifiable log with signed heads. At runtime the system verifies inclusion under a freshness policy and verifies append‑only evolution on head advance.

Permit‑before‑Action Audience‑bound

### Short‑lived permits + immutable receipts

On PASS, mint a scoped, expiring permit bound to an audience (agent/tenant/mission) and record a receipt in an immutable ledger. Subsequent actions require a valid, unexpired, unrevoked permit identifier.

Fail‑closed Disposition codes

### HOLD / QUARANTINE / DENY / ESCALATE

Structured failure semantics help procurement and auditors score behavior under missing/stale/unverifiable prerequisites.

Non‑bypassable hooks Control points

### Driver / firmware / hypervisor

Enforcement is claimed at non‑bypassable chokepoints: kernel‑mode driver paths, device firmware microcode, or hypervisor intercepts.

Licensing gate Quorum

### Tier + m‑of‑n authorization

Permit minting can require a license tier check and m‑of‑n quorum signatures for designated tiers.

### Claims and detailed filings (NDA)

We keep detailed claim sets and unpublished filings off the public site. For licensing diligence or technical review, we share relevant materials under NDA with qualified partners.

Request NDA package Contact security HALTSEAL overview
Procurement kit HALTSEAL Contact security

## Counsel FAQ

Short answers designed to de‑risk diligence and reduce interpretation risk.

### Does this page grant any patent license?

No. Patent rights are not licensed by publication. Any patent license requires a separate written agreement. This page is informational only and not an offer to license.

### What is included in the NDA diligence pack?

A scoped set of relevant filings, claim sets, and supporting materials matched to your field of use. We also include integration and enforcement options and verifier/evidence expectations where applicable.

### How do public drafts relate to the patent portfolio?

Some documents are published as public drafts (e.g., DOI) for interoperability and procurement language. Text licenses may apply to those drafts, but patent rights remain separate.

### What licensing models are available?

Typical structures include evaluation/pilot licenses and production licenses scoped by field of use, deployment surface, and tier. Terms are provided only in writing and depend on the integration surface.

### Where do you share ownership / encumbrance details?

We avoid making public representations. Relevant diligence representations can be provided under NDA as part of the diligence pack.

### What does the review process look like?

Email security@ to request the NDA pack. After NDA, we align a review window with your Security/Legal team, scope the relevant families, and then run a pilot discussion and license path if there is a fit.

### Next step

If you’re evaluating licensing, partnership, or enforcement at a specific control point, request the NDA diligence pack or email security@ with your use case.

Request NDA package Email security@