Product Authorization

Your commercial agreement and trusted OEM authorization provider determine which purchased technical capabilities are authorized. TDSE Runtime is always present in a complete TDSE installation; TDSE Circuit and the GPU/FPGA Add-ons are usable only when both included in the installation and allowed by that provider. License format, term, seat, node, and installation-count policy are not TDSE Runtime API contracts.

Activate and verify

1. Install the complete TDSE package supplied for your company.
2. Follow the TDSE or authorized OEM instructions for any authorization material required by that provider. The trusted OEM host is responsible for connecting its authorization service to TDSE. Depending on that integration, the provider may be built into the host or delivered separately; it is not necessarily a file in the TDSE installation.
3. Run:

tdse doctor

The report keeps four facts separate:

• Included — the product or Add-on exists in this installation.
• Authorized — the trusted authorization provider permits the capability.
• Available — the required runtime provider and hardware are visible.
• Qualified — separate release evidence approves the exact platform and provider combination. tdse doctor never infers this status.

For machine-readable support evidence use:

tdse doctor --json-out tdse-doctor.json

If Runtime reports that authorization requires attention, confirm the OEM provider configuration and any authorization material against the installed release and company policy. Preserve the JSON report when contacting support.

Authorization changes and expiry

TDSE receives neither a license file nor a valid_until value through its public authorization ABI. It asks the trusted OEM host whether a technical capability is allowed at an authorization point; the OEM provider owns all license, expiry, renewal, company-identity, and session-policy decisions.

Do not infer that an already-created model will continue after a license or provider policy changes. The applicable OEM authorization policy defines that behavior. Creating a new model or selecting a protected hardware Add-on may create another authorization point, but this is not a substitute for the OEM's documented lifecycle policy.

OEMs and license-provider integrators receive a separate Authorization Provider Integration reference. Ordinary customer applications do not implement that callback.