VLSI KoreaTRUST & PROVENANCE
Know what the evidence proves.
VLSI Hub connects public engineering assets with their sources and documented dependencies. Discovery, source review, engineering profiling, reproduction and silicon evidence are separate stages. No single “Verified” badge covers them all.
| State | Meaning and limits |
|---|---|
| Source linked | A public upstream URL is recorded. It does not prove the source was freshly reviewed or that any engineering claim was tested. |
| License checked | License bytes were retrieved from a pinned source and hashed. The observed identifier and scope are shown. Repository licensing does not override notices on bundled components or manufacturing terms. |
| Upstream documented | A specific engineering claim or relationship is supported by a cited section of official documentation at a recorded revision. Tool/target versions remain unknown unless the source names them. |
| Hub reproduced | A retained execution identifies source revision, tools, environment, command, conditions, exit status, logs and artifacts. A passing simulation covers the stated test only. |
| Independently reported silicon result | A cited independent silicon implementation report identifies the actual design and conditions. It is separate from a Hub test and from an upstream assertion. |
| Known failure | Retained, scoped evidence documents a failure for a specific combination or run. An intentional negative-control assertion is labeled as such. |
| Not tested | No qualifying execution evidence is recorded. Unknowns are visible and neutral. |
Collection and review
Adapters collect bounded public metadata from official repositories. Canonical upstream URLs, source revisions, observation timestamps and source-byte hashes accompany fresh observations. Ambiguous identities, missing licenses, invalid facts and incomplete execution claims enter quarantine for review rather than automatically updating trusted records.
Legacy catalog labels retain their historical observation dates; they are not silently promoted to fresh checks. The existing Knowledge Core keeps its own immutable, temporal claim history. Its SUPPORTED and human-reviewed VERIFIED assessments do not imply Hub execution.
Compatibility is scoped
A source may document using a tool without testing every release. Every relationship therefore carries a qualifying scope, source/target revisions when known, a citation, limitations and a distinct execution status. Connections are not transitively inferred. A shared HDL language or open PDK is insufficient to establish a working flow.
Benchmarks require conditions
Area needs units, technology and implementation configuration. Timing needs constraints and operating corner. Power needs measurement conditions. Comparisons require compatible revisions, tools, libraries, PDKs, voltage, temperature, constraints and seeds. Missing context suppresses numerical ranking.
Rights, corrections and removal
We store short original summaries, metadata, source links and hashes. Public access does not imply redistribution permission. Upstream documentation remains at its source. Authored examples identify their license. Report a correction, broken link, ownership issue or removal request with the resource URL and supporting source through the existing contribution form.
Suggest a source-backed correction →Basic discovery needs no account. Saved entries stay in this browser using the established My VLSI controls. See the existing privacy policy for analytics and browser storage.