Archived planning engines
DieWeaver and ModelNative 1.2.0; unchanged archive/source identities; bounded JSON scenarios.
Connected.
Not assumed compatible.
Discover what is integrated in this release, what needs a deployment binding and what requires separate qualification.
| Integration | Available scope | Boundary |
|---|---|---|
| GARMO DieWeaver 1.2.0 | Unchanged archived engine in a bounded JSON-only subprocess | Source digest enforced before execution; synthetic samples, not silicon performance |
| GARMO ModelNative 1.2.0 | Unchanged archived engine in a bounded JSON-only subprocess | Source digest enforced before execution; synthetic samples, not silicon performance |
| GSP website workflow / 1 | Placement → model mapping → independent checks → evidence | Two engine adapters, one connected resource context |
| Existing native GSP deployment | Operator binding required | No fabricated endpoint or native engine execution |
| Foundry / PDK / model collateral | Release-specific authorized integration | No external process certification is created by this website |
| Private organization projects | Persistent revisions, job queue, artifacts, cancellation and exports | Single persistent SQLite deployment; no automatic global scale-out |
Qualification register.
Connected planning workflow
Selected-resource mapping, independent checks, artifact consistency and four benchmark cases.
GSP canonical modules
73 canonical identities reconciled from the controlled inventory. Per-release implementation and qualification must be bound separately.
Native GSP service
Contract adapter implemented; no native endpoint, foundry access or production runtime connected in this build.
Commercial foundry tool certification
Existing chip-release evidence remains unchanged. Tool/flow/node certification requires the relevant external qualification.
Hardware emulation and analog PHY qualification
No emulation appliance, process-qualified PHY, TCAD calibration or fabrication qualification is created by a website update.
Public production operation
Persistent hosting, workspace approval, DNS/TLS, authorized mail, legal/content review and operational validation.
Qualification belongs
to a precise combination.
Engine version. Process. Library. Constraint set. Model. Methodology. Output acceptance criteria.
Prepare an integration review
Select a workflow, identify the existing GSP service or controlled package, define the input/output contract, and provide the approved release and authorization scope.
Program membership, technical integration and external certification are different relationships. None is implied by a logo.