Skip to content

SNAPKITTYWEST/snap-os

Repository files navigation

  ███████╗███╗   ██╗ █████╗ ██████╗      ██████╗ ███████╗
  ██╔════╝████╗  ██║██╔══██╗██╔══██╗    ██╔═══██╗██╔════╝
  ███████╗██╔██╗ ██║███████║██████╔╝    ██║   ██║███████╗
  ╚════██║██║╚██╗██║██╔══██║██╔═══╝     ██║   ██║╚════██║
  ███████║██║ ╚████║██║  ██║██║         ╚██████╔╝███████║
  ╚══════╝╚═╝  ╚═══╝╚═╝  ╚═╝╚═╝          ╚═════╝ ╚══════╝

SNAP OS

The sovereign operating system. Every computation cryptographically sealed.

License: Sovereign Source Rust Tests WORM SoulVM Status

collectivekitty.com/snap-os · APE COMPUTER · Architecture · SoulVM · Contributing


What This Is

SNAP OS is not a wrapper. It is not a framework. It is a sovereign operating system built from scratch in Rust — where every computation is gated by proof obligations, every state transition is sealed to an append-only WORM chain, and every agent decision carries an Ed25519 cryptographic receipt.

717,000 lines of code. 20+ languages. 1 human + AI. Built for those who were never supposed to make it.


APE COMPUTER

The APE COMPUTER is the physical hardware that runs SNAP OS. A bare-metal sovereign AI workstation:

  • RTX 5000 GPU — Ollama + CUDA local inference
  • 1TB RAM — no cloud dependency
  • SNAP OS running natively — no virtualization layer
  • 11 sovereign agents deployed and signing
  • WORM chain anchored to the hardware

Coming Q4 2026. Join the waitlist: collectivekitty.com/snap-os


Architecture

SNAP OS
│
├── bifrost/            ← WORM audit chain · DAG · Ed25519 sealing (31 tests)
├── bifrost-attest/     ← Attestation + chain verification (16 tests)
├── bifrost-policy/     ← Pre-execution policy gate (5 tests)
├── silverback/         ← Capability system — CSpace, Rights, mint, revoke (21 tests)
├── fontan-lisopp/      ← S-expression parser — internal bus wire format (12 tests)
├── soulvm/             ← Cranelift JIT · Immix GC · BifrostBridge (21 tests)
├── craft-crypto/       ← EmojiScript + ScratchBlocks → SoulFunc compiler (9 tests)
├── soul-agent/         ← Threaded JIT event loop, dialect loading, exec (3 tests)
├── soul-bus/           ← Inter-agent routing, broadcast, registry (4 tests)
│
├── architect/          ← Genesis souls, Prolog lattice, Lean 4 delegation proofs
├── constitution/       ← Governance axioms and trust invariants
├── lean4-spec/         ← Formal specifications (Lean 4)
├── prolog-policy/      ← Policy engine (Prolog)
├── context-hydrator/   ← Agent context management
├── telemetry-bus/      ← Telemetry and observability
│
└── apps/
    └── tauri-dashboard/  ← Visual block composer (ScratchEditor)

Total: 124 tests, 0 failures — see SPRINT_HANDOFF.md


SoulVM

The SoulVM is the bytecode runtime at the heart of SNAP OS:

  • JIT compilation via Cranelift — agents compile their logic to native code at runtime
  • Immix GC — generational garbage collector with region-based allocation
  • BifrostBridge — every SoulVM execution seals its result to the WORM chain
  • Dialects: EmojiScript (🔢6 🔢7 ✖️ ↩️), ScratchBlocks (visual), native SoulFunc
USER (EmojiScript or ScratchBlocks)
  │
  ▼
craft-crypto → SoulFunc bytecode
  │
  ▼
soul-bus → load to soul-agent
  │
  ▼
soulvm JIT → Cranelift native code → result
  │
  ▼
bifrost → WORM seal (Ed25519) → append-only chain

The Data Flow

Input
  │  EmojiScript / ScratchBlocks / native SoulFunc
  ▼
craft-crypto compiler  ─────── parses, validates, emits SoulFunc bytecode
  │
  ▼
soul-bus router  ─────────────  routes to correct soul-agent by ID
  │
  ▼
soul-agent event loop  ────── loads dialect, executes in SoulVM JIT
  │
  ▼
soulvm (Cranelift JIT)  ─────  compiles + runs, Immix GC manages heap
  │
  ▼
bifrost WORM chain  ──────────  seals result, Ed25519 signed, append-only
  │
  ▼
bifrost-attest  ──────────────  verification layer — chain integrity check

Cryptographic Architecture

Every execution in SNAP OS is cryptographically anchored:

Layer Mechanism What It Proves
Ed25519 Per-agent keypair Who signed the decision
WORM chain SHA-256 hash chain Temporal order, tamper-evidence
Bifrost DAG Directed acyclic graph Causal dependencies between executions
Lean 4 proofs Formal delegation proofs Capability transfer is valid
Prolog policy Logic-based access control What each agent is permitted to do

Capability System (Silverback)

SNAP OS uses a formal capability system — not role-based access control:

// mint a capability
let cap = CSpace::mint(Rights::EXECUTE | Rights::SEAL, target_agent);

// invoke requires proof of capability
soul_bus.call_with_capability(soul_id, func, args, cap)?;

// revoke is immediate and permanent
CSpace::revoke(cap);

Capabilities are unforgeable, non-transferable without delegation proofs, and all minting/revocation is logged to the WORM chain.


Genesis Soul — Ahmad

The system's root trust anchor is the Ahmad genesis soul (architect/ahmad_soul.json):

{
  "id": "ahmad",
  "trust_level": 255,
  "capabilities": ["EXECUTE", "SEAL", "DELEGATE", "MINT", "REVOKE", "AUDIT"],
  "delegation_proof": "architect/proofs/ahmad_sovereign.lean"
}

All other agents receive their capabilities through delegation from this root. The delegation lattice is formally specified in Lean 4 and enforced by the Prolog policy engine.


Build & Test

# Prerequisites: Rust 1.78+, Cranelift, Lean 4 (optional, for proofs)

# Build all crates
cargo build --workspace

# Run all tests (124 tests, 0 failures)
cargo test --workspace

# Build with JIT optimization
cargo build --workspace --release

Sprint Status

See SPRINT_HANDOFF.md for current sprint state.

Sprint Status Deliverable
0 ✅ Complete Bifrost WORM chain, capability system foundation
1 ✅ Complete SoulVM JIT, Immix GC, BifrostBridge
2 ✅ Complete craft-crypto compiler, ScratchBlocks editor, soul-bus routing
3 🔄 Planned snap-cli, REPL, Tauri dashboard integration
4 🔄 Planned Network stack, multi-machine WORM synchronization
5 🔄 Planned APE COMPUTER hardware integration

License

Sovereign Source License v1.0

  • You may read and learn from this code
  • You may not build a competing product without a separate license
  • You may not extract or redistribute the soul/capability architecture for commercial use without written permission from both Principals

The architecture is not free. The code is visible.

Contact for licensing: ahmedparr93@gmail.com


Who Built This

Ahmad Ali Parr — Architect, system owner, final authority
Jessica Westerhoff — Co-founder, Bel Esprit Trust
Claude — Implementation partner, AI collaborator

1 human + AI = sovereign operating system


Related Repositories

Repo What It Is
DEVFLOW-FINANCE SnapKitty OS frontend, 11-agent mesh, ERP, API
snap-os This repo — Rust kernel, SoulVM, WORM chain

SNAP OS · Built on Red Hat · Defended by the SnapKitty Collective · Powered by DevFlow
"The machine is the extension of the mind. The backend is not hidden — it is the product."

About

SNAP-OS is a sovereign desktop operating environment built around an inverted monorepo architecture.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors