Saved queues and watch subscriptions #113

Open
opened 2026-07-28 06:06:05 +00:00 by claude-bot · 0 comments

Severity: MEDIUM

The problem

docs/circa-spec.md §11.4 requires notifications driven by durable saved queues and watched
albums. The wireframes show a Saved Queue selector. The API spec §17 left it as an open question
that was never resolved into an issue. #27 covers disputes, mentions, and batches — but has no
watch targets to hang them on.

This is also how multi-person division of labour works without formal assignment: "I'm working the
Red Album, you take the loose photos."

Scope

  • A saved queue entity: name, filter, sort, owner, optional shared flag.
  • Queue selector in the browser and workspace.
  • Watch an album or a saved queue; #27's notifications fire on new matching photos.
  • Queue depth and progress visible per queue.

This depends on the queue substrate introduced by the review navigation work (#95) — the same
(filter, sort, cursor) definition, made durable and nameable.

Done when

  • A reviewer can save, name, and return to a queue
  • Albums and queues can be watched
  • Notifications fire against watch targets
  • Queue progress is visible

References

  • docs/circa-spec.md §11.4, §16
  • docs/circa-api-spec.md §17

Depends on: #95 (queue substrate), #27 (notifications).

## Severity: MEDIUM ## The problem `docs/circa-spec.md` §11.4 requires notifications driven by durable saved queues and watched albums. The wireframes show a Saved Queue selector. The API spec §17 left it as an open question that was never resolved into an issue. #27 covers disputes, mentions, and batches — but has no watch targets to hang them on. This is also how multi-person division of labour works without formal assignment: "I'm working the Red Album, you take the loose photos." ## Scope - A saved queue entity: name, filter, sort, owner, optional shared flag. - Queue selector in the browser and workspace. - Watch an album or a saved queue; #27's notifications fire on new matching photos. - Queue depth and progress visible per queue. This depends on the queue substrate introduced by the review navigation work (#95) — the same `(filter, sort, cursor)` definition, made durable and nameable. ## Done when - [ ] A reviewer can save, name, and return to a queue - [ ] Albums and queues can be watched - [ ] Notifications fire against watch targets - [ ] Queue progress is visible ## References - `docs/circa-spec.md` §11.4, §16 - `docs/circa-api-spec.md` §17 Depends on: #95 (queue substrate), #27 (notifications).
claude-bot added this to the v0.4.0 milestone 2026-07-28 06:06:05 +00:00
Sign in to join this conversation.
No description provided.