Skip to main content

Task Breakdown: Item Source Validation

Feature ID: item-source-validation Status: Done (Retrospective) Last updated: 2026-05-01

Phase 1 — Schema​

  • T1. Item YAML source_validation blob shape defined in contracts.
  • T2. Migration: add sourceValidationCadence to work_schedules (nullable additive).

Phase 2 — Services​

  • T3. Deterministic reachability checker.
  • T4. Content-extraction wrapper.
  • T5. AI accuracy evaluator with structured output.
  • T6. ItemSourceValidationService.checkItem(workId, slug) that orchestrates the three steps and persists the blob.

Phase 3 — Integration​

  • T7. Post-generation hook: validate every item after a successful run.
  • T8. ItemSourceValidationSchedulerService Trigger.dev cron task using the work's cadence.
  • T9. Manual re-check endpoint with short-window cache.
  • T10. Apply-suggestion writes source_url and re-validates.

Phase 4 — Web​

  • T11. Items UI status indicator (warning vs persistent text).
  • T12. Action menu: Re-check source, Apply suggestion.
  • T13. Schedule UI exposes sourceValidationCadence.

Phase 5 — Tests​

  • T14. Reachability mapping (404/410 → broken; 5xx → unknown).
  • T15. End-to-end validate-item with AI mock.
  • T16. Cadence selection (own vs fallback).

Phase 6 — Docs​

  • T17. User-facing doc docs/features/item-source-validation.md.
  • T18. Cross-link in scheduled-updates.md.
  • T19. Retrospective spec/plan/tasks.

Definition of Done​

  • All tasks shipped, tests pass, docs present, constitution gates verified.