# v1 implementation and future scope

The original chat's feature suggestions were readable, but its later version-allocation replies were saved as content-reference placeholders. This release follows the explicit v1 request in the build brief. The v2–v8 allocation below is a **proposed grouping**, not a recovered claim about that unavailable version plan.

## Implemented in v1.0

| Area | Delivered |
|---|---|
| Installation | Upload-ready dependency package; first-access environment/key/token preparation; token-protected browser wizard; PHP/extensions/writability preflight; PostgreSQL/Redis connection verification; migrations; administrator creation; encrypted saved database credentials; installation lockout |
| Authentication | Root client login and /admin administrator login; separate guards, cookies and cookie paths; role checks; password hashing; login throttling; CSRF; session regeneration/logout |
| UI | Responsive Vue application; dark/light persistence; mobile bottom navigation/account menu; empty/loading/error states; keyboard-aware dialogs; monitor search/status/group filtering |
| Clients | Administrator provisions client accounts and assigns monitors/groups; client requests are scoped to their own records |
| Monitors | Create/edit/delete/pause/resume HTTP(S), TCP and ICMP monitors; configurable interval, timeout, retries/delay, expected HTTP status, degradation threshold and successful-run recovery threshold |
| Worker execution | Redis job queue; scheduler; due-time dispatch; persistent run leases; stale-run recovery; idempotent result recording; delayed retry jobs; process timeouts |
| Network safeguards | Public address policy by default; HTTP DNS pinning; no redirects/proxies; TLS validation; bounded response size; command-array ICMP invocation |
| Groups | Owner-scoped groups; monitor assignment; group filtering; deleting a group retains monitors |
| Data and incidents | Separate per-attempt check history, incidents and incident timeline events; started/detected/resolved timestamps; reason and failed-check count |
| Metrics | Observed time-weighted uptime/downtime; average and P95 successful latency; 24h/7d/30d/365d/year/custom ranges up to 366 days; sampled latency chart and availability strip |
| Health | Last-check freshness and stale display; worker heartbeat/processed count; queue size; failed-job count; checks per minute; protected DB/Redis/extension diagnostics |
| Releases | Trusted Ed25519 ZIP verification; archive safeguards and full hashes; staged complete releases; pre-migration pg_dump; recovery journal; exclusive deployment lock; atomic activation; failed-update recovery; manual database+code rollback |
| Delivery | Dependency locks; compiled assets in source archive; Docker/Compose/Nginx configuration; native setup and update instructions; automated tests; CI configuration |

## Deliberate v1 boundaries

- No WhatsApp or email delivery is enabled. Notifications are not simulated.
- The incident schema and automatic open/resolve lifecycle are implemented. Manual investigating/identified/monitoring workflows, notes, notification records, root cause and resolution editing are deferred.
- Uptime uses observed samples with gap limits; it is not a contractual SLA calculation. No pre-install history is fabricated.
- Latest incident/check lists show the most recent 100. Full history remains in PostgreSQL; paginated exploration and exports are deferred.
- Retries confirm from the same deployment, not a second independent geographic location.
- There is no public signup, self-service password reset/change UI, 2FA, fine-grained RBAC, public API-key access or audit-log viewer in v1.
- Deployment and updates assume one Linux host and a shared filesystem. Redis durability and backups are required; application-level distributed coordination is future work.
- Default data retention is indefinite. Database sizing, archive/rollup jobs, multi-million-row performance benchmarks and destination-host release drills are operational follow-up work.

## Deferred versions — proposed allocation

| Version | Functionality still to build |
|---|---|
| v2 | Email and supplied WhatsApp API integration; editable event templates/variables; previews/test sends; contacts; per-monitor notification rules; recovery messages; delivery/retry logs |
| v3 | Advanced reports; additional calendar presets; min/max/P50/P99; daily heatmaps; SLA targets/budgets; PDF/Excel/CSV exports; scheduled reports; retention and rollups |
| v4 | SSL expiry/issuer/validity checks; DNS checks; content/keyword checks; API GET/POST monitoring; heartbeat/cron monitoring; richer failure classification and slow-site rules |
| v5 | Public/custom-branded status pages and domains; manual incident announcements; automatic status-page updates; maintenance windows and SLA exclusions; incident notes/root-cause/resolution |
| v6 | Client teams and admin roles; fine-grained permissions; 2FA/passkey readiness; password recovery/account self-service; login/session history; audit logs; account administration |
| v7 | Multiple geographic monitoring nodes; cross-worker confirmation; monitor dependencies; alert correlation/suppression; cooldowns; escalation rules; infrastructure map; distributed release coordination |
| v8 | Server agents and CPU/RAM/disk/service metrics; domain-expiry monitoring; public scoped REST API; outbound webhooks; additional notification integrations/push/SMS; broader fleet operations |

No v2–v8 feature is described in the UI as available unless its basic v1 component is separately listed above.
