SYSTEM BLUEPRINT & SIX-ENGINE ARCHITECTURE SPECIFICATION

Engineered for Exabyte Throughput & Uncompromising Durability

Aarkam decomposes the storage stack into six decoupled, independently deployable layers. Zero-allocation memory pipelines, SIMD vectorization, Direct I/O NVMe bypass, and out-of-band machine learning eliminate the latency and hardware penalties of legacy object stores.

End-to-End Zero-Allocation Write Path

Client Payload → Durable NVMe Chunks
1. S3 Ingest AWS SigV4 Auth Gateway :57776
2. Envelope Crypto AES-256-GCM (HSM) Client Boundary
3. Cauchy Math AVX-512 SIMD (8+3) Ahmodi Parity Kernel
4. gRPC Transit Parallel mTLS Mesh Rokka StorageNodes
5. LSM Direct I/O Direct NVMe Bypass Kdouja Engine
01

Ahmodi: Cauchy Reed-Solomon Erasure Coding Engine

AVX-512 & AVX2 Vectorized Galois Field GF(2⁸) Kernel
58.3% Storage Cost Cut

Where legacy systems store 3 full replicas (consuming 300% raw disk space), Ahmodi divides payloads into \(K\) data chunks and mathematically computes \(M\) parity chunks. Using Cauchy distribution generator matrices over Galois Field \(GF(2^8)\), any sub-matrix is guaranteed non-singular, allowing instantaneous inversion via Gaussian elimination.

Supported Enterprise Profiles:
Profile (4+2): 66.7% Efficiency · Tolerates 2 Failures
Profile (8+3) [Standard]: 72.7% Efficiency · Tolerates 3 Failures
Profile (16+4) [Archive]: 80.0% Efficiency · Tolerates 4 Failures
SIMD AVX-512 Vector Kernel 12.5 GB/s / Core
// Vectorized GF(2⁸) multiplication via 4-bit nibble tables
var vLowTable = Vector512.Create(LowNibbleTable[coeff]);
var vHighTable = Vector512.Create(HighNibbleTable[coeff]);
var vMask = Vector512.Create((byte)0x0F);

// Parallel 64-byte chunks processed per single clock cycle
var lowRes = Avx512BW.Shuffle(vLowTable, lowNibbles);
var highRes = Avx512BW.Shuffle(vHighTable, highNibbles);
var result = Vector512.Xor(lowRes, highRes);
02

Kdouja: Embedded LSM-Tree Persistence Engine

Direct I/O NVMe Bypass · Arena Skip-List · WAL Replay
Zero Inode Exhaustion

Storing millions of small chunks as discrete operating system files exhausts filesystem inodes and fragments metadata caches. Kdouja operates in-process inside every storage node, packing chunks into contiguous multi-gigabyte append-only segment containers.

By supporting unbuffered Direct I/O (O_DIRECT), Kdouja bypasses the operating system page cache entirely. NVMe writes stream straight from userspace memory buffers to physical flash with zero double-buffering kernel copies.

Durability Guarantees:
Synchronous WAL Append: Every chunk key-value write is committed to disk before acknowledging upward.
Arena Memory Pools: Skip-list nodes allocated from contiguous unmanaged spans; zero .NET GC pauses.
1% False-Positive Bloom Filters: Rejects non-existent chunk reads in memory without disk I/O.
03

Rokka: Stateless Raft MON & Distributed Data Daemon

Consistent Hash Ring · Epoch Fencing · Speculative Hedged Reads
Zero Bottleneck Mesh

Rokka splits responsibility between a stateless Raft MON consensus coordinator (handling topology changes, cluster epochs, and partition mapping) and a per-host storage daemon (streaming 4KB chunks in parallel over gRPC with mutual TLS).

Because the coordinator is decoupled from the data path, raw chunk uploads bypass the controller entirely—achieving linear horizontal scaling up to thousands of storage hosts without coordinator saturation.

Speculative Hedged Reads:

When retrieving an (8+3) erasure-coded object, only 8 chunks are needed. If any storage node experiences a transient I/O stall, a speculative read is instantly fired to a parity node. The first 8 chunks to arrive reconstruct the file, completely eliminating tail latency spikes.

04

Abodi: Autonomous Telemetry & Predictive Failure Sidecar

Out-of-Band Observation · S.M.A.R.T. Correlation · ML Runway Forecasting
Zero Write Path Interference

Hardware fails continuously in large fleets. Traditional storage discovers drive death only after write failures cause I/O timeouts. Abodi continuously queries S.M.A.R.T. counters, IOPS latency jitter, and flash wear levels directly from the OS kernel via WMI or sysfs.

Its machine-learning correlation rules calculate an impending failure runway (e.g. 72 hours). Rokka automatically fences the degraded node from new writes and migrates replicas gracefully while the drive is still capable of serving reads.

Monitored Telemetry Signals:
• S.M.A.R.T. Reallocated Sector Count (ID 05)
• Current Pending Sector Count (ID 197)
• NVMe Media Wear Percentage & Critical Warning Byte
• P99.9 Tail-Latency Jitter & Kernel SCSI Bus Resets
05

Aarkam.IO: Edge S3 SigV4 Gateway & Management Portal

AWS SigV4 Authentication · DMZ Rate Limiter · RBAC Orchestration
Port :57776

Aarkam.IO serves as the public perimeter gateway. It fully implements the AWS SigV4 (AWS4-HMAC-SHA256) protocol, allowing existing enterprise applications, backup agents, and data science pipelines to connect as a 100% drop-in replacement for AWS S3.

The gateway provides cryptographic multi-tenant namespace isolation, bucket-level RBAC policy evaluation, rate limiting, and an administrative Web UI for cluster monitoring.

Gateway Capabilities:
• Full S3 API: Multipart Uploads, Object Tagging, Lifecycle Rules
• S3 Object Lock (Compliance Mode WORM retention)
• TLS 1.3 Strict Termination & AES-256-GCM Envelope Encryption
• Per-Tenant Capacity Quotas and Burst Bandwidth Limits
06

Aarkam.AM: Single-Binary Cluster Orchestration CLI (`am.exe`)

Deterministic Exit Codes · Zero-Downtime Rolling Upgrades · JSON Automation
Single Binary

Engineered for Site Reliability Engineers and automation pipelines, Aarkam.AM (am) is a standalone binary that provides comprehensive cluster control.

From initializing Raft MON quorums to triggering offline hardware evacuations, inspecting Galois Field SIMD benchmarks, and scheduling rolling upgrades, `am` eliminates manual administration risks through built-in preflight safety checks and structured output formats.

CLI Operations POSIX Exit Codes
# Non-blocking live status refresh
am cluster status --watch 1s

# Graceful storage host evacuation with preflight safety
am node evacuate storage-04 --reason "NVMe replacement" --yes

# Hardware wear evaluation via Abodi ML
am abodi score --device nvme0n1 --format json
Independent Architectural Benchmarks

Comparative Storage System Matrix

How Aarkam compares directly against MinIO, Ceph, and AWS S3 in high-assurance enterprise deployments.

Feature / Capability Aarkam (Beta) MinIO Ceph (RGW) AWS S3
National Data Sovereignty 100% KSA In-Kingdom Self-hosted Self-hosted Foreign Jurisdiction (CLOUD Act)
Erasure Coding Math Ahmodi AVX-512 Cauchy RS AVX2 Reed-Solomon Jerasure Plugin (Pool level) Opaque (AWS internal)
Storage Footprint Overhead 25% – 37.5% (Ahmodi 8+3 / 16+4) 50% (Standard 4+2) 200% (Default 3x rep) Hidden / High egress billing
Failure Detection Abodi Predictive ML Sidecar Passive / Reactive Scrubbing / OSD heartbeat Cloud Managed
NVMe Direct I/O Bypass Native (Kdouja O_DIRECT) OS Page Cache Dependent BlueStore Raw Partition Proprietary
Dedicated Operator CLI Aarkam.AM (am.exe) mc CLI ceph / radosgw-admin aws cli
NCA ECC & SDAIA PDPL Ready Certified Mappings Built-In Customer Manual Config Customer Manual Config Requires KSA Local Zone add-ons