Shared feature semantics the orchestrator uses across providers.
These pages explain what CrossWatch means by Watchlist, History, and Ratings.
You’ll only need this when a plan looks confusing.
Jump to:
Watchlist
History
Ratings
Related:
Pair feature toggles: Configure Pairs
How plans are built: One-way sync, Two-way sync
These are the shared feature semantics used by the orchestrator across providers.
Core code: cw_platform/orchestrator/_pairs_oneway.py, cw_platform/orchestrator/_pairs_twoway.py
cw_platform/orchestrator/_pairs_oneway.py
cw_platform/orchestrator/_pairs_twoway.py
Build snapshot (build_index).
build_index
Plan (adds/removes or upserts/unrates).
adds/removes
upserts/unrates
Apply (add/remove on the destination).
add/remove
Persist (baselines + checkpoints in state.json).
state.json
Related runtime pages:
Snapshot rules: Snapshots
Diff logic: Planner
Writes + chunking: Applier
Baseline persistence: State.json
Everything is keyed by a canonical key derived from IDs.
Common tokens:
imdb:tt...
tmdb:...
tvdb:...
Typed tokens are used to reduce season/episode duplication when keys differ.
present
delta
Providers declare how their snapshot behaves:
present: full list each run.
delta: incremental reads. The orchestrator merges baseline + current delta.
delta providers rely more on state (watermarks / checkpoints) for correctness.
Last updated 12 hours ago
Was this helpful?
