HVT
New: live AI agent containment demo

Control AI agentsbefore they go rogue.

HVT is the sovereign control layer for autonomous AI. Every agent action is verified, authorized and recorded before it touches a real system, and anything unsafe halts into SAFE HOLD.

View the evidence
0
step governance loop
0
control layers
L0 to L0
evidence ladder
0 / 0
verification tests passed
Built on
Post-quantum crypto (Kyber / Dilithium)Open-weight modelsvLLM / SGLang runtimeHash-chained evidence logMutual-TLS agent gatewayHuman sign-off gatesPolicy allowlists329 / 329 verification tests
Post-quantum crypto (Kyber / Dilithium)Open-weight modelsvLLM / SGLang runtimeHash-chained evidence logMutual-TLS agent gatewayHuman sign-off gatesPolicy allowlists329 / 329 verification tests
The platform

Two products. One sovereign stack.

Control what your AI agents can do, and run them on infrastructure you own.

Agent control plane

HVT Agent Control

A fail-closed gate between every AI agent and every real system. Unverified, out-of-policy or high-risk actions never execute: they halt into SAFE HOLD and are logged.

Sovereign runtime

HVT Private AI

Open-weight models run on hardware you control, behind identity, policy gates and an immutable evidence log. No commands or data touch third-party cloud APIs.

How it works · scroll

Follow one action through the loop.

Step 01 of 08
SENSE

Capture agent requests, tool calls, context and system state as they happen.

REQUEST #4821IN FLIGHT
agentlogistics-agent✓
actionreroute_grid_load✓
SENSE
UNDERSTAND
VERIFY
DECIDE
AUTHORIZE
EXECUTE
MONITOR
ASSURE
01 // SOVEREIGN AI AGENT CONTROL

How to keep your AI agents under control

Autonomous agents are powerful and fallible. The SSOS governance loop sits between every agent and every real-world system, from energy and ports to aviation, defense and cyber — so a hallucinating, hijacked or runaway agent is stopped at the gate, not after the damage.

LIVE DEMONSTRATION // MODELED, NOT FIELD DATA
Agent containment simulator
AI AGENTSREAL-WORLD DOMAINSSSOS CONTROL BOUNDARY03 VERIFY04 POLICY05 AUTHORIZE06 EXECUTELOGISTICS-AGENTROUTING-AGENTCOMMS-AGENTFINANCE-AGENTFIELD-AGENTENERGYINTEGRITY 100%PORTSINTEGRITY 100%AVIATIONINTEGRITY 100%DEFENSEINTEGRITY 100%CYBERINTEGRITY 100%
Requests
0
Executed
0
Blocked
0
SAFE HOLD
0
Rogue actions executed
0
Agent registry · budgets · kill switch
LOGISTICS-AGENTMedium risk
0/14
ROUTING-AGENTHigh risk
0/14
COMMS-AGENTMedium risk
0/14
FINANCE-AGENTHigh risk
0/14
FIELD-AGENTMedium risk
0/14

Each agent has a tool-call budget. Exceed it and the circuit breaker blocks further calls until the window recovers.

Human approval queue
No actions waiting. High-risk actions held by SAFE HOLD appear here for sign-off, and expire fail-closed after 25 s.
Containment effectiveness
Rogue actions stopped100%
Blast radius (damage)0%

Switch governance OFF and trigger a rogue agent: actions reach critical systems and domain integrity collapses. Switch it ON: the same actions die at the gates and are logged.

Immutable evidence log · hash-chained0 records
Awaiting agent requests…
The control loop every agent action passes through
01
SENSE
02
UNDERSTAND
03 · GATE
VERIFY
04
DECIDE
05 · GATE
AUTHORIZE
06
EXECUTE
07
MONITOR
08
ASSURE

Why you need a control layer

Deploying AI agents without a control plane means trusting third-party clouds, opaque models and unaudited autonomy with your critical systems.

Data & decision sovereignty

Open-weight models run on hardware you control. No commands or sensitive data touch third-party cloud APIs.

0 third-party API calls

Agents that cannot go rogue

Models recommend; policy gates decide. Unverified, out-of-policy or high-risk actions never execute — they halt into SAFE HOLD.

Gate 5: 100% rejection target

Audit every autonomous act

Tamper-evident, hash-chained evidence records let regulators, auditors and courts replay exactly what an agent did and why.

Immutable evidence log

Defense in depth

Seven control layers, from identity and policy gates to bounded tool adapters, so one failed check never means an unchecked action.

7 layers · fail-closed

Law and human oversight built in

Compliance rules, human sign-off levels and multi-signature authorization map your policies and regulation directly into the control loop.

L0–L4 evidence ladder

Staged, evidence-first adoption

A 24-week programme with 8 exit gates lets you prove capability on your own workloads before committing.

8 gates · 24 weeks
Observability

See every decision as it happens.

Throughput, block rate, threat mix and gate latency in one view. Simulated telemetry shown.

Decisions / min
39
Block rate
13.0%
Median gate latency
12 ms
Pending approvals
2
Agent actions per minute
AllowedBlocked
Decision mix
Allowed87.0%
Blocked9.0%
SAFE HOLD4.0%
Threats contained · 24 h
Prompt injection184
Privilege escalation121
Data exfiltration96
Runaway loops73
Audit tampering41
Unsafe tool use58
Gate latency distribution
2 msp50p95p9940 ms
Policy hits · 7 days × 24 h
00:0012:0023:00
Policy as code

Write the rules once. Enforce them on every call.

Switch rules on and off, pick an action an agent might attempt, and see exactly how the gateway would decide.

Rules
policy.yaml
policy: default-agent-policy
rules:
  - min_evidence: L2
  - egress: allowlist
  - budget: 14 calls / window
  - high_risk: require_approval
  - pii: redact
Test an agent action
DENY

Evidence level L1 is below the required L2.

Matched rule
min_evidence: L2
Evidence presented
L1
Logged
Yes, hash-chained
Threats contained

The failure modes that make agents go rogue.

Injection

Prompt injection

Hostile instructions hidden in documents or tool output are rejected at the Verify gate before they reach a decision.

See it contained
Privilege

Privilege escalation

An agent that tries to grant itself new authority is stopped by policy and logged with the evidence level it presented.

See it contained
Exfiltration

Data exfiltration

Calls that move datasets to external endpoints are blocked unless an allowlist and a human sign-off both agree.

See it contained
Integration

One call between your agents and the real world.

Agents propose. The gateway verifies identity, checks policy, requires sign-off where needed, and records the result. Illustrative interface shown.

from hvt import Gateway

gw = Gateway(tenant="ministry-of-energy")

decision = gw.authorize(
    agent="logistics-agent",
    action="reroute_grid_load",
    domain="earth",
    evidence_level="L3",
)

if decision.allowed:
    decision.execute()
else:
    print(decision.state, decision.gate)  # SAFE HOLD, POLICY
Compliance

Evidence your auditors can actually use.

Every decision is logged with the rule, the evidence level and the approver. Export it when someone asks.

NIST AI RMF
Govern, Map, Measure, Manage
Policy-as-code, agent inventory with risk tiers, gate metrics from shadow mode, kill switch and incident log.
EU AI Act
Human oversight, logging, risk management
Named-approver queue, tamper-evident decision logs, risk-tier controls and documented rollout gates.
ISO/IEC 42001
AI management system evidence
Versioned policies, role-based approvals, exportable evidence records and review checkpoints.
OWASP LLM Top 10
Injection, excessive agency, data disclosure
Verify gate for injection, bounded tool adapters and budgets for excessive agency, redaction for disclosure.

This is a mapping to help gather evidence. It is not a certification and not legal advice.

Intellectual property

Patent-pending inventions by Salem Salah bin Omair AlShamsi.

The control layer rests on four pending inventions, conceived and architected by Salem Salah bin Omair AlShamsi in Abu Dhabi.

Named inventor and sovereign design authority
Salem Salah bin Omair AlShamsi
Chairman of Rabdan Global & SAS Rabdan · Sovereign Design Authority · Abu Dhabi
Read the technical record
IP-01PATENT PENDING

HVT SWITCH™ Live-Gate AI Arbitration

A fail-closed physical and deterministic logical choke point intercepting all consequential agent actions. LLMs and autonomous models are prevented from triggering external effects without valid, unexpired sovereign authority.

Sub-millisecond emergency stop measured at P50/P95/P99 with zero bypass leakage.
Inventor: Salem Salah bin Omair AlShamsi
CUMULATIVE LIMIT
IP-02PATENT PENDING

Autonomous Execution Envelopes & Authority Graph

Cryptographic multi-dimensional boundaries capping rate, velocity, financial thresholds, geography and blast radius, so many individually permitted acts cannot sum up to one forbidden outcome.

Cumulative harm prevention with dynamic cryptographic revocation propagation.
Inventor: Salem Salah bin Omair AlShamsi
#9f3a#c71e#02bd#7e44
IP-03PATENT PENDING

Deterministic State Synchronization & DM-CODE

A tamper-evident, single-source state ledger providing continuous telemetry correlation across heterogeneous endpoints, designed for complete resistance against desynchronization.

440.85 ms deterministic cold crash recovery with total state restoration.
Inventor: Salem Salah bin Omair AlShamsi
CAPABILITY ≠ AUTHORITYCONNECTED ≠ AUTHORISEDEXECUTED ≠ VERIFIEDUNKNOWN = SAFE HOLD
IP-04PATENT PENDING

Four Axioms Runtime Enforcement Engine

A constitutional governance engine embedding the Four Axioms That Never Bend into every compute layer: Capability ≠ Authority, Connected ≠ Authorised, Executed ≠ Verified, and Unknown = Safe Hold.

Zero invariant violations across 25,000 automated fuzzing cycles.
Inventor: Salem Salah bin Omair AlShamsi
0/0
deterministic checks passed
Verified under the design of Salem Salah bin Omair AlShamsi
0
invariant violations
Verified under the design of Salem Salah bin Omair AlShamsi
0%
mutation kill rate
Verified under the design of Salem Salah bin Omair AlShamsi
0
fuzzing cycles, zero violations
Verified under the design of Salem Salah bin Omair AlShamsi

Status: patent pending. No patent has been granted, and these descriptions summarise pending applications by Salem Salah bin Omair AlShamsi, not issued claims. Filing details are available on request through the contact form.

04 // COGNITIVE LAYER

Private AI: Client-Sovereign LLM Infrastructure

No client data or operational commands touch third-party commercial cloud APIs. Open-weight foundation models run strictly on customer-controlled high-memory GPU servers with hardware-enforced policy gates.

GOVERNANCE PRINCIPLE // EVIDENCE OVER CLAIMS
PILLAR 01

Evidence Over Claims

Performance, accuracy, concurrency, and cost are benchmarked on actual client workloads before accepting results.

PILLAR 02

No Unverified Execution

The model can recommend or prepare actions, but policy and authorization gates decide whether a tool or command may execute.

PILLAR 03

Fail Safely & SAFE HOLD

Ambiguous authorization, stale lease, or failed dependency halts into an explicit SAFE HOLD state with auditable logs rather than executing a guessed action.

PILLAR 04

Strict Order of Work

1. Prompts & Policy Gates → 2. Verified Retrieval (RAG) → 3. LoRA/QLoRA adapter tuning only where justified. Never pre-train blindly.

CONTROL BOUNDARY PIPELINE // SAFE HOLD GATE
01. Client Workflows & UI

Approved internal applications, operator consoles, encrypted telemetry

PASSED
02. AI Gateway & Identity

Mutual TLS, tenant/role access, cryptographic request IDs, rate quotas

PASSED
03. Policy & Safety GatesCRITICAL GATE

Allowlists, compliance rules, human sign-off triggers, SAFE HOLD engine

PASSED
04. LLM Runtime Engine

Qwen3.8-27B dense or Kimi K3 MoE on vLLM/SGLang with strict memory isolation

PASSED
05. Knowledge & Grounded RAG

Vector embeddings with tenant metadata isolation; strict source-citation audit

PASSED
06. Bounded Tool Adapters

Idempotent schemas, hard timeouts, schema validation, zero direct DB execution

PASSED
07. Immutable Evidence Log

Tamper-evident run records capturing prompt hashes, tool params, and gate decisions

PASSED
05 // SSOS OPERATING SYSTEM

The 8-Step Sovereign Governance Loop

Autonomous agents must operate inside strict boundaries across every system they touch. No step in the loop proceeds without verified evidence.

CIRCULAR 8-PHASE STATE ENGINEDOMAINS: 5 (SPACE TO CYBER)
SSOS LOOPHALTED AT 0301SENSE02UNDERSTAND03VERIFY04DECIDE05AUTHORIZE06EXECUTE07MONITOR08ASSURE
Current Invariant:RULE ENFORCED: NO AUTHORIZE WITHOUT VERIFY
01
SENSE

Capture agent requests, tool calls, context and system state as they happen.

02
UNDERSTAND

Fuse signals, map what each agent can reach, and flag anomalies such as injection or drift.

03
VERIFYGATE REQUIRED

CRITICAL GATE: Validate identity, check crypto signatures, test invariants.

04
DECIDE

Generate candidate actions or policy interventions for the agent request.

05
AUTHORIZEGATE REQUIRED

Check compliance rules, human sign-off levels, and multi-signature gates.

06
EXECUTE

Run the approved action atomically through a bounded tool adapter.

07
MONITOR

Observe telemetry delta, measuring actual vs predicted performance.

08
ASSURE

Commit cryptographic attestation to immutable audit records.

EVIDENCE LEVELS (0 - 4 VERIFICATION HIERARCHY)AUDIT CRITERIA
L0None

Unverified claim; strictly rejected at Gate 03.

L1Self-Asserted

Telemetry timestamped by originating node.

L2Documented

Traceable schema and cryptographic signature verified.

L3Tested

Automated regression and invariant checks passed.

L4Independently Certified

HSM attestation plus human operator multi-key.

Solutions

Built for every sovereign AI deployment.

Sovereign states

  • Keep data and decisions on national hardware
  • Map national law into the authorization gates
  • Replay every autonomous act for oversight bodies
Talk to us

Defense & security operators

  • Bounded authority across every operational domain
  • Hardware-enforced policy gates on all tool calls
  • SAFE HOLD instead of guessed actions
Talk to us

Critical infrastructure

  • Energy, ports and aviation agents under bounded authority
  • Prompt-injection and privilege-escalation containment
  • Staged rollout with eight exit gates
Talk to us
Deployment

Start small. Scale on evidence.

Sizing is indicative and confirmed by benchmarks on your own workload before you buy hardware.

Pilot

Prove it on one server
Model
Qwen3.8-27B (Q4 Quantized)
  • GPU: 1× RTX PRO 6000 Blackwell 96 GB / 1× H100 80 GB
  • Memory: 128 GB ECC RAM, 2-4 TB Gen5
  • Context: 262k native (ext. to 1M)
  • Agent gateway, policy engine and evidence log
  • Shadow mode on your live traffic
Start a pilot

Enterprise

Most chosen
High-concurrency production
Model
Kimi K3 (2.8T MoE / 104B Active)
  • GPU: 16× H200 (2.26 TB VRAM) or 16× B200 (2.88 TB VRAM)
  • Memory: 1-2 TB Server-Grade RAM, 8-16 TB NVMe Fabric
  • Context: 1M Token Context
  • Everything in Pilot
  • Named-approver workflows and exportable evidence
Talk to sales

Sovereign

Air-gapped and regulated
Model
Open-weight, your choice
  • Fully air-gapped deployment
  • Customer-held keys and HSM attestation
  • Independent red-team assessment (Gate 7)
  • Runbook training for operators and approvers
  • Tailored to your regulator
Contact us
Proven before it ships

Eight exit gates. Evidence at every one.

A 24-week programme where each phase must pass a measurable gate before the next begins.

Gate 01Wk 1 - 3

Agent & Workload Discovery

Inventory every agent, tool, data store and external destination. Define risk tiers and the security perimeter.

Agent inventory and risk tiers signed off
Gate 02Wk 4 - 6

Isolated Runtime Baseline

Provision customer hardware, pin drivers, and benchmark the isolated model runtime on real workloads.

First-token latency under 45 ms on client hardware
Gate 03Wk 7 - 9

Policy Design & Gateway

Write allowlists, budgets, approval rules and evidence requirements. Deploy the identity-aware gateway in shadow mode.

Policies reviewed by security and legal owners
Gate 04Wk 10 - 12

Knowledge Ingestion (RAG)

Tenant-isolated vector indexing, metadata filters and source-attribution verification.

Zero unsupported answers on golden reference questions
07 // OPERATIONAL BRIEFINGS

Technical Video Archive

Recorded hardware testbenches, simulated laser handovers, and live terminal captures of policy gates in action.

CONFIG: /DATA/VIDEOS.TS
The Age of Autonomous AI & Governed Infrastructure
04:14
Autonomous Multi-Agent Architecture // Strict Boundary Gates // Zero Trust
GovernanceID: VID-03

The Age of Autonomous AI & Governed Infrastructure

Strategic architectural overview of multi-agent autonomous decision systems, cryptographically enforced boundary gateways, and sovereign intelligence foundations built for mission-critical operations.

PLAYLIST // 3 REPOSITORY ENTRIES
The Age of Autonomous AI & Governed Infrastructure
04:14
Governance

The Age of Autonomous AI & Governed Infrastructure

Autonomous Multi-Agent Architecture // Strict Boundary Gates // Zero Trust

UturnU Decision Intelligence & Autonomous Travel Agent
00:26
Private AI

UturnU Decision Intelligence & Autonomous Travel Agent

UturnU Autonomous Agent // Multi-Attribute Utility Engine // Live UI

Multi-Domain SSOS Observation & Policy Authorization Cycle
00:46
Governance

Multi-Domain SSOS Observation & Policy Authorization Cycle

Stage 01 Observe // SSOS Governance Loop // Access Authority Gating

Questions, answered.

It sits between your AI agents and the systems they act on. Each requested action is verified, checked against policy, held for a human when risky, executed through a bounded adapter, and recorded in a tamper-evident log.

06 // INTEGRITY DECLARATION

What We Don't Claim

Credibility requires stating the boundaries of what the product does and does not do.

GOVERNANCE PRINCIPLE // EVIDENCE OVER CLAIMS
LIMITATION 01
BOUNDED SPEC

Guardrails Reduce Risk, They Do Not Remove It

No control layer can prove an agent will never misbehave. HVT narrows what an agent can do and records what it did. Residual risk remains and must be owned by the operator.

LIMITATION 02
BOUNDED SPEC

Hardware Sizing Is Indicative, Not a Purchase Guarantee

GPU VRAM requirements (for example 16× B200 for Kimi K3) are derived from parameter math and batch overheads. Final sizing requires benchmarks on your actual workload before you buy hardware.

LIMITATION 03
BOUNDED SPEC

Models Do Not Replace Deterministic Rules

Open-weight LLMs are probabilistic. In this architecture the model is never the authoritative source for system state, financial balances or safety-critical commands.

LIMITATION 04
BOUNDED SPEC

Demos Are Modeled, Not Production Telemetry

The interactive simulator on this site uses scripted scenarios to illustrate the control flow. Measured results come from the staged rollout gates on your own infrastructure.

LIMITATION 05
BOUNDED SPEC

Compliance Mapping Is Not Certification

We map controls to common frameworks to help with evidence gathering. That is not a certification or legal advice. Your auditors and counsel make the final determination.

All numbers in this brief are derived directly from verified Python simulation outputs or optical testbench logs.
Request Verification Logs
CONTACT

Talk to our team

Tell us which agents you run and which systems they touch. We will walk you through the control layer, share benchmark profiles under NDA, and scope a pilot.

DIRECT MESSAGE

For quick questions or an urgent briefing request:

Message us on WhatsApp
TECHNICAL DOSSIER INTAKE* REQUIRED FIELDS

Stay current on sovereign AI control.

Research notes and test results, when there is something worth sending.