Evaluate the right GSP scope
Select a real supported workflow, its deliverables and an explicit qualification target.
Public evaluation
The public workbench accepts bounded synthetic resource and model scenarios and returns a complete evidence envelope. No proprietary PDK, design database or customer dataset is necessary.
Private engineering
Create a verified organization and save a versioned project. Review the software and integration release identities, then run the same bounded workflow with private scenario data under the published quotas.
Native and CAD evaluations
A native GSP workflow needs the approved endpoint, exact release, authorized tool/PDK access, agreed input scope, resources, acceptance criteria and a recorded execution grant. Engineering programs in the module registry are not instantly executable just because they have a canonical identity.
Commercial agreement
Use the existing request, quote, agreement-review and release-entitlement process. No public workbench run, quote acceptance or architecture record silently creates production, foundry, distribution or proprietary-source rights.