feat(supervisor): manage existing door inventory and metadata #190

New issue

Open

opened 2026-09-30 15:25:49 +00:00 by gabogg · 0 comments

gabogg commented

2026-09-30 15:25:49 +00:00

Owner

Part of #187 — milestone: Focused operator and supervisor door operations.

Intended outcome

Give Supervisors a useful inventory and management workflow for existing HikCentral doors. door_records currently follows HikCentral telemetry, and names/categories/exclusion flags already exist; the management boundary must be clear before edit forms are built. Manual status for existing doors belongs to #191, labels to #195, and exclusion policy to #194.

Triage questions

Which fields can a Supervisor view or edit: local display name, location, operational notes, and hardware identity? Which remain hardware-owned?
Which local edits survive synchronization and restarts, keyed by the existing hardware door ID? How are stale/disconnected/retired doors represented?
Should changes be audited and reversible? How should the UI distinguish live telemetry from locally maintained metadata and the manual status in #191?

Ready-to-spec outcome

A field ownership table for existing doors, synchronization rules, and a minimal Supervisor inventory workflow. This issue does not create new door identities or define manual status semantics.

Part of #187 — milestone: Focused operator and supervisor door operations. ## Intended outcome Give Supervisors a useful inventory and management workflow for existing HikCentral doors. `door_records` currently follows HikCentral telemetry, and names/categories/exclusion flags already exist; the management boundary must be clear before edit forms are built. Manual status for existing doors belongs to #191, labels to #195, and exclusion policy to #194. ## Triage questions 1. Which fields can a Supervisor view or edit: local display name, location, operational notes, and hardware identity? Which remain hardware-owned? 2. Which local edits survive synchronization and restarts, keyed by the existing hardware door ID? How are stale/disconnected/retired doors represented? 3. Should changes be audited and reversible? How should the UI distinguish live telemetry from locally maintained metadata and the manual status in #191? ## Ready-to-spec outcome A field ownership table for existing doors, synchronization rules, and a minimal Supervisor inventory workflow. This issue does not create new door identities or define manual status semantics.

gabogg added this to the Focused operator and supervisor door operations milestone

2026-09-30 15:25:49 +00:00

gabogg added the

needs-triage

label

2026-09-30 15:25:49 +00:00

gabogg referenced this issue

2026-09-30 15:26:53 +00:00

epic(ui): focus Operator on doors and alarms; introduce Supervisor workspace #187

gabogg changed title from ~~feat(supervisor): manage door inventory and manual identities~~ to feat(supervisor): manage existing door inventory and metadata

2026-09-30 16:03:53 +00:00