Artifacts

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 f2a0a9f87d7e

Name
checkouts/current/congruency/tools/pair_loop.py
Kind
forge-source
Version
3ed4d72c8c
Forge sha
f2a0a9f87d7eb058e4bef39f380dae7810582deb
Locations
1 registration · minted by #463
First seen
2026-07-16 07:58 UTC

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 f2a0a9f87d7eb058e4bef39f380dae7810582deb — which probes forge-artifacts and returns every place those bytes live. The registry below lists every place they were registered.

Every location this sha is registered at
#MINTING TICKETNAMEVERSIONKINDREGISTERED
24#463checkouts/current/congruency/tools/pair_loop.py3ed4d72c8cforge-source2026-07-16 07:58 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.

← all kinds