Operations
Backends are capability providers behind Power's shared execution and evidence contracts. Choose them by model format, platform, and trust boundary rather than treating the backend name as the architecture.
Build profiles
The llamacpp-mtp-fr profile is intentionally separate because it modifies the
pinned source. Ordinary llamacpp builds do not need the experimental patch.
Service endpoints
Health and model inspection endpoints expose effective, non-secret settings so benchmark and deployment automation can reject configuration drift.
Artifact installation
The artifact provisioner requires an expected filename, maximum byte length, and SHA-256 digest. It streams into a private staging file, verifies the exact bytes, and commits atomically under a cross-process lock. Offline policy fails closed when a previously verified artifact is unavailable.
The hosted model store is content-addressed under ~/.a3s/power by default.
Model aliases point to manifests rather than weakening blob identity.
Production boundaries
- Bind development servers to loopback unless a reviewed transport policy says otherwise.
- Use RA-TLS or vsock deliberately; constructing the embedded runtime never chooses a transport for the caller.
- Treat simulated TEE mode as development-only.
- Do not claim confidential GPU execution from CPU TEE placement alone.
- Preserve raw report fields when saving attestation evidence.
- Treat mixed quantization and vocabulary-reduced drafting as quality-gated, workload-specific techniques.
- Keep model bytes, ACL, binary hashes, drivers, and host controls with every performance acceptance record.
Supply chain and storage
The pure-Rust tee-minimal path reduces native inference dependencies, while
the llama.cpp path trades a larger native toolchain for mature GGUF and CUDA
capabilities. Audit the feature profile that will actually ship.
For Rust API types and feature flags, use docs.rs/a3s-power.
