schedule-continuity-workflow

Schedule continuity is maintained by coordinating the update, validate, and publish cycle across erify_api, erify_studios, and Google Sheets to apply deterministic diff and upsert behavior. This prevents gaps when publishing schedule changes.

Handling cancelled and reappearing shows is managed by tracking identity and task continuity through states like removed and cancelled_pending_resolution. This ensures cross-system alignment by client_id and external_id during updates.

Cross-system consistency is ensured by orchestrating the update, validate, and publish flow across API, frontend, and planning scripts. It applies deterministic diff and upsert behavior aligned by client_id and external_id.

Audit-ready metadata for schedule policy checks is generated by recording reasons and resolutions during the update cycle. This supports governance by tracking pending resolutions and cross-system alignment.

Schedule gaps occur when publishing changes across erify_api, erify_studios, and Google Sheets without a coordinated workflow. The schedule continuity workflow prevents this by enforcing deterministic diff and upsert behavior.

Yes, you can validate schedule changes before publishing by applying the update, validate, and publish cycle. This orchestrates checks across API, frontend, and planning scripts to ensure continuity before final publication.