The ticket-side artifact registry — congruency holds the metadata and the provenance, the forge holds the blob. Kind is the tag: open a kind to list its artifacts, or an artifact to see every location its content sha is registered at.
artifacts › sha f1bf3523334a
This sha is the content address of the blob itself, so it is shown in full: it is what the universal resolver takes as input — python3 tools/resolver.py f1bf3523334a05c9bb3ff61ac877da17673a0b4d971bd987fdb96fb5878b25cd — which probes forge-artifacts and returns every place those bytes live. The registry below lists every place they were registered.
| # | MINTING TICKET | NAME | VERSION | KIND | REGISTERED |
|---|---|---|---|---|---|
| 19 | #455 | fabric-cidata | f1bf3523334a | forge-vm | 2026-07-16 05:21 UTC |
These bytes are registered at exactly one location. Were the same sha registered again — under another ticket, name or version — it would appear here as a second location of this one artifact, not as a second artifact.