ReelkeeperYour private watch journal633 titles · 351 seasons

Workspace

What Reelkeeper knows

A reviewable view of supported media, saved settings, uncertainty, and meaningful changes.

Known

984 canonical titles

302 watched and 283 deliberately saved for later.

Needs review

20 uncertain identities

Generic filenames and shared titles remain visible rather than guessed.

Supported

Anything watchable

Movies, TV, limited series, specials, documentaries, videos, and other formats share one safe model.

Preferences

How Reelkeeper organizes the library

Browse groups

  • media type
  • release year
  • genre

Watchlist defaults

  • medium priority
  • Needs-review titles shown separately
  • Routine requested local updates saved after validation

Readable safeguards

Rules that protect your library

Evidence before certainty

Researched details and artwork retain sources. Missing facts stay labeled.

Source first

Watchable and watchlist records change before pages are rebuilt.

Canonical pages, fewer duplicates

Saved titles reuse their watchable pages, repeated research references share one research page, and seasons live at anchors on their parent show page. A generated manifest makes stale-page pruning deterministic.

Status stays synchronized

Every status change finds and refreshes all explicitly linked cards. Watched cards show a clear ✓ Watched ribbon everywhere they appear; other statuses never inherit that checkmark.

One show card, independent seasons

A multi-season show has one top-level card. Its detail page contains season cards with their own artwork and independent statuses; parent status is never inferred from its seasons.

Discover stays a collection hub

Specific collections keep one card on Discover and their full contents on separate pages. Rendering must verify established cards, local artwork, and target links before replacing the hub.

Broad changes back up automatically

Before a broad authorized change, Reelkeeper automatically creates and verifies a recoverable snapshot under backups/, then continues without asking. Large HTML replacements also keep timestamped page history.

Project-local temporary files

Agent scratch work uses unique task directories under the project’s tmp/ root. Temporary files never replace canonical state, and cleanup stays limited to the exact task directory.

Publishing stays deliberate

Publishing uploads only the generated public review surface and requires a current direct Publish Site request.

Website publishing

Publish Site

First publication

Download a deployment credential from your 8bit account, then say Publish Site. Only the bundled bootstrapper and its verified official publishing client read the credential; setup stores the token separately in protected local storage and continues with publishing. Delete the downloaded credential file after setup succeeds.

Later updates

Say Publish Site again. Reelkeeper reuses the protected local setup and uploads only the current public site/ directory. Workspace source, backups, agent instructions, Git data, and secrets are never uploaded, and publishing never occurs automatically during local work.

Recent changes

Meaningful activity

  1. clear in progress batch 20260823

    success · reelkeeper.watchables.manage

  2. remove public implementation copy 20260823

    success · workspace.maintain

  3. public 8bit footer 20260823

    success · workspace.maintain

  4. public facing helper cleanup 20260823

    success · workspace.maintain

  5. remove workspace navigation 20260823

    success · workspace.maintain