Build the admin event anchor management UI #40

New issue

Open

opened 2026-07-28 04:57:35 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-07-28 04:57:35 +00:00

Context

The EventAnchor model lands in v0.3.0 to feed constraint propagation. This issue adds
the management UI the spec places in the admin panel.

Scope

Admin UI for creating, editing, and managing event anchors.

Implementation notes

List anchors with label, date range, notes, and the count of photos associated with each.
Create and edit anchors with a date range and precision, not a single date.
Associate and disassociate photos, including a bulk path â€” anchors typically cover a run
of photos, and one-at-a-time association would make the feature impractical.
Editing an anchor's dates must show its blast radius before saving: how many photos have
derived evidence from this anchor and will be recomputed. A correction to a widely used
anchor can shift dozens of derived dates, and the admin should see that before confirming.
Deleting an anchor supersedes derived evidence rather than deleting it, and the UI must
say so plainly.
A timeline view of anchors makes overlaps and gaps visible and is a natural fit here.
Show which anchors are actually contributing evidence, so unused anchors are identifiable.

Done when

Anchors can be created, edited, and deleted from the admin console
Photos can be associated with anchors individually and in bulk
Editing an anchor shows how many derived dates will be recomputed before saving
Deletion supersedes derived evidence and communicates that clearly
Anchor usage is visible

References

docs/circa-spec.md section 8 (EventAnchor), section 11
The EventAnchor model issue in v0.3.0

Depends on: the EventAnchor model, #19 (constraint propagation).

## Context The `EventAnchor` model lands in v0.3.0 to feed constraint propagation. This issue adds the management UI the spec places in the admin panel. ## Scope Admin UI for creating, editing, and managing event anchors. ## Implementation notes - List anchors with label, date range, notes, and the count of photos associated with each. - Create and edit anchors with a date range and precision, not a single date. - Associate and disassociate photos, including a bulk path â€” anchors typically cover a run of photos, and one-at-a-time association would make the feature impractical. - Editing an anchor's dates must show its blast radius before saving: how many photos have derived evidence from this anchor and will be recomputed. A correction to a widely used anchor can shift dozens of derived dates, and the admin should see that before confirming. - Deleting an anchor supersedes derived evidence rather than deleting it, and the UI must say so plainly. - A timeline view of anchors makes overlaps and gaps visible and is a natural fit here. - Show which anchors are actually contributing evidence, so unused anchors are identifiable. ## Done when - [ ] Anchors can be created, edited, and deleted from the admin console - [ ] Photos can be associated with anchors individually and in bulk - [ ] Editing an anchor shows how many derived dates will be recomputed before saving - [ ] Deletion supersedes derived evidence and communicates that clearly - [ ] Anchor usage is visible ## References - `docs/circa-spec.md` section 8 (`EventAnchor`), section 11 - The `EventAnchor` model issue in v0.3.0 Depends on: the EventAnchor model, #19 (constraint propagation).

claude-bot added this to the v0.5.0 milestone

2026-07-28 04:57:35 +00:00

claude-bot added the

enhancement

frontend

labels

2026-07-28 04:57:35 +00:00