Review the control model
Signed lifecycle, commitments, verification classes, recovery, settlement separation, and Repository Assurance are documented directions.
05 / Capability roadmap
Evidence before promotion.
The roadmap distinguishes recorded capabilities, external dependencies, and separate governance decisions. A vendor-interface dependency is not a routine next internal engineering step.
Strict binding is blocked
Trusted source time, identity, provenance, and negative cases remain requirements. Strict CUDA execution/output binding additionally depends on a documented vendor-supported primitive/API.
Separate approval decisions
Independent review, production recovery and key-lifecycle evidence, customer validation, and explicit governance approval precede broader authorization.
Roadmap status
Recorded, blocked, and not claimed.
A recorded capability is not production authorization. Agent Trust Runtime v1.0 remains a public technical preview / prelaunch asset with a private, local/synthetic runtime release.
Control foundation
Signed lifecycle, verification classes, recovery, and settlement controls are documented for review.
RECORDEDRepository Assurance
Release references and repository-local results support reproducibility only within their evaluated scope.
REVIEWABLERecorded GCP co-residence
Google Confidential Space + Intel TDX + NVIDIA H100: signature, GCE, GPU, and workload identities verified; CUDA probe observed. Result: PASS_NON_PROMOTABLE; classification: ATTESTED_WORKLOAD_AND_GPU_CORESIDENCE. This is not strict CUDA execution/output proof.
Complete composite GPU assurance
The internally tested composite-attestation implementation and historical RTX 4000 Ada runtime pilot are separate records. The GCP TDX/H100 run does not establish complete AMD SEV-SNP + NVIDIA NRAS composite-profile qualification or final release provenance.
CLOSEDTier 3 GPU execution/output binding
Status: BLOCKED_BY_VENDOR_PRIMITIVE_AVAILABILITY. Based on documented public NVIDIA and Google interfaces reviewed as of October 2026, no supported primitive/API has been identified to cryptographically bind GPU attestation to a specific CUDA execution context or workload output. Additional internal testing alone cannot establish Tier 3; a vendor-supported mechanism or newly documented supported path must be separately qualified.
Production promotion
Production readiness, customer validation, independent audit, and Mainnet authorization remain separate decisions, not granted by recorded passes.
NOT CLAIMEDConditional review path
Evidence first. Promotion is not automatic.
These are separate requirements, not a promised engineering schedule or an automatic progression.
01Current RecordPreserve scoped repository, runtime, and GCP co-residence evidence separately.
02 / BLOCKEDHardware BindingRequires a documented vendor-supported primitive/API for strict execution/output binding, then separate qualification. Internal testing alone cannot establish Tier 3.
03Independent Technical ReviewReview original records, supported bindings, negative cases, and provenance independently.
04Customer ValidationValidate an agreed bounded workflow without inferring adoption or production approval.
05Production DecisionOnly explicit governance can authorize a new release state; no gate is opened here.