Evidence request for a US/Canada-controlled identity-validation route for a VBS enclave signing profile

We are preparing a Windows VBS enclave development signing workflow while preserving Secure Boot. Before creating paid Artifact Signing resources, please confirm whether a supported identity-validation arrangement exists that does not use AU10TIX and meets a strict US/Canada AI-component provenance requirement.

For any proposed arrangement, please identify the identity-verification service's developer, legal owner, ultimate controller, any AI/vision model source and license, inference/hosting providers, data-access jurisdictions and automatic fallback routes. Please provide primary documentation and confirm that the resulting certificate profile supports Windows VBS enclave signing, rather than only ordinary code signing.

We are requesting technical eligibility information only. No identity documents, account credentials, binaries, subscription identifiers or payment information are included. We are not requesting an identity-check bypass or a change to Windows security settings.