Citizen-facing services · Community communication

PBB Chat / Civitas

LAN-local community rooms, direct messages, requests, moderation, and a clear emergency handoff to Hotline.

Integrated · Production hardening Baseline node service

Primary placement: Daily-apps node; Barangay node
Primary users: Community members, Local moderators, Barangay administrators

What it is

A practical part of one local platform

PBB Chat / Civitas is a Laravel community communication service for a local barangay network. It supports rooms, direct conversations, message requests, read state, badges, reports, blocks, moderation, and PBB Realtime-powered live updates.

Civitas is intentionally LAN-local and its public gateway is disabled. Emergency escalation is a handoff that returns the configured Hotline URL and context; direct incident creation, Relay synchronization, and a durable browser-offline compose queue are not confirmed.

Problem it solves

The operational gap

Communities need a dependable local communication space that does not disappear with internet access, while emergency reporting remains clearly routed to the dedicated Hotline workflow.

Core workflow

How Civitas supports local work

Enter the local community space
A local user opens Civitas through the node LAN and joins rooms or an approved direct conversation.
Communicate locally
Messages persist in the local Chat database and supported live updates move through the local Realtime gateway.
Use safety controls
Users and moderators can report, block, mute, review, hide, or resolve supported community-safety issues.
Hand off emergencies
The escalation action points the user to Hotline with limited context instead of claiming direct incident creation.

Who uses it

Designed around local service roles

Community members
Local moderators
Barangay administrators

Offline-first behavior

What continues locally—and what does not

Works on the local node

Rooms, direct messages, requests, safety actions, badges, and moderation are backed by the local Chat database.
The application is intended for local/LAN access with public gateway exposure disabled.

Required local services

Civitas requires its Laravel app and MySQL database.
PBB Realtime is required for confirmed live room and direct-message events; persisted records remain app-owned.

When a route returns

Account can support sign-in and app-admin provisioning when configured.
Realtime resumes supported live delivery when the local gateway is reachable.

Connectivity-dependent

Users need a route to the local Chat node; internet access is not a confirmed requirement.
The Hotline handoff needs the configured local Hotline URL to be reachable.

Not currently synchronized

No Relay synchronization of community messages or moderation data is confirmed.
No durable browser-side offline compose queue or direct Hotline incident creation is confirmed.

Deployment placement

Where it fits

Baseline deployment

Daily-apps node; Barangay node

Hardware, connectivity, power, training, travel, and field logistics remain deployment-specific.

Practical questions

Frequently asked questions

Does Civitas need the public internet?

No. Civitas is designed to work on the local PBB network using its local database and live-update service.

Can Civitas be exposed through the public gateway?

Not in the current release. Civitas should remain available only on the local network unless a separate security plan is reviewed and approved.

Does an escalation automatically create a Hotline incident?

No. Civitas can send the user to Hotline with a small amount of helpful context, but it does not automatically create an incident.

Can users compose messages while disconnected from the node?

This is not confirmed. Users should assume their browser must still be connected to the local Chat node to write and send messages.

Are community messages copied to other nodes?

No. Messages, reports, blocked-user lists, and moderation records currently stay on their local node.

What must be approved before a live community rollout?

The deployment owner must approve how long records are kept, who may moderate content, how backups and deletions work, how device sessions are handled, and what operators must do.

Status and readiness

Integrated

Local room, direct-message, safety, moderation, Realtime, Hotline handoff, and Account integration paths are implemented.

Remaining hardening work

Approve local message retention, moderation, backup, and purge policy.
Keep public gateway exposure disabled unless a separate security model is reviewed.
Decide whether any future selective upstream synchronization is appropriate.

Connected platform

Local-node foundation

Briefing and pilot discussion

Discuss Civitas in a local PBB deployment

Explore how a local-node deployment could support practical service continuity in your community.

Request a briefing