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 84b04d26f4be
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 84b04d26f4be16cacd857fcb7b56e438bb6e283e04f69f0c349286f69acbc7a0 — 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 |
|---|---|---|---|---|---|
| 17 | #455 | workstation-seed | 84b04d26f4be | 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.