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 a8427ee4d9a9
a8427ee4d9a9c45b16af983c036cae2431c7248bThis 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 a8427ee4d9a9c45b16af983c036cae2431c7248b — 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 |
|---|---|---|---|---|---|
| 27 | #424 | checkouts/current/forge2/agent_tools_suite/pyproject.toml | 79aafe198f | forge-source | 2026-07-16 23:01 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.