artifact-validationlisted

# Artifact Validation ## Purpose Decide whether a specific Artifact revision can safely support the declared target and downstream use, applying Reuse Before Regenerate. ## Trigger Run before consuming an existing Artifact, after an Artifact is created or changed, when an upstream dependency changes, or when prior evidence is stale or incomplete. ## Inputs - Artifact ID, type, content, revision, source, owner, and intended use. - Required upstream Artifact revisions and applicable Project Constraints. - Target Stage/Artifact, effective Workflow Level, prior validation, and known limitations. ## Prerequisites - Confirm the exact revision and validation scope. - Resolve or explicitly record uncertain Artifact type and provenance. - Identify the minimum validation depth required by target risk. ## Procedure 1. Verify content-based Artifact classification and provenance. 2. Check completeness against its intended consumer and Definition of Done. 3. Check internal consistency and consistency with authoritative Artifacts. 4. Check correctness using source evidence, executable checks, or independent review appropriate to type. 5. Check freshness against upstream revisions, repository state, and `Last Verified`. 6. Check dependency compatibility, including versioned Contracts, schemas, constraints, and assumptions. 7. Check fitness for the current target; an Artifact may be valid for one scope but insufficient for another. 8. Record evidence, validator, evaluated revisions,