Artifact Entry v1 Schema

Validates one L0 artifact entry: a hash-only CycloneDX component (evidence or derived artifact) as enumerated inside a Case Provenance BOM's components array. Normative requirements: https://sec.hypermedia.au/standards/artifact-entry/v1 This is a component fragment schema: it deliberately carries no BOM envelope (bomFormat/specVersion/serialNumber) because it validates one entry inside a Case Provenance BOM, not a document.

Validates the artifact-entry standard.Raw schema (JSON).

Field	Type	Required	Constraints
bom-ref ART-002: evidence-<ordinal>-<hashPrefix> or derived-<sourceOrdinal>-<kind>; never urn:cdx:	string	yes	pattern ^(evidence-[0-9]+-[0-9a-f]+|derived-[0-9]+-[A-Za-z0-9_-]+)$
type ART-001: file = raw evidence, data = derived artifact	string	yes	one of: file, data, machine-learning-model
name Filename as received (evidence) or as persisted (derived)	string	yes	—
hashes ART-003: at least one SHA-256 entry; stronger algorithms may be added	array	yes	items 1–∞
data Optional CycloneDX data classification for derived artifacts	array	—	—
properties ART-004: exactly one cyberbench:artifactClass of evidence | derived (closed set)	array	yes	—

Also defines: hashEntrypropertyEntry