# Internet Use Control — Original Notes (archived)

> Historical pre-planning notes. **Superseded by `AGENTS.md`.** Do not build from this.


> Kept for provenance. The sections above replace these. Do not build from this.

```
Project Goal & Philosophy
- A cross-platform screening system (Android + Windows) that helps kids
  self-regulate evening screen usage. A gentle enforcement layer, a reminder
  system (overlays, warnings, sounds), and a notifier via Apprise.
- A centralized Docker dashboard for scheduling, logging, and remote management.

Components (original)
- Central Orchestrator (Go + HTMX + Tailwind), SQLite, Docker, behind Caddy at
  webrestrict.lab.audasmedia.com.au. Session login.
- Windows Client (Python + psutil + pystray): background loop, warning overlays,
  .wav countdowns, process termination, domain logging, ACPI sleep/shutdown,
  4-digit parent PIN.
- Android Agent (Kotlin, Device Owner): ForegroundService, setPackagesSuspended,
  WindowManager overlay, usage reporting.

Original phases
1. Go + HTMX Docker environment; SQLite tables for schedules and blocklists.
2. Client telemetry API (POST /api/log, GET /api/client-config); Apprise triggers.
3. Windows monitor script.
4. Kotlin Device Owner workspace.
5. LAN control integration.

Ideas (kept)
- Usage stats for kids: total time, top apps, by day and week.
- Some apps allowed through: Spotify, school sites and timetables.

Superceded by the decisions in this spec: the 30-second poll is replaced by MQTT;
the router/DNS and "network hooks" ideas are dropped in favour of device-side
enforcement; the Rust idea is dropped; the chores idea is removed.
```