validation-contract

# Validation Contract Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178. <!-- dual-compat-start --> ## Use When - Authoring a new specialist skill and deciding which validation evidence it should produce. - Normalising an older specialist skill against the current house style. - Preparing a feature or release for ship and assembling the Release Evidence Bundle. - Reviewing a PR that claims a feature is production-ready. ## Do Not Use When - The work is purely local, experimental, or explicitly throwaway with no path to production. - The skill being authored is a baseline, process, or pure index skill. Those do not declare evidence. - The task is unrelated to validation planning or shipping readiness. ## Required Inputs - The specialist skill or feature being validated, including its intended scope and risk tier. - Access to the repository's existing validation skills (`advanced-testing-strategy`, `vibe-security-skill`, `observability-monitoring`, etc.) as the source of category-specific "how to validate" content. - Awareness of the 14 canonical artifact templates in `skill-composition-standards/references/` so evidence rows can cite existing formats. ## Workflow - Identify whether the skill or feature in scope is specialist (declares evidence) or baseline/process (does not). - For specialist skills: map each artifact the skill produces to one of the seven evidence categories. - For releases: produce a Release Evidence Bundle that links con...