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 4bc1a755a80b
4bc1a755a80bb78b5dd79140345d7491f911179bThis 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 4bc1a755a80bb78b5dd79140345d7491f911179b — 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 |
|---|---|---|---|---|---|
| 21 | #459 | migrations/0034_artifacts_page.sql | 3842e5159d | forge-source | 2026-07-16 06:29 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.