Release History

Changelog

Evidence-labeled updates across software, hardware, and roadmap work.

Software
Hardware
Tools
bring-upHardware2026-05-24

bring-up — Standalone SD Boot Reached Minimal FSBL

  • Strict-FAT32 SD boot now reaches the minimal FSBL from BootROM
  • PL bitstream programming completes; PCFG_DONE is observed high
  • Remaining gate is FSBL exception handling and final autonomous handoff
  • Classified as BUILD_ARTIFACT until public power-on logs support a stronger claim
Open hardware proof map→
v0.39-KHardware2026-05-21

v0.39-K — ATOMiK Desk Current Live Prototype UI Proof

  • Current live-hardware screenshot promoted as the public ATOMiK Desk proof artifact
  • Top rail de-noise, v0.39-K visual hierarchy, Pulse Bar, Cap Rail, Hero, and Fabric surfaces visible in the captured prototype UI
  • Classified as HARDWARE_VALIDATED for the UI surface, not as a commercial desktop product or performance benchmark
  • Public proof asset: 09-current-live-atomik-desk-v039k.png
Open proof image→
Hardware2026-04-28

Phase 10: Internal Investor Demo System

  • Internal interactive demo screens for explaining state waste, delta accumulation, and hardware proof boundaries
  • Scripted operator demo flow with proof cards for hardware validation, formal verification, and benchmark review
  • State Storm visualization: software scans are contrasted with delta-state accumulation as a narrative model
  • Cost and race visualizations are treated as demo surfaces unless linked to measured artifacts
  • Slide sync, framebuffer screenshot capture, and browser control plane built for live presentation operations
Hardware2026-04-06

Multi-Buffer Change Detection Benchmark

  • End-to-end workload: track N memory regions, detect changes via ATOMiK vs memcmp
  • ATOMiK accumulator-path detection: ~262 cycles per region in the linked AX7020 benchmark artifact
  • Software memcmp comparison retained in the linked benchmark artifact and interpretation note
  • Measured results retained in benchmark artifacts; quote exact speedups only from the linked evidence files
  • Monitoring-rate claims require the matching board-run artifact and interpretation note
  • libatomik C runtime with /dev/mem backend and MMIO ordering fences
Benchmark artifact→Interpretation note→
Hardware2026-04-06

Linux Userspace Validation on Zynq

  • ATOMiK 16/16 PASS from Linux 6.9 userspace (S-mode, MMU enabled, /dev/mem mmap)
  • HARDWARE_VALIDATED stack path: user process -> kernel -> Wishbone CSR -> ATOMiK core
  • Linux 6.9 + OpenSBI 1.3.1 booting on VexRiscv SMP (Zynq XC7Z020)
  • MMIO ordering: fence iorw,iorw + STATUS readback required for Wishbone CSR correctness
  • Frozen baseline with SHA-256 manifest (tag: zynq-linux-v1)
Linux userspace proof→
v0.5.0Tools2026-03-16

v0.5.0 — Kernel Module — Archived Evaluation Experiments

  • /proc/atomik/audit ring-buffer audit log (last 1024 operations)
  • perf/ftrace tracepoints wired to all 4 ioctl handlers
  • Memory shrinkers for COW and network hash tables
  • atomik-report waste analysis tool (--json/--csv/--brief)
  • Prometheus exporter with health endpoints (/healthz, /ready)
  • Grafana dashboard (3-row pre-built JSON)
  • Kubernetes: DaemonSet, Helm chart with RBAC + NetworkPolicy + probes
  • License-key experiment archived; public evaluation is now request-based
v0.4.0Software2026-03-16

v0.4.0 — Python SDK - Historical Release Notes

  • PersistentSyncTable: crash-safe delta persistence with WAL and compaction
  • AsyncSyncTable + AsyncCallbackTransport for asyncio/FastAPI/aiohttp
  • Benchmark --share flag for shareable result summaries
  • DeviceContext: Python bindings for /dev/atomik kernel module ioctls
  • SyncTable + MemoryTransport + CallbackTransport (full transport layer)
  • C accelerator wired into Fingerprint hot path
  • 200+ tests passing
  • pip install atomik-core==0.4.0
v0.3.0Software2026-03-16

v0.3.0 — Python SDK — Serialization & Tracing

  • DeltaMessage serialization: to_dict/from_dict + to_bytes/from_bytes (16-byte wire format)
  • Fingerprint encapsulation fix: no more direct _accumulator access
  • Benchmark --json flag for CI pipeline integration
  • All bench_* functions return structured result dicts
  • 67 tests passing (up from 60)
  • pip install atomik-core==0.3.0
v0.4.0-kmodSoftware2026-03-15

v0.4.0-kmod — Kernel Module — Initial Release

  • COW redundancy detection via kretprobe on wp_page_copy()
  • TCP send deduplication with CRC32C fingerprinting (SSE4.2)
  • Per-container/cgroup waste attribution for Kubernetes
  • /proc/atomik machine-readable metrics interface
  • 27 sysfs attributes for real-time monitoring
  • DKMS packaging, systemd service, udev rules
  • Request-based evaluation access and evidence review
Kernel evaluation notes→
v0.2.0Software2026-03-15

v0.2.0 — Python SDK — Benchmarks & PyPI

  • Benchmark module: python -m atomik_core.benchmark
  • 5 public benchmark functions exported
  • Project URLs on PyPI (atomik.tech, docs, changelog)
  • 60 tests passing, zero dependencies
  • pip install atomik-core==0.2.0
v0.1.0Software2026-03-14

v0.1.0 — Initial Release

  • AtomikContext: LOAD, ACCUM, READ, SWAP operations
  • AtomikTable: 256-context state table
  • DeltaStream: multi-context streaming with message serialization
  • Fingerprint: XOR-based change detection
  • Python 3.9–3.13, Apache 2.0, zero dependencies
  • 50+ tests
Hardware2026-02

Zynq Characterization

  • 6 configs (N=1 to N=512), 4 synthesis strategies
  • N=512 peak synthesis configuration documented for XC7Z020
  • SYNTHESIS_VALIDATED LUT scaling is documented in the linked synthesis artifact
Synthesis artifact→
v3.1.0Hardware2025-12

v3.1.0 — HD HDMI SoC

  • 1280×720@60Hz on $13.50 Tang Nano 9K
  • Custom RV64I CPU with native ATOMiK ISA extensions
  • Delta-driven display pipeline
  • 6,287 LUT (73%), zero TNS
v2.0.0Hardware2025-09

v2.0.0 — PicoRV32 Prototype SoC

  • Single-bank ATOMiK timing and throughput documented in historical hardware artifacts
  • PicoRV32 integration, SPI XIP boot
  • 11/11 hardware tests, +23% Fmax margin

Turn the release trail into a proof review.

The useful next step is not a generic release list. Bring one workload or diligence question and map the relevant hardware, software, synthesis, and roadmap artifacts to an evidence boundary.

Request Investor DiligenceReview Hardware Proof