Frequently Asked Questions
Public answers about evaluation access, proof labels, and current prototype status. Can't find your answer? Contact ATOMiK.
General
ATOMiK is a state-aware compute architecture for systems that spend too much work rediscovering what changed. The public materials cover the live hardware prototype direction, proof artifacts, developer adoption path, and roadmap toward ATOMiK Desk and Resource Fabric.
State-heavy systems repeatedly move, replay, rescan, or reconstruct state even when only a small part changed. ATOMiK makes state change, delta application, and adaptive execution first-class primitives so a workload can be evaluated around the work that actually changed.
The repository includes website, docs, proof notes, software, SDK, math, hardware, and live prototype implementation areas. Public claims are labeled as measured, hardware-validated, software-validated, synthesis-validated, projected, conceptual, or roadmap.
No. ATOMiK Desk is a live prototype and demonstration surface for state-aware compute. Live screenshots show prototype progress; concept visuals show product direction and are not represented as commercial functionality.
Evaluation
No. ATOMiK is request-based right now so evaluation time is focused on real workloads, evidence review, and technical fit.
There are three public paths: proof-review reservation, technical-evaluation reservation, and request-based investor, licensing, or design-partner diligence for teams with a real state-heavy workload and defined success criteria.
Not necessarily. The right first step may be proof review, software exploration, a benchmark exchange, or a hardware-backed demo depending on the workload and available artifacts.
Yes. Evaluation Access is intended for technical founders, engineers, researchers, infrastructure teams, and early evaluators who can review evidence and provide useful workload feedback.
Technical
Public software and proof materials can be reviewed in conventional development environments. The live hardware prototype path is currently documented around Zynq / NaxRiscv / Linux artifacts.
Both address state synchronization problems, but ATOMiK frames state change and delta application as compute primitives. Public comparisons are best read with the evidence labels and artifact links attached to any performance claim.
Performance claims are public-safe only when linked to measured artifacts or clearly labeled synthesis/modeling notes. The current AX7020 matrix is intentionally caveated: naive hardware access can lose, while batching and workload personality choices determine whether the architectural path helps.
No public certification claim is made. Some architecture properties may be relevant to security-sensitive systems, but security, compliance, and safety claims require scoped review and artifact-backed validation.
Support
For public evaluation, use the contact form and include the workload, platform, and evidence you want reviewed. GitHub issues are appropriate for repo bugs and documentation problems.
File bug reports on GitHub Issues. Include your SDK version, language, OS, and a minimal reproduction case for fastest resolution.
Feature requests work best when tied to a concrete state-heavy workload or evaluation goal. Design partner conversations are the best path when the request affects roadmap, prototype mapping, or evaluation deliverables.
Still have questions?
Bring a workload, proof question, or evaluation goal and ATOMiK will route it to the right next step.