feat(doors): manage exclusions with provenance and review #194

New issue

Open

opened 2026-09-30 15:26:12 +00:00 by gabogg · 0 comments

gabogg commented

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

Owner

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

Intended outcome

Make door exclusions understandable and manageable from the Supervisor workspace. The current exclude_from_rankings flag also affects status sub-counters and activity; exclusion_source distinguishes AUTO from MANUAL, and /api/doors/override is admin-only.

Triage questions

Should exclusion be one global policy or separate choices for live rankings, status counts, alarms, historical reports, and activity? Which data must remain visible for audit even when excluded?
Who may set or clear exclusions? Should a reason, author, start/end time, and review date be required? Can a Supervisor override automatic sensorless quarantine?
How do bulk/category changes interact with per-door manual choices and later hardware reclassification? How is precedence shown in the UI?
How should excluded doors appear in reports and the door inventory, and how can a Supervisor find every exclusion needing review?
Does a human-entered door status from #191 influence exclusions, or are these independent decisions? How does the UI explain the difference?

Ready-to-spec outcome

A documented scope and precedence policy, audited mutation workflow, and explicit cases for restart/sync, category changes, auto recovery, and report visibility. Preserve existing AUTO/MANUAL provenance unless triage chooses a migration.

Part of #187 — milestone: Focused operator and supervisor door operations. ## Intended outcome Make door exclusions understandable and manageable from the Supervisor workspace. The current `exclude_from_rankings` flag also affects status sub-counters and activity; `exclusion_source` distinguishes `AUTO` from `MANUAL`, and `/api/doors/override` is admin-only. ## Triage questions 1. Should exclusion be one global policy or separate choices for live rankings, status counts, alarms, historical reports, and activity? Which data must remain visible for audit even when excluded? 2. Who may set or clear exclusions? Should a reason, author, start/end time, and review date be required? Can a Supervisor override automatic sensorless quarantine? 3. How do bulk/category changes interact with per-door manual choices and later hardware reclassification? How is precedence shown in the UI? 4. How should excluded doors appear in reports and the door inventory, and how can a Supervisor find every exclusion needing review? 5. Does a human-entered door status from #191 influence exclusions, or are these independent decisions? How does the UI explain the difference? ## Ready-to-spec outcome A documented scope and precedence policy, audited mutation workflow, and explicit cases for restart/sync, category changes, auto recovery, and report visibility. Preserve existing AUTO/MANUAL provenance unless triage chooses a migration.

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

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

gabogg added the

needs-triage

label

2026-09-30 15:26:12 +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 referenced this issue

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

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