The Official Reference Implementation of the DROS-RFC-001 Architecture Specification
Ultra-low latency, bare-metal Dharma Reasoning Micro-Kernel.
This repository contains the authoritative C++ implementation of the Dharma Reasoning Operating System (DROS) Micro-Kernel.
As the original creators of the DROS Architecture, this codebase serves as the absolute standard for deterministic, hallucination-free reasoning engines designed for Large Language Models (LLMs).
DROS is composed of two primary layers:
-
The Open-Source Core (This Repository): This is the fundamental reasoning engine. It implements the strict constraints and deterministic logic routing of the
DROS-RFC-001Specification. It is 100% open-source under the AGPL-3.0 license. -
The Commercial Guard (VajraClaw): For enterprise and proprietary deployments, we offer VajraClaw, our physical-layer C-FFI Circuit Breaker. VajraClaw seamlessly wraps around this open-source core, providing anti-tamper UUID binding and commercial licensing exemptions without requiring your entire enterprise application to be open-sourced. 👉 Learn more about Commercial Licensing
This repository is governed by the DROS-RFC-001 Specification. Any implementation claiming to be DROS-compliant must adhere to the structural constraints laid out in our official whitepapers.
- Protocol: Fully compliant with
DROS-RFC-001Semantic Constraints. - Architecture: Minimalist footprint, zero-dependency core logic designed for Absolute Truth mapping.
- Integration: Plugs directly into your C++-based architectures to act as the cognitive firewall for LLMs.
1. Installation & Build
mkdir build && cd build
cmake ..
make2. Execution
./dros_coreFor complete integration tutorials and API references, please visit our Official Documentation.
Our technological authority is protected by strict Copyright and Open Source Licensing. This software is governed by the GNU Affero General Public License v3.0 (AGPL-3.0).
WARNING: DROS is a highly protected intellectual property. The AGPL-3.0 license is intentionally utilized as a legal shield to enforce open-source compliance for all networked applications.
- Networked Usage (SaaS / API): If you wrap this micro-kernel inside a server, API, web application, or SaaS offering, you MUST open-source the complete corresponding source code of your entire application stack under AGPL-3.0.
- Proprietary Commercialization: This kernel CANNOT be closed-source or integrated into proprietary/commercial systems without a separate Commercial License from the original creators. If you need this, you must procure VajraClaw.
- No "Soft" Exceptions: We do not recognize "internal enterprise use" as an exemption if the service interfaces with public networks. Any obfuscation, bypassing of license constraints, or stripping of original authorship attribution is a direct violation of international copyright law.
For commercial inquiries and proprietary licensing, please visit our website.