Compatibility
Evaluation Compatibility
Public review surfaces, hardware paths, and deployment targets with evidence boundaries. Treat this as an evaluation map, not a production support contract.
Platform Review Matrix
| Platform | Status | Min Version | Tested On |
|---|---|---|---|
| Python SDK | Public | Python 3.9+ | Public software path; verify package version before quoting support. |
| C99 Header | Public | Any C99 compiler | Source-review path; compiler claims require current CI or local artifacts. |
| Linux Kernel Module | Evaluation | Linux 5.15+ | Request-based technical evaluation surface. |
| FPGA (Tang Nano 9K) | Archived | Gowin EDA 1.9+ | Historical prototype path; use current proof notes for public claims. |
| FPGA (Zynq) | Validated | Vivado 2025.2+ | AX7020 / XC7Z020 artifacts with proof-level labels. |
| npm Package | Roadmap | Node.js 16+ | Do not quote as a current public product path. |
Evaluation Patterns
State-heavy service path
Review where repeated state diffing, replay, or sync work dominates.
Edge / embedded path
Scope battery, heat, backhaul, and local-latency constraints before claims.
Hardware proof path
Map the workload to measured, hardware-validated, or synthesis-labeled artifacts.
Benchmark Boundary
Software baseline
c7g.xlarge (Graviton3): run local benchmark before quoting throughput
Hardware baseline
Use AX7020 artifacts and interpretation notes before quoting board behavior.
Deployment target
Cloud, edge, and rack claims require a workload-specific benchmark exchange.
Historical articles and technical notes may include exploratory examples, synthesis figures, or modeled comparisons. Treat performance, power, savings, customer, production, and deployment claims as public-safe only when they are linked to measured artifacts or explicit evidence labels. Start with the current docs or evidence-label definitions.