Context Recovery
Current Context
Where PagePoint is right now. Read this before touching code after a reset or handoff.
Current Architectural State
PagePoint is split into PPOE and PPSM. PPOE is the live operations appliance. PPSM is the service appliance. Maintenance must never interfere with operational paging.
Subsystem Status
| Subsystem | Status |
|---|---|
| PPOE | Operational runtime with live paging, messages, sequences, traffic, relays, and phone UI. |
| PPSM | Service appliance foundation active; UI, portal, network ownership, and provisioning workflow are current focus. |
| Networking | PPSM owns DNS/DHCP and Android validation services at the appliance level. |
| Phones | Ulefone Armor X12 target; provisioning automation still needs validated ADB implementation. |
| Engineering Portal | Canonical source now lives at C:\PagePoint\engineering-portal\src. |
Current UI Work
- PPSM touchscreen/service UI is active work.
- PPSM Service Portal is the installer/admin surface for keyboard-heavy tasks.
- PPOE LP buttons are evolving into Launch Pad Status Cards.
- PPOE UI direction: no bottom status bar, taller top status bar, phone icon, battery icon, Wi-Fi icon, improved typography, taller zone cards, centered LP label/countdown/current sequence message, progress bar retained.
Immediate Priorities
- Keep Engineering Portal source updated as architecture changes.
- Move phone provisioning from design notes to verified implementation.
- Keep PPSM UI useful for service without becoming operator UI.
- Keep PPOE runtime stable while UI polish continues.
Open Questions
- Exact ADB commands that are reliable on Ulefone Armor X12 Android 13 Go.
- Whether future PPSM content compilation should generate audio from structured text packages.
- Exact Cloudflare publishing command or repo integration for
engineering.pagepoint.io. - How much of the older local PPSM docs should be updated or replaced by portal source pages.