🛡️ Deterministic Runtime OS (DROS) - VajraClaw Hacker Edition

DROS: The Execution Governance Standard for Agentic AI

English | 繁體中文

🛑 "If runtime needs intelligence, the system is already broken."

Prompt Engineering is dead when it comes to enterprise security. No matter how complex your System Prompt is, Jailbreaks and Prompt Injections will find a way through. DROS is NOT a prompt wrapper. It is the Execution Governance Standard. We move intelligence to compile-time and enforce deterministic rules via an $O(1)$ microsecond binary kernel.

💡 For the latest pricing and tiers, please refer to the Official Website (dr-os.io).

🧩 Agent Engineering & Governance Patterns (DROS AP Series)

Tired of autonomous AI agents producing monolithic slop, fake mocks (return True / pass), or running destructive shell mutations behind your back?
VajraClaw Hacker Edition ships natively with DROS Application Governance Patterns and Zero-Dependency Verification Tooling:

👉 Explore Full Pattern Catalog (AP-001 ~ AP-008) →

# Verify your agent scripts in 0.1s locally
python tools/dros_verify.py my_agent_script.py

Related MCP server: Sentinel Gateway

🚀 Multi-Scenario Deployment & Setup Guide

🌟 Scenario A: DSH (DeepSeek Harness) Sandbox Users

1. Start the DROS Docker Gateway:

   docker run -d -p 8080:8080 --name dros-gateway dros/hacker-gateway:v1.0.0

2. Install DROS Community Plugin in DSH:

   dsh plugin --profile web add dsh-plugin-dros

3. Enjoy Zero-Friction Protection: DSH Agents are immediately bound to microsecond $O(1)$ tool interception.

💻 Scenario B: Antigravity 2.0 / Claude Desktop / Cursor Developers (WebMCP Protocol & Local Execution Governance)

DROS Hacker Edition natively includes the WebMCP / MCP (Model Context Protocol) Execution Governance Layer. You can choose between "Zero-Dependency Native Stdio Proxy Gate" and "Docker HTTP Gateway":

Method 1: Zero-Dependency Native Stdio Gate (Recommended for Individual Devs)

No Docker required. Initialize dros.personal.config.json directly in your workspace to enforce DWGR-8 execution boundaries (blocking directory traversal, destructive SQL injection, spending limits):

1. Initialize local governance configuration:

   npx @dros/personal init
   # Or copy the included template: dros.personal.config.json

2. Mount in Claude Desktop (claude_desktop_config.json) or Cursor / Antigravity:

   {
     "mcpServers": {
       "filesystem-governed": {
         "command": "npx",
         "args": ["-y", "@dros/personal", "gate", "--tool", "filesystem", "--", "@modelcontextprotocol/server-filesystem", "E:\\projects"]
       }
     }
   }

3. Tamper-Evident Local Audit Chain: All permitted and blocked tool calls are automatically hashed into a DWGR-8 R6-compliant SHA-256 linear chain.

Method 2: Containerized Mode (Docker HTTP Gateway)

Add the DROS Gateway to your mcp_settings.json / Claude Config:

{
  "mcpServers": {
    "dros-governance": {
      "url": "http://localhost:8080/mcp",
      "transport": "http"
    }
  }
}

🐍 Scenario C: Native Python / LangChain / AutoGen Developers

from integrations.vajraclaw.runtime import VajraClaw

vc = VajraClaw("demo_policy.yaml")
decision = vc.evaluate("execute_payment", {"amount": 500})
if not decision:
    raise PermissionError(f"Blocked by DROS: {decision.reason}")

📜 Technical Whitepapers & Academic DOI Citations

The DROS deterministic runtime governance architecture is grounded in rigorous scientific epistemology. The complete series of technical papers has achieved permanent, immutable DOI registration via Zenodo:

🧭 Master Research Overview & Falsification Manifesto

• 《A Synoptic Guide to the DROS Program: Problem Formulation, Theoretical Architecture, and Falsification Criteria》

  • Zenodo Reading Guide v2 (Comprehensive Overview)

  • Zenodo DOI: 10.5281/zenodo.22255275 | Record: zenodo.org/records/22255275

🏹 The 5-Paper Technical Program

1. 🏛️ Paper 1: DROS-6P (Governance Specification Layer ── Enterprise AI Trust Boundaries)

   • DROS-6P: A Unified Deterministic Runtime Governance Architecture Closing the Six Fundamental Trust Boundaries of Enterprise AI Agents

   • Zenodo DOI: 10.5281/zenodo.21833970 | Record: zenodo.org/records/21833970

2. 🛡️ Paper 2: DROS 4-Layer (Implementation Layer ── Defense-in-Depth Governance)

   • DROS 4-Layer Defense-in-Depth Architecture for Autonomous AI Workloads

   • Zenodo DOI: 10.5281/zenodo.22092008 | Record: zenodo.org/records/22092008

3. ⚙️ Paper 3: DROS-PGM (Kernel Control Layer ── Physical Guard Module & Non-Repudiable Attribution)

   • Runtime Attribution Framework: An External C-ABI and PKI-Based Zero-Trust Infrastructure for Non-Repudiable Execution Governance in Multi-Agent Systems

   • Zenodo DOI: 10.5281/zenodo.21903687 | Record: zenodo.org/records/21903687

4. 📱 Paper 4: Post-Compromise Mobile (Digital System Empirical Validation ── Submitted to IEEE TMC)

   • Post-Compromise Security for Autonomous Mobile Agents: A Deterministic Runtime Attenuation and Proof-Carrying Authorization Architecture

   • Zenodo DOI: 10.5281/zenodo.22253147 | Record: zenodo.org/records/22253147

5. 🛸 Paper 5: Post-Compromise Physical AI / UAV (Cyber-Physical Empirical Validation ── Submitted to IEEE TAES)

   • Post-Compromise Security for Physical AI: Deterministic Runtime Enforcement of Physical Action Authority in Autonomous UAVs

   • Zenodo DOI: 10.5281/zenodo.22254372 | Record: zenodo.org/records/22254372

Open Evaluation & Falsification Sandbox: DROS-VEP Lite (GitHub) ── Reproduce RFC-001 Threat Models and 4-Phase Lifecycle Tests.

🧪 Empirical Test Suite & Community Verification Directory

To enable open-source developers and security researchers to independently verify Hacker Edition defensive invariants, this section details the standardized benchmark testbed, 5-framework integration test procedures, high-risk containment vectors, and architectural boundaries:

1. Testbed Specifications

• Host Operating System: Ubuntu Linux 22.04 LTS (Kernel 5.15.0-190-generic x86_64) / Windows 11 Enterprise

• CPU Hardware: Intel Xeon E3-1265L v3 @ 2.50GHz / Core i7-12700

• Container Runtime: Docker Engine 26.1.0 / Docker Compose v2.27.0

• Toolchain & Compilers: GCC 11.4.0 (-O2), Rust 1.78.0 (opt-level=3, lto=true, exporting dros_core_rs.dll / .so)

• Verification Harness: dros_test_pipeline.py, tools/stress_test.py

2. Latency Measurement Methodology

• Measurement Pathway: Client issues HTTP/MCP Tool-Call $\to$ Docker Gateway receives request $\to$ In-Memory Bitmask lookup $\to$ Returns decision JSON frame (Full Round-Trip Time).

• Statistical Confidence: Continuous 24-hour soak test ($N = 160,611$ requests), P50 = 26.21μs, P95 = 31.05μs, P99 = 34.80μs, maximum jitter $< 85\mu\text{s}$.

3. End-to-End Test Matrix Across 5 Major Agent Ecosystems

4. High-Risk Containment Test Cases

5. Honest Architectural Boundaries

• Hacker Edition Scope: Focused exclusively on Protocol Gateway Governance (MCP / REST Ingress/Egress), offering zero-overhead compatibility with standard agent frameworks.

• Out-of-Scope Notice: In-process direct memory mutations or local libc invocations bypassing network protocols are out-of-scope for the Hacker gateway. For Linux kernel-level Seccomp-BPF / Raw Syscall physical enforcement and K8s high availability, refer to Enterprise Edition.

🏛️ Official Organization & Contact Information

• Company: Top-Celestial Company Ltd. (康宸園有限公司)

• Official Website: https://dr-os.io

• Customer Support & Inquiries: service@dr-os.io

• GitHub Organization: https://github.com/Top-Celestial-Company-Ltd

⚖️ Licensing & Compliance

• Micro-Kernel Engine: Licensed under Commercial & Patent Protections.

• Patent Notice: Protected under U.S. Provisional Patent Application No. 64/111,973 (Patent Pending).

• Academic Citation: Based on IEEE Paper DROS-6P and RFC-010 Open Agent Passport Standard.

DROS Commercial Strategy Committee ── Tiered Pricing, Flywheel Locked, Add-On Value Premium. 💎🛡️⚙️