Separate PPOE and PPSM
Reason: Operations and maintenance must remain independent so service work cannot interfere with paging.
Architecture Record
Decision Log
Decisions that define PagePoint direction.
DNS/DHCP belongs to the PPSM appliance
Reason: Infrastructure services belong with maintenance and must run as OS-level daemons independent of the PPSM app process.
No live/runtime TTS in PPOE
Reason: PPOE must remain a reliable playback and paging appliance, not a speech-generation system.
PPSM Version 1 assumes externally generated audio
Reason: External generation provides flexibility, better quality, and independence from a specific TTS engine.
PPSM touchscreen is for service, not administration
Reason: The panel should support quick installer tasks. Browser-based Service Portal handles keyboard-heavy work.
Use file-based PPSM storage for Version 1
Reason: Configuration, packages, backups, logs, inventory, audit records, and job status are naturally file-based. Avoid SQLite until there is a real query or concurrency need.
Engineering Portal source lives inside PagePoint
Reason: The portal is the living technical history. It must version with the project and survive hosting changes or AI session resets.