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 beb8f3f599ea

Name
raspios-trixie-arm64-lite
Kind
forge-vm
Version
beb8f3f599ea
Forge sha
beb8f3f599ea2f262ca089beaa0692a7b0a009665cccb5246bda918a72372ac8
Locations
1 registration · minted by #455
First seen
2026-07-16 05:21 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 beb8f3f599ea2f262ca089beaa0692a7b0a009665cccb5246bda918a72372ac8 — 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
7#455raspios-trixie-arm64-litebeb8f3f599eaforge-vm2026-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.

← all kinds