验证证据 Controller
This Skill exclusively controls 流程管理/Validation.md. It creates, validates, and updates this artifact without taking over the semantic work of requirement analysis, planning, decision-making, engineering, or approval.
Trigger
- 每次工程修改或验证活动。
project-initializationselects this controller from.codex/harness/document-controllers.jsonwhen the artifact is required for the project type or enabled module.
Contract
- Purpose: 记录 smoke、模块、集成、E2E、eval、浏览器截图和生产闭环证据。
- Use
assets/template.mdas the initial structure; preserve newer user content and append the smallest valid delta. - Validate the required headings, stable identifiers, links to related records, and current status before returning.
- Update
ROUTER.mdthroughdoc-routeronly when this file is created, moved, renamed, or retired. - Never duplicate another artifact's facts. Link by requirement, task, decision, issue, version, or release ID.
- Runtime Skill/Hook events belong in
.codex/harness/runtime-events.jsonl, not this Markdown file.
Boundaries
- Keep this Markdown artifact as human-readable governance evidence. Its controller or semantic Skill owns validation and transitions; the file records timestamp, triggering user request, called Skills/plugins, current status, related IDs, result, and next route.
- Do not create a Markdown state-machine definition. Raw Hook/Skill telemetry remains in the machine event log; this artifact keeps only calls needed to explain its own lifecycle.
- Do not approve a Plan, decision, release, or acceptance on the user's behalf.
- If a required field is unknown, mark it explicitly and route the gap to the responsible semantic Skill.


