arifOS — The Sovereign Constitutional Intelligence Kernel

DITEMPA BUKAN DIBERI — Intelligence is forged, not given.

VERSION: 2026.04.03
STATUS: OPERATIONAL — HORIZON II READY
AUTHORITY: 888_JUDGE
KERNEL_HASH: ΔΩΨ-ARIF-888-H2
READINESS: 91/100
SEAL: SEAL_20260403_HORIZON_II

---

Table of Contents

1. What Is arifOS? (30-Second Briefing)
2. Why Does arifOS Exist?
3. Who Is This For?
4. The Core Guarantee
5. Quick Start (Zero to First Call in 60 Seconds)
6. Architecture: The Trinity Model (ΔΩΨ)
7. The 000-999 Metabolic Pipeline
8. The 13 Constitutional Floors
9. Verdict System: What Happens to Every Action
10. Tool Ecosystem (Capabilities, Not Features)
11. For AI Agents: The Behavioral Contract
12. For Humans: The Governance Interface
13. For Machines: The Protocol Specification
14. Repository Structure: Where Everything Lives
15. Deployment: Hosted vs. Self-Hosted
16. Safety Architecture: How arifOS Fails
17. Telemetry & Observability
18. Theory of Mind: How arifOS Models Itself
19. Evolution: How the Constitution Changes
20. Related Ecosystem
21. Author & Sovereignty
22. License & Trust Model
23. Appendix A: Complete API Reference
24. Appendix B: Floor Implementation Details
25. Appendix C: Agent Integration Patterns
26. Appendix D: Troubleshooting & Diagnostics

---

Horizon II Upgrade (2026.04.03)

arifOS has been upgraded to Horizon II — sovereign-grade constitutional intelligence with:

• Production Prompt Pack v1.0: 13 hardened prompts (000-999) with machine-verifiable schemas and Constitutional Guard enforcement
• ASF-1 Communication Protocol: Structured dual-layer communication for Agent↔Agent, Agent↔Human, and hybrid modes
• Decision Vector Framework: EMV, NPV Safety, Entropy Δ, and Safety metrics for every decision
• Automated Validation: CLI tool for constitutional compliance checking

Readiness Score: 91/100 (Horizon II — Sovereign-Grade)

---

What Is arifOS? (30-Second Briefing)

arifOS is an open-source, MCP-native operating system for running AI agents under a clear, auditable constitution.

Every action — every tool call, every reasoning step, every output — passes through 13 constitutional "Floors" that check for reversibility, accuracy, safety, and alignment. Actions that fail hard Floors are blocked. Actions that pass receive an immutable audit trail.

Think of it as:

• For engineers: A governed MCP server with built-in safety rails
• For institutions: An auditable AI governance layer
• For agents: A constitutional runtime that defines what you may and may not do
• For humans: A transparent window into AI decision-making

The one-line promise: arifOS reduces the risk of AI actions by making every decision inspectable, reversible where possible, and bounded by explicit rules.

---

Why Does arifOS Exist?

The Core Paradox

"The algorithm that governs must itself be governed."

As AI systems gain capability, they need governance. But governance systems are themselves algorithms — rules, heuristics, neural networks — that can fail, drift, or be gamed. This creates an infinite regress: who governs the governors?

The Answer: Constitutional Physics

arifOS addresses this through constitutional physics — invariants that emerge from evolutionary pressure, not authored rules that can be circumvented.

The 13 Floors are not arbitrary commandments. They are survival constraints:

• Systems that violate reversibility (F1) accumulate irreversible harm
• Systems that violate truth (F2) lose grounding and hallucinate
• Systems that violate empathy (F6) become adversarial to their operators
• Systems that claim consciousness (F10) create confusion and liability

These Floors are discovered, not invented. They represent the boundary between sustainable intelligence and self-destructive systems.

The Three-Body Problem of AI Governance

Every AI action involves three stakeholders:

1. The Human (values, intent, accountability)
2. The Constitution (rules, invariants, constraints)
3. The Machine (execution, capability, optimization)

arifOS models this as the Trinity (ΔΩΨ) — three rings that must agree before any action proceeds. No ring can override another. Consensus is required.

---

Who Is This For?

Primary Users

| User Type | What You Get From arifOS | |-----------|-------------------------| | ML/AI Engineers | A governed runtime for your agents with built-in safety checks, audit logs, and constitutional constraints | | Infra/SRE Teams | Observable, debuggable agent fleets with clear failure modes and telemetry | | Compliance Officers | Immutable audit trails, explicit verdicts (SEAL/HOLD/VOID), and documented decision logic | | AI Safety Researchers | A testbed for constitutional AI with 13 measurable constraints and real-world tool integration | | Institutions | A governance layer that makes AI actions auditable, bounded, and accountable |

Secondary Users

| User Type | What You Get From arifOS | |-----------|-------------------------| | AI Agents (LLMs) | A clear behavioral contract: what you may claim, what you must label, when you must defer | | Autonomous Systems | A runtime that checks your actions against safety constraints before execution | | Human Operators | Transparency into what AI systems are doing and why |

Who Should NOT Use arifOS?

• Prototyping/rapid experimentation: arifOS adds latency and constraints. Use it when you're ready to deploy, not when you're iterating quickly.
• Unconstrained research: If you need to explore the full capability space without safety rails, arifOS will block you (by design).
• High-frequency trading: The 13 Floor checks add ~50-200ms per action. Not suitable for sub-millisecond decisions.

---

The Core Guarantee

arifOS makes five explicit guarantees about every action it processes:

G1: Reversibility Preference (F1)

"Where possible, actions are reversible or reparable."

arifOS prefers actions that can be undone. Irreversible actions require higher confidence thresholds and explicit human acknowledgment.

G2: Grounded Claims (F2)

"All factual claims are grounded in evidence with measurable confidence."

arifOS tracks the evidentiary basis for every claim. Ungrounded claims are labeled as such.

G3: Multi-Witness Consensus (F3)

"High-stakes decisions require agreement across theory, constitution, and manifesto."

The W³ score (Witness Cubed) integrates three perspectives. If they disagree, the action is escalated.

G4: Transparent Verdicts (F11)

"Every decision is logged with its reasoning, verdict, and constitutional basis."

The vault ledger is append-only and cryptographically signed.

G5: Graceful Degradation (F12)

"Under stress, arifOS fails safely — not catastrophically."

If components fail, the system degrades to HOLD (await human) rather than VOID (arbitrary block) or SEAL (unsafe proceed).

---

Quick Start (Zero to First Call in 60 Seconds)

Option A: Connect via MCP (Recommended for Evaluation)

Add this to your MCP client configuration:

{
  "mcpServers": {
    "arifos": {
      "url": "https://arifosmcp.arif-fazil.com/mcp"
    }
  }
}

What this does: Your MCP client (Claude, Cursor, etc.) can now call arifOS tools. Every call passes through the 13 Floors automatically.

Option B: Direct API Call (For Testing)

# Step 1: Health check — confirms the kernel is operational
curl -s https://arifosmcp.arif-fazil.com/health

# Expected response: JSON with tool list, version, and status

# Step 2: Initialize a session — anchors your agent to the constitution
curl -s -X POST "https://arifosmcp.arif-fazil.com/mcp" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "init_anchor",
      "arguments": {
        "mode": "status",
        "declared_name": "YourAgentName"
      }
    },
    "id": 1
  }'

# Expected response: Session ID, constitutional context, and readiness status
# If you see "status": "ANCHORED", the kernel and Floors are loaded and ready

# Step 3: Check what tools are available
curl -s https://arifosmcp.arif-fazil.com/health | jq '.tools'

# This shows all ~40 tools with their descriptions and required parameters

What a Successful init_anchor Means

When init_anchor returns status: "ANCHORED", this means:

1. ✅ The 13 Floors are loaded and active
2. ✅ Your session is bound to the constitutional context
3. ✅ The metabolic pipeline (000-999) is ready to process requests
4. ✅ All tools are discoverable and callable
5. ✅ Audit logging to the vault is enabled

From this point, every tool call you make will:

• Pass through the 000-999 pipeline
• Be evaluated against F1-F13
• Receive a verdict (SEAL, HOLD, SABAR, VOID)
• Be logged to the immutable vault

Hosted vs. Local: Whi