Why it matters
Artifacts gives ForkMesh a concrete mechanism for run outputs collected and browsable beside the repository. Workflow outputs are collected per run and browsable from the repository's Artifacts tab.
Delivery metadata is part of a project, not a separate dashboard that should disappear during a migration. In ForkMesh, artifacts addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles artifacts through the same split it uses across the product: ForkMesh keeps runs, logs, artifacts, releases, quality signals, installers, and downloads close to the mirrored repository.
The behavior is intentionally narrow: Workflow outputs are collected per run and browsable from the repository's Artifacts tab. Outputs can be linked to commits and served by nodes instead of becoming opaque hosted-only assets.
Where it fits
Use artifacts when shipping, validation, and release assets need to remain attached to the preserved repository.
It pairs with the rest of CI, releases & distribution because Artifacts keeps run outputs collected and browsable beside the repository connected to the repository, its signatures, and the nodes that serve it.