PagePointEngineering
Overview Current Sprint Current Context DYY9 Release Candidate Engineering Principles Architecture PPOE PPSM Networking Phone Provisioning Audio Standard Roadmap Decision Log Testing Hardware Publishing

Project Constitution

Engineering Principles

The design philosophy that governs PagePoint architecture and implementation decisions.

  • Separate Operations from Maintenance.
  • PPOE operates.
  • PPSM maintains.
  • Infrastructure belongs to PPSM.
  • PPOE must remain lean, predictable, and appliance-like.
  • PPSM must never be required for live paging, audio playback, sequence execution, or relay control.
  • No dependency on customer IT for core PagePoint operation.
  • Appliance first, computer second.
  • Diagnostics before repair.
  • Report before modifying a connected phone or operational system.
  • Keep operator UI simple.
  • Installer workflow should be highly automated, but not dishonest about Android security prompts.
  • Every feature should have one clear responsibility.
  • When the requested change is small, preserve the blast radius.
  • Do not turn a channel map, UI move, or timing adjustment into an audio-engine refactor unless evidence demands it.
  • For live paging, reliable and fast operation is more important than perfect-looking diagnostic counters.
  • Every PPSM feature must help install, maintain, diagnose, update, or recover PagePoint.
  • If a feature helps make announcements, it belongs in PPOE.
  • Live/runtime TTS is excluded from PPOE.
  • PPSM Version 1 assumes externally generated audio.
  • Future PPSM content compilation may be considered separately from live operations.
  • Cloudflare is a publishing target, not the source of truth.
  • Read the Portal. Build the Code. Update the Portal.