Controlled physical release
An exact controlled physical release is identified. Changes still require their own qualification.
A curated collection selected from the controlled Garmo Bible. Start with stronger release evidence, then inspect the exact integration boundary.
Physical release, executed digital verification, internal physical output, source and architecture are different evidence classes. We keep them visible.
An exact controlled physical release is identified. Changes still require their own qualification.
Recorded digital tests, formal checks or synthesis. The scoped result does not qualify an analog plant or a fabricated device.
Named implementation records with physical-output hashes. These are not blanket foundry-signoff or functional coverage claims.
Implemented source, executable models or structural checks. Tool execution and physical qualification remain release-specific.
Source-backed engineering records retained from the original collection. Ask for the exact release package.
Architecture and interface contracts retained for integration planning. No instant executable or hard macro is implied.
Preserve 122 existing approved public listings; their weaker evidence remains labeled, not promoted.
Add 390 distinct canonical identities with actual source/reference/digital/physical evidence.
Rank exact controlled releases and executed digital verification above GDS-only inventory evidence.
Exclude unnamed numbered inventories, testbenches, duplicate IDs, opaque/no-substantive-implementation records, degenerate one-cell KX results, forbidden product families and unsupported analog-hard-IP assertions.
Do not turn node counts or physical-output hashes into foundry qualification.
Every added record retains a Bible section/table/row locator and record digest; retained entries without a parsed table match keep their original canonical source reference.
Source digest: 0c0fac8cf5d2dc39313609e8d3bb20ddd6d8816c5380fa94447f877cb0fd4f0e
Ranking is an editorial evaluation priority, not a probability of correctness. The original 122 public entries are preserved; the additions prioritize named, substantive implementation records. An IP listing is not an automatically granted license.