- Create sectors table migration (034) with RLS and devices.sector_id FK - Add Sector ORM model with site_id and tenant_id foreign keys - Add SectorCreate/Update/Response/ListResponse Pydantic schemas - Implement sector_service with CRUD and device assignment functions - Add sectors router with GET/POST/PUT/DELETE and device sector assignment - Register sectors router in main.py - Add sector_id and sector_name to Device model and DeviceResponse Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
3.5 KiB
gsd_state_version, milestone, milestone_name, status, stopped_at, last_updated, progress
| gsd_state_version | milestone | milestone_name | status | stopped_at | last_updated | progress | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1.0 | v9.7 | Tower & Site Management | unknown | Completed 13-03-PLAN.md | 2026-03-19T11:13:17.840Z |
|
Project State
Project Reference
See: .planning/PROJECT.md (updated 2026-03-18)
Core value: Operators can monitor, configure, and troubleshoot their entire MikroTik fleet from a single pane of glass Current focus: Phase 13 — link-discovery-registration-ingestion
Current Position
Phase: 13 (link-discovery-registration-ingestion) — COMPLETE Plan: 3 of 3 (all complete)
Performance Metrics
Velocity:
- Total plans completed: 7
- Average duration: 3 min
- Total execution time: 0.35 hours
By Phase:
| Phase | Plans | Total | Avg/Plan |
|---|---|---|---|
| 11 | 3 | 12min | 4min |
| 12 | 2 | 6min | 3min |
| 13 | 2 | 5min | 2.5min |
| Phase 13 P01 | 5min | 2 tasks | 4 files |
| Phase 13 P03 | 3min | 2 tasks | 6 files |
Accumulated Context
| Phase 11 P01 | 3min | 2 tasks | 9 files | | Phase 11 P02 | 6min | 3 tasks | 8 files | | Phase 11 P03 | 3min | 2 tasks | 5 files | | Phase 12 P01 | 3min | 2 tasks | 6 files | | Phase 12 P02 | 3min | 2 tasks | 3 files | | Phase 13 P01 | 3min | 2 tasks | 6 files | | Phase 13 P02 | 2min | 2 tasks | 5 files |
Decisions
Decisions are logged in PROJECT.md Key Decisions table.
- Sites must use nullable site_id FK (never mandatory) to preserve flat-list workflow
- Per-client wireless data gets its own NATS stream and hypertable (not DEVICE_EVENTS or wireless_metrics)
- Link state machine requires 3 consecutive missed polls before marking down (prevents false flapping)
- [Phase 11]: alert_count set to 0 with TODO -- alert_events integration deferred to avoid coupling
- [Phase 11]: Site detail page kept minimal (info + stats) -- full dashboard deferred to Phase 14
- [Phase 11]: Used Dialog for delete confirmation (no AlertDialog component in UI library)
- [Phase 11]: Site column placed after Model in fleet table for logical grouping
- [Phase 11]: Viewers see site name text, operators get Select dropdown for assignment
- [Phase 12]: Used unified tenant_isolation RLS policy with super_admin OR clause (matching codebase convention) instead of separate super_admin_bypass policy
- [Phase 12]: WIRELESS_REGISTRATIONS NATS stream uses 30-day retention (vs 24h for DEVICE_EVENTS) for historical client analytics
- [Phase 12]: RF monitor collection gated on wireless interface presence to avoid unnecessary API calls
- [Phase 13]: No backref on DeviceInterface.device relationship -- link discovery reads interfaces directionally
- [Phase 13]: MAC addresses lowercased at collection time for consistent downstream matching
- [Phase 13]: InterfaceInfo (identity/link discovery) kept separate from InterfaceStats (traffic counters)
- [Phase 13]: Link discovery uses separate durable consumer on WIRELESS_REGISTRATIONS for independent processing
- [Phase 13]: Unknown clients query uses DISTINCT ON (mac_address) for most recent data per MAC
Pending Todos
None yet.
Blockers/Concerns
- OpenBao dev instance loses Transit keys on data wipe — device creds need re-entry
- RouterOS 7 WiFi registration-table field names need validation on real hardware (Phase 12)
- MAC-to-device resolution data source needs codebase audit (Phase 13)
Session Continuity
Last session: 2026-03-19T11:13:17.837Z Stopped at: Completed 13-03-PLAN.md Resume file: None