Works on the local node
- Installed game and learning assets run locally without a database or public internet connection.
- The mode policy and health summary are read from local configuration and registry files.
Citizen-facing services · Community engagement
PBB Games / Tabulus
Optional local games and preparedness-learning activities with safeguards for active incidents and emergencies.
Integrated · Pilot-ready foundation
Baseline node service
- Primary placement
- Daily-apps node
- Primary users
- Community members, Young people and families, Preparedness facilitators, Local node operators
What it is
A practical part of one local platform
PBB Games / Tabulus is a lightweight optional engagement service made from local PHP and static assets. It offers locally installed games and preparedness-learning activities without a database or confirmed operational API dependencies.
Tabulus stays subordinate to emergency work. Active-incident mode hides recreational categories while emergency mode disables all games and directs users toward emergency guidance. The current control is configuration-driven and needs an operator runbook.
Problem it solves
The operational gap
A resilient local network should offer useful everyday engagement as well as emergency services, while ensuring recreational use never competes with active response priorities.
Core workflow
How Tabulus supports local work
-
Open the local activity hub
A community member reaches Tabulus through the local PBB network after the optional package is installed.
-
Choose an available activity
The local registry displays only the games or preparedness activities permitted by the current mode.
-
Protect emergency capacity
Active-incident mode limits recreation, while emergency mode disables games and presents emergency guidance.
Who uses it
Designed around local service roles
- Community members
- Young people and families
- Preparedness facilitators
- Local node operators
Offline-first behavior
What continues locally—and what does not
Required local services
- Tabulus requires a local PHP/static host and its installed assets.
- It uses vendored Helper UI assets but does not require operational PBB APIs in the confirmed V1.
When a route returns
- No operational synchronization is required or confirmed for current game use.
- Future package updates would be installation activity rather than live application data sync.
Connectivity-dependent
- Users must be able to reach the local Games host over the node LAN.
- The configured Hotline link must be reachable for emergency guidance navigation.
Not currently synchronized
- No Hotline, Relay, Support, Realtime, Hub, Maestro, MapServer, or Kit Setup API calls are confirmed in V1.
- Tabulus does not store or synchronize scores as operational PBB records in the reviewed implementation.
Deployment placement
Where it fits
Optional deployment
Daily-apps node
Hardware, connectivity, power, training, travel, and field logistics remain deployment-specific.Practical questions
Frequently asked questions
Why are games part of a resilience platform?
Useful everyday activities give people a reason to know and use the local network before an emergency. Approved preparedness games can also support community learning.
What happens during an emergency?
Emergency mode turns off all games and shows emergency guidance. During an active incident, recreational games are hidden, while approved learning activities may remain available.
Do installed games need internet access?
No. Once installed, the current games and their files are stored on the local node and do not depend on a cloud service.
Does Tabulus call Hotline or Relay APIs?
No. The reviewed V1 does not show Tabulus exchanging operational information with Hotline, Relay, or the other PBB services.
Does Tabulus keep a community member database?
No. The reviewed version does not use a community member database. It works as a simple local game catalog with settings for operating modes.
Who changes the emergency mode?
The mode is currently changed through system settings. The exact person or automatic process responsible for changing it still needs to be documented and approved.
Status and readiness
Integrated
The local registry, mode policy, health endpoint, static assets, and emergency-mode safeguards are implemented without operational data dependencies.
Remaining hardening work
- Publish an operator runbook for changing mode during incidents.
- Confirm whether future mode control remains manual or receives a reviewed local signal.
- Review licensing and provenance before adding any third-party game assets.
Connected platform
Related modules
Local-node foundation
Related infrastructure
Briefing and pilot discussion
Discuss Tabulus in a local PBB deployment
Explore how a local-node deployment could support practical service continuity in your community.