Catalog Validation Structure

This document defines how hardware-target validation is organized in core.

Source of Truth

• configs/onboarding/*.yaml is the canonical source for catalog-facing target metadata.
• Validation status fields (pass_rate, verified, validation.*) are written in this repo by CI.

Workflow Responsibilities

1. core-onboarding-smoke.yml
2. Purpose: fast PR-gate smoke checks on a curated matrix of representative targets.

3. Output: onboarding smoke artifacts and scoreboard.

4. core-validate-hw-targets.yml

5. Purpose: full onboarding target sweep for catalog metadata refresh.
6. Trigger: scheduled/manual and selected main pushes.
7. Output:
8. Updated configs/onboarding/*.yaml with validation metadata.
9. out/hw-target-validation/summary.json and summary.md artifacts.

Contract for Downstream Consumers

Downstream services (for example Foundry catalog ingest) should consume only:

1. onboarding manifests in this repo, and
2. validation links stored under validation.run_url / validation.artifacts_url.

They should not run separate target-validation pipelines against a forked catalog source.