| name | manual-validation-flow |
| description | Use when: changing pending validation behavior, needs_validation flags, approval or rejection flow, validation routes, staged file finalization, or the web admin validation UI in Soundome. |
| argument-hint | Describe the validation-flow change, affected layer, and expected user-visible behavior. |
Manual Validation Flow
Use this skill for changes that touch the review flow for partially matched or uncertain tracks.
Scope
needs_validation and validation_reason
- staged file retention
- approve or reject endpoints
- finalization after manual edits
- frontend validation list and actions
Procedure
- Determine whether the change starts in domain, server, or web.
- Trace the flow across these layers:
- domain: load staged track, apply patch, tag and organize, clear validation state
- server: expose approve or reject routes and DTOs
- web: render pending items and send the correct payloads
- Preserve the invariant that audio is already present in staging before manual approval.
- Preserve safe behavior when a user rejects a pending track.
- Confirm that the validation state transitions are explicit and persisted.
- Validate the narrowest affected slice first.
Useful files
packages/domain/src/services/download_service.rs
apps/server/src/routes/validations.rs
apps/web/src/
docs/workflows/web-admin.md