Skip to main content

​
Verified current behavior

​
Attestation status

Attestation evidence can still provide meaningful hardware authenticity and freshness checks. The missing policy checks limit the conclusion: a pass must not be described as complete proof that an approved release image processed the request.

​
Model status

The documented model set includes:
  • qwen36-27b;
  • glm-5.2, resolving to zai-org/GLM-5.2;
  • deepgram/general-nova-3 for audio transcription.

​
Known gaps

​
Priority sequence

  1. Publish reproducible images, provenance, and release-to-measurement reference sets.
  2. Expose per-GPU verdicts, review the current check semantics, and enforce exact-set backend binding for multi-GPU inference.
  3. Resolve package/runtime version reporting.

​
Trust progression

Each stage answers a different question. Manufacturer evidence authenticates hardware claims. Release policy decides whether measured values are approved. Route assurance binds that decision to a model path. Reproducible provenance connects the approved measurements to source and build inputs.
Status entries distinguish source review from live testing. The presence of an API route alone does not establish that a model or end-to-end workflow is operational.