Skip to content

P.O.W.E.R. platform support matrix

This matrix is the operational boundary for the v3.6.2 release contract. It separates automated lifecycle coverage from model-backed, physical-host, GPU, and retrieval-quality evidence. A green CI job does not certify a different host, provider, corpus, or performance envelope.

Current support boundary

Platform / environment Tested now Conditional Not certified by this matrix
Linux, Python 3.11–3.14 Ubuntu CI runs the full test suite, Ruff, MyPy, documentation and release-contract gates; package smoke runs wheel/sdist outside the checkout. Dense, reranked, and provider-backed workflows require a local model cache and an actually bound provider. Host-independent latency, GPU benefit, ANN recall, and reranker quality beyond the published release receipts.
macOS Deferred indefinitely for v3.6.2; no macOS CI or release upgrade evidence is claimed. No scheduled release target. A future proposal requires a named runner, owner, and fresh receipts. All macOS compatibility, performance, GPU, dense real-vault, and reranker claims.
Hosted Windows CI Deferred indefinitely for v3.6.2; no Windows CI or release upgrade evidence is claimed. No scheduled release target. A future proposal requires a named runner, owner, and fresh receipts. All hosted Windows lifecycle, provider, performance, GPU, dense real-vault, and quality claims.
Physical Windows 11 25H2 Deferred indefinitely for v3.6.2; the installation guide is informational and is not a release certification. No scheduled release target. A future proposal requires exact host and artifact receipts. Physical Windows compatibility, GPU performance, CUDA availability, and latency claims.

Evidence rules for agents

  • Treat tested as lifecycle coverage only. It proves the named command path on the named runner and Python version.
  • Treat conditional as a precondition, not as a successful runtime claim. Check power doctor --json and require active provider readback before dense work.
  • Treat unsupported or missing evidence as a stop condition. Do not silently fall back from an explicitly requested GPU provider to CPU.
  • For a real vault, require an immutable generation, complete coverage, a content-free retrieval receipt, cold/warm/process/MCP controls, and resource attribution before making latency or ranking claims.

Source of truth

The executable checks live in CI, the release workflow is release.yml. Windows procedures remain outside the supported-platform boundary for v3.6.2 and have no scheduled release target. The roadmap records evidence boundaries and pending gates in ROADMAP_POWER.md.