Skip to content

SNAPKITTYWEST/snap-os

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

3 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

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

4 stars

Watchers

0 watching

Forks

Packages

 
 
 

Contributors